1. #1
    Ext JS Premium Member watrboy00's Avatar
    Join Date
    Aug 2007
    Location
    Minneapolis, MN
    Posts
    473
    Vote Rating
    0
    watrboy00 is on a distinguished road

      0  

    Default Backwards compatibility (DEPRECATED)

    Backwards compatibility (DEPRECATED)


    Since we are in beta 3 (I believe) and this is a new framework with notes saying that things might change...should we already be seeing this?

    // Backwards compatibility (DEPRECATED)
    Ext.Container.LAYOUTS = Ext.layout.TYPES;
    Eric Berens
    Intranet Systems Manager @ Best Buy
    You should follow me on twitter here.

  2. #2
    Ext JS Premium Member watrboy00's Avatar
    Join Date
    Aug 2007
    Location
    Minneapolis, MN
    Posts
    473
    Vote Rating
    0
    watrboy00 is on a distinguished road

      0  

    Default


    // Backwards compatibility with desktop
    Ext.CompositeElementLite = Ext.CompositeElement;

    It's a mobile platform...who cares about the desktop!
    Eric Berens
    Intranet Systems Manager @ Best Buy
    You should follow me on twitter here.

  3. #3
    Sencha User Jamie Avins's Avatar
    Join Date
    Mar 2007
    Location
    Redwood City, California
    Posts
    3,661
    Vote Rating
    18
    Jamie Avins is a jewel in the rough Jamie Avins is a jewel in the rough Jamie Avins is a jewel in the rough

      0  

    Default


    We're trying to keep some level of familiarity across the platforms, but this one in particular will probably go away.

  4. #4
    Ext JS Premium Member watrboy00's Avatar
    Join Date
    Aug 2007
    Location
    Minneapolis, MN
    Posts
    473
    Vote Rating
    0
    watrboy00 is on a distinguished road

      0  

    Default


    Oh for sure. I think there should be HUGE similarities between the two. I just don't think there should be backward compatibility all over the place if there wasn't a previous version to be backward compatible with. Just want to see that the framework isn't being bloated for no apparent reason.
    Eric Berens
    Intranet Systems Manager @ Best Buy
    You should follow me on twitter here.

  5. #5
    Ext JS Premium Member watrboy00's Avatar
    Join Date
    Aug 2007
    Location
    Minneapolis, MN
    Posts
    473
    Vote Rating
    0
    watrboy00 is on a distinguished road

      0  

    Default


    These are the other ones...

    //backwards compatibility
    Ext.data.DataProxy = Ext.data.Proxy;

    //[deprecated 5.0]
    Ext.ns('Ext.data.Record');

    //Backwards compat
    Ext.data.Record.id = Ext.data.Model.id;
    //[end]

    //backwards compatibility, remove in Ext JS 5.0
    Ext.data.HttpProxy = Ext.data.AjaxProxy;

    //backwards compatibility, will be deprecated in 5.0
    this.nocache = this.noCache;

    // backwards compat, convert idPath or id / success
    // DEPRECATED - remove this in 5.0
    Ext.applyIf(config, {
    idProperty : config.idPath || config.id,
    successProperty: config.success
    });

    // backwards compat
    Ext.data.SimpleStore = Ext.data.ArrayStore;

    //backwards compatibility - deprecate in next major release
    this.label = this.label || this.fieldLabel;
    Eric Berens
    Intranet Systems Manager @ Best Buy
    You should follow me on twitter here.

  6. #6
    Ext JS Premium Member stever's Avatar
    Join Date
    Mar 2007
    Posts
    1,407
    Vote Rating
    6
    stever will become famous soon enough stever will become famous soon enough

      0  

    Default


    Well, I imagine it is because a site's data structure is often built on top of Ext classes. To provide a desktop and a mobile UI, one can switch out the UI layer to the appropriate one, but much of how your data works will be the same and so ought to be the underlying layers where appropriate.

  7. #7
    Ext JS Premium Member watrboy00's Avatar
    Join Date
    Aug 2007
    Location
    Minneapolis, MN
    Posts
    473
    Vote Rating
    0
    watrboy00 is on a distinguished road

      0  

    Default


    I'm sorry am not tracking what you say...

    I think it is good design that your back end data structure should remain consistent whether you are display it on a desktop browser or mobile browser. You *should* just have to switch out the UI. Now where I am not following is how the back end data structure relates to the front end UI and the client side lib having to deal with backwards compatibility. When you swap the desktop UI for the mobile one you would also have to switch the associated client side code to make the UI functional. You wouldn't be able to use Ext Core/3.x lib on a mobile device with much success much like you wouldn't be able to use the Touch lib on a desktop browser. Sure they might work but probably not as expected or efficient.

    My main point was because most of the mobile UI lib will not share much, if any, components from the desktop version why are we maintaining backwards compatibility already at this point. There won't be any cross over. Since Touch v1.0 RTM hasn't been released what's the point? It's in beta still. Things change daily I'm sure. I would say starting after 1.0 is released backwards compatibility should be managed. Until then seems pointless.
    Eric Berens
    Intranet Systems Manager @ Best Buy
    You should follow me on twitter here.

  8. #8
    Sencha User Jamie Avins's Avatar
    Join Date
    Mar 2007
    Location
    Redwood City, California
    Posts
    3,661
    Vote Rating
    18
    Jamie Avins is a jewel in the rough Jamie Avins is a jewel in the rough Jamie Avins is a jewel in the rough

      0  

    Default


    Some of the code base is being developed in parallel with Ext 4.0 and your seeing parts moving back and forth between the code bases. We'll get them straightened out as things become more solidified.

  9. #9
    Sencha User
    Join Date
    Mar 2007
    Location
    Haarlem, Netherlands
    Posts
    1,243
    Vote Rating
    10
    TommyMaintz will become famous soon enough TommyMaintz will become famous soon enough

      0  

    Default


    Almost all of the examples you found are within the data package which is the only piece of code that is shared one on one with Ext 4.0. This means that if you write an app for desktop and mobile, you can use all the same stores, models and validations for both versions of the app.

    You just have to switch out the UI components.

    We will investigate if any of them can be removed though, like label -> fieldLabel and CompositeElementLite. The others are all data related.

Similar Threads

  1. Replies: 1
    Last Post: 2 Feb 2010, 10:39 AM
  2. Backwards compatibility (GridPanel)?
    By dekely in forum Ext 2.x: Help & Discussion
    Replies: 7
    Last Post: 24 Aug 2009, 8:01 AM
  3. Ext.MessageBox.wait params not inline with 'standard' or backwards
    By jay@moduscreate.com in forum Ext 1.x: Bugs
    Replies: 2
    Last Post: 9 Jul 2007, 8:22 AM
  4. YAHOO.ext.DomHelper backwards?!
    By jay@moduscreate.com in forum Ext 1.x: Help & Discussion
    Replies: 5
    Last Post: 1 Dec 2006, 1:49 PM
  5. Sort order backwards??
    By tryanDLS in forum Ext 1.x: Bugs
    Replies: 8
    Last Post: 10 Nov 2006, 7:27 AM

Thread Participants: 3