You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The alphabetical order is quick and simple. However, it can leads to harder reading when the number of attributes is important. For example, FontSize and TextAlignment have a close relationship, but can be few attributes (lines) away.
Here are the different groups, and their ordering, proposed.
How to handle custom controls attributes ? If you are using a vendor control suite (like Telerik or Infragistics), you may have a ton of "misc" attributes.
Your feedback is welcome.
The text was updated successfully, but these errors were encountered:
cmaneu
changed the title
XA1003 - Use a grouped order instead of an alphabetical order.
XA1003 - Use a logical grouped order instead of an alphabetical order.
May 12, 2014
I agreed, sorting can be tricky to read.
Grouping is more logical, ie : I always group Width and Height together.
To automatise the process with a plugin, you need a configuration where you store grouped attributes.
Every time a new attribute is encountered, it is added in the configuration file in a "unsorted" group.
A UI allowing the user the move attributes between groups.
The alphabetical order is quick and simple. However, it can leads to harder reading when the number of attributes is important. For example,
FontSize
andTextAlignment
have a close relationship, but can be few attributes (lines) away.Here are the different groups, and their ordering, proposed.
Pros:
Cons:
Questions:
Your feedback is welcome.
The text was updated successfully, but these errors were encountered: