1. #11
    Ext User
    Join Date
    Jul 2007
    Location
    Florida
    Posts
    9,996
    Vote Rating
    5
    mjlecomte will become famous soon enough mjlecomte will become famous soon enough

      0  

    Default


    FYI, a 3.x compatible StatusBar was checked into svn today.

  2. #12
    Sencha User
    Join Date
    Mar 2009
    Posts
    356
    Vote Rating
    0
    koko2589 is on a distinguished road

      0  

    Default


    Quote Originally Posted by mjlecomte View Post
    FYI, a 3.x compatible StatusBar was checked into svn today.
    wehre to see demo??
    my ext js site
    http://www.itoto4.com/

  3. #13

  4. #14
    Sencha User
    Join Date
    Mar 2009
    Posts
    356
    Vote Rating
    0
    koko2589 is on a distinguished road

      0  

    Default


    Quote Originally Posted by mjlecomte View Post
    It's available in svn.
    do hve svn for free? they say to buy do you wont israeli mony?
    my ext js site
    http://www.itoto4.com/

  5. #15
    Sencha User
    Join Date
    Aug 2007
    Posts
    44
    Vote Rating
    0
    cherbert is on a distinguished road

      0  

    Default


    The removal of StatusBar seems like a stupid decision. Would it really do much harm to have kept it in the core?

    So I see Ext.StatusBar is not even in the API docs now. So then... why is it listed in the Samples pages? And why does it now reference as Ext.ux.StatusBar in the samples source?

    So if I understand correctly... Ext.ux is a User Extension right? Yet it is now part of the 3.0 final release? Can I just use it by changing my existing 2.0 apps to reference Ext.ux.StatusBar now?

    All very confusing... They should have just left it alone.

  6. #16
    Sencha Premium Member
    Join Date
    Jul 2007
    Posts
    256
    Vote Rating
    1
    brookd is on a distinguished road

      0  

    Default


    ux is the namespace for user extensions. They initially dumped the status bar from the core, but it was later replaced with a ux (user extension) that has the same functionality. You should be able to include the new code and just change one line of code to use the new ux class.

    It was dumped to keep the size of the library down which is a good thing. I was upset a little at first two, but I believe the ux version is the same...

  7. #17
    Ext User
    Join Date
    May 2009
    Posts
    12
    Vote Rating
    0
    kaeptn is on a distinguished road

      0  

    Default


    Quote Originally Posted by brookd View Post
    It was dumped to keep the size of the library down which is a good thing. I was upset a little at first two, but I believe the ux version is the same...
    The weight it would have added would have been negligible IMHO.

    And UX does not only mean a namespace but more importantly no documentation. So now you must rebuild something with standard methods which formerly was an object by itself with it's own functionality.