1. #1
    Ext JS Premium Member
    Join Date
    Jan 2011
    Posts
    2
    Vote Rating
    0
    kevinlonigro is on a distinguished road

      0  

    Question Class System relative to Non-Component Creation

    Class System relative to Non-Component Creation


    Is the new class system only for UI type Components or should it be used anytime the "new" keyword would be used; for example in creating a new Model, Store, etc. would it be advisable to use "Ext.define" instead of the "new" keyword instantiation.

    It appears that the examples for the new Data package still use the "new" keyword in creating respective classes and therefore defining the namespace with Ext.ns would still be required.

    Any thoughts on best practices.

  2. #2
    Ext JS Premium Member
    Join Date
    Sep 2007
    Posts
    29
    Vote Rating
    0
    xonmac is on a distinguished road

      0  

    Default


    Ext.define is not meant as a replacement for "new". Ext.define defines a class, while "new" creates an instance of a class.
    Netzke: Ruby on Rails and Ext JS component framework.

  3. #3
    Ext JS Premium Member
    Join Date
    Jan 2011
    Posts
    2
    Vote Rating
    0
    kevinlonigro is on a distinguished road

      0  

    Default


    Thanks for the reply. I don't know why I was thinking instantiation when I should have been thinking definition as it appears Ext.define is being preferred over Ext.extend.

Similar Threads

  1. How To switch Development System to Production System
    By extjs_mahendra in forum Ext 3.x: Help & Discussion
    Replies: 4
    Last Post: 22 Dec 2009, 8:47 AM
  2. application design, component creation and efficiency
    By ry.extjs in forum Community Discussion
    Replies: 119
    Last Post: 21 Jun 2009, 10:39 AM
  3. Replies: 6
    Last Post: 18 Dec 2008, 3:55 PM
  4. Custom Component Creation
    By bhardwajkumar_pravesh in forum Ext 2.x: Help & Discussion
    Replies: 1
    Last Post: 4 Nov 2008, 7:44 AM

Thread Participants: 1

Tags for this Thread