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.
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...
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.
Originally Posted by mjlecomte
Reply With Quote
my ext js site