Extjs 4 is comming

Any plan on the admin ui?

It will eventually, but not in almost ready 2.1 release.

Moving to Ext4 is not a trivial upgrade. The entire API of ExtJS has been completely rewritten in Ext4. This means:

- All the CSS will have to be redone in the mgr
- All the base JS MODExt classes will have to be rewritten
- All the documentation on building Custom Manager Pages (CMPs) will have to be updated
- All the MODExt documentation will have to be updated
- All the tweaks to fix issues with ExtJS in the mgr will have to be reviewed, as well as all the special implementations that MODExt does to enable more content-editing abilities (such as the element properties grid) will have to be rewritten and reviewed.
- All Extras with CMPs will have to be rewritten

Not to mention, this cannot be done on a patch release (such as 2.1.1), since it would break all existing Extras. It will have to wait for 2.2, 2.3, 2.4, or 3.0.

It’s not trivial, and will require a ton of work. The cost/benefit of it right now is not worth it at the moment. (Especially with it still in beta.)

So does it makes sense to stay with EXTjs or is it
worth trying with jQuery?

ExtJS definitely makes sense to stick with for the power-user version of the Manager.

jQuery is the most popular library, but also far less powerful and flexible than ExtJs.
Just the json store facility of ExtJS justify to stay with it.

btw, going to ExtJS 4 will definitively not be trivial but most 3.x applications are going to be compatible with the help of a dedicated compatibility layer that will be provided by the Ext team for the 4.0 release.

Quote from: lossendae at Apr 03, 2011, 08:30 PM

jQuery is the most popular library, but also far less powerful and flexible than ExtJs.
Just the json store facility of ExtJS justify to stay with it.

How does YUI3 compare feature wise?
What are its downfalls?
Quote from: rthrash at Apr 03, 2011, 06:02 PM

ExtJS definitely makes sense to stick with for the power-user version of the Manager.

Would either jQuery or YUI3 be more suitable for a cut down version of the manager?

Quote from: allanb at Apr 04, 2011, 03:10 AM

Quote from: lossendae at Apr 03, 2011, 08:30 PM

jQuery is the most popular library, but also far less powerful and flexible than ExtJs.
Just the json store facility of ExtJS justify to stay with it.

How does YUI3 compare feature wise?
What are its downfalls?
Quote from: rthrash at Apr 03, 2011, 06:02 PM

ExtJS definitely makes sense to stick with for the power-user version of the Manager.

Would either jQuery or YUI3 be more suitable for a cut down version of the manager?

The revo manager should run on extJS (but on v4 as soon as possible) as it allows rapid development and is much faster to develop than jQuery/YUI/mootools.
Mark-H is developing HandyMan, a lightweight manager for mobile devices built on jQuery touch. Maybe you can user this?

YUI and Ext have the same root (the original ExtJS was based on Yui-ext).
They use similar code structure and i think it is a matter of preference which one you prefer (both are rich, powerful and flexible). I find the documentation of ExtJs better.

Feature-wise, i think that ExtJS is much more complete, there are plenty of examples and user submitted examples.
It’s not that YUI can’t do the same, it’s just that the Ext team is more pro active on showing how to acheive great functionalities with their framework.

For a cut down manager, jQuery would be enough, for a mobile version,a s stated above jQuery touch is good. I would have used Sencha touch which have similar structure to ExtJS 4 (actually, it’s the over way around, ExtJS 4 is going to have similar structure to Sencha Touch).
Sencha Touch and jQuery Touch are developped by the same people.

Thanks lossendae, for this..

btw, going to ExtJS 4 will definitively not be trivial but most 3.x applications are going to be compatible with the help of a dedicated compatibility layer that will be provided by the Ext team for the 4.0 release.

I was worried about the extras... and the need to rewrite all of them,
but if there is going to be a compatibility layer, then it is OK.

We need to start writing more Extras, not just Shaun, and I think this
can be a stopper because are people going to learn how to make them using
Extjs 3 and then have to do it all over again using Extjs 4 (that is why
I suggested jquery, that and I have already seen everything Extjs does
done using jQuery et al (jqueryUI, jqueryTemplates, etc))