Results 1 to 5 of 5

Thread: API Component / Keyword Conventions

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Sencha User
    Join Date
    Oct 2010
    Posts
    2
    Vote Rating
    0
      0  

    Question Answered: API Component / Keyword Conventions

    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

  2. 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.

  3. #2
    Sencha User rdougan's Avatar
    Join Date
    Oct 2008
    Posts
    1,159
    Answers
    93
    Vote Rating
    7
      0  

    Default

    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.
    Sencha Inc.
    Robert Dougan - @rdougan
    Sencha Touch 2 and Ext JS 4 Core Team Member, SASS/Theming Wizard.

  4. #3
    Sencha User
    Join Date
    Oct 2010
    Posts
    2
    Vote Rating
    0
      0  

    Default Thank you for the update

    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

  5. #4
    Sencha User
    Join Date
    Sep 2011
    Posts
    125
    Answers
    1
    Vote Rating
    0
      0  

    Default

    Take a look at this section of the docs.

  6. #5
    Sencha User rdougan's Avatar
    Join Date
    Oct 2008
    Posts
    1,159
    Answers
    93
    Vote Rating
    7
      0  

    Default

    Quote Originally Posted by tiredoftry View Post
    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.
    Sencha Inc.
    Robert Dougan - @rdougan
    Sencha Touch 2 and Ext JS 4 Core Team Member, SASS/Theming Wizard.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •