XSD Code Standards Consistency

[modnaut]

I was looking through the xsd, here are my thoughts, let's do some clean up for consistency.

• Make sure everything is in true camel case. ie: StringCD - > StringCd.
• Let's spell out as much as we can. ie: icnCls -> iconClass. itemCls -> itemClass
• The following abbreviations are fine: min, max, msg...
• I don't know what these mean: tdAttrs / trAttrs..? Lets spell them out.
• Lastly, lets use good descriptions. ie: x / y.... can we add something else? Like xAxis or yAxis? I know it may seem clear now but as we move farther along it may get muddled so lets avoid using single characters unless it is only truly necessary.
• I like 'parm' for 'parameter' instead of 'param'. If this doesn't cause an issue, I think we should use 'parm' always.

[modnaut]

Per Danny --

I've tried very hard to keep all attribute names matching the configuration properties for the underlying ExtJS components that are created. Not only does it keep the XSL very clean, but it makes it very easy to look up how an attribute works because it's in the Sencha docs at docs.sencha.com. If you want to move away from that we can, I just thought this was cleaner and easier to maintain because the documentation is effectively already written for us.

The exception to this is stringCD, I created that before we decided on a standard, I can change it.

[modnaut]

Ok, keep it clean and matching the configuration properties as needed. Can you add in comments to help clarify situations where it may not be necessarily clear based on the abbreviations or format?

Yes!! Please change stringCD to stringCd. Thanks!

[dannycohn]

I justed pushed the change from stringCD to stringCd