API Component / Keyword Conventions

[tiredoftry]

Hello,

I have been going through some of the samples in the Touch 2.x documentations and am finding a lot of the code in Touch 1.x format. Some of the changes are minor, however, it would be much easier if there was a list of the conventions used for the API and components.

Example Ext.Application from Touch 1 is not Ext.application in Touch 2 - Note the lowercase 'a' in application.

This does not carry through, however, as Ext.Create is an uppercase and components are formatted such as TabPanel.

Is there any documentation which explains the convention methodology of the API? This would make it much easier when converting the examples (and any created applications) from Touch 1 to Touch 2.

Thank you for the time,
Randy Friend

[rdougan]

Functions should always have a lowercased first letter and then be capitalized. Like Ext.application, Ext.create, and Ext.define.

Class names however have a capitalized first letter. So Ext.tab.Panel, Ext.Container, Ext.field.Text, and so on.

If you find any inconsistencies with this, please do let us know.

[tiredoftry]

I also notice that 'multinamed' components are upper on both segments such as TabPanel.

I do appreciate your assistance on the casing of object. Do you know when the documentation in 2.0 will be fully updated with just 2.0 examples?

Randy

[oddz]

Take a look at this section of the docs.

[rdougan]

I also notice that 'multinamed' components are upper on both segments such as TabPanel.

I do appreciate your assistance on the casing of object. Do you know when the documentation in 2.0 will be fully updated with just 2.0 examples?

Randy

That will happen before the 2.0 GA release.