Page 3 of 3 FirstFirst 123
Results 21 to 29 of 29

Thread: Question on modern vs classic toolkits

  1. #21
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985
    Answers
    506

    Default

    As far as I know, greater parity between the toolkits is actively being worked on by Engineering and continues to be a goal for upcoming releases.

  2. #22
    Sencha Premium Member valio's Avatar
    Join Date
    Jan 2014
    Posts
    203
    Answers
    8

    Default

    If I open http://docs.sencha.com/extjs/ now and click on "API" I'm getting redirected to the ExtJS Docs for the modern toolkit.
    Thus I assume that Sencha is already planing on "phasing out" the classic toolkit, once feature parity is achieved and is nudging new developers to the modern toolkit.

  3. #23
    Sencha User dongryphon's Avatar
    Join Date
    Jul 2009
    Location
    Kansas
    Posts
    1,748
    Answers
    55

    Default

    There is no plan to phase out the Classic Toolkit at this time. The way to think about the focus on the Modern Toolkit is that we are working to ensure your the choice of toolkit is based on browser requirements and existing code... instead of by feature set they provide (as is often the case today). Also, the choice of Modern or Classic API view is remembered so which one is displayed first should track which toolkit you are using.
    Don Griffin

    "Use the source, Luke!"

  4. #24

    Default

    Sorry to dig up this thread guys, but I'm wondering when we expect to see feature parity between the two? Also, if Modern has the same widgets as Touch, what are the differences between the two?

    Thanks in advance.

  5. #25
    Sencha User dongryphon's Avatar
    Join Date
    Jul 2009
    Location
    Kansas
    Posts
    1,748
    Answers
    55

    Default

    The 6.2 release added considerably to the Modern Toolkit. We are pushing hard now on another large feature update to Modern for the second half of next year (as we announced at SenchaCon).

    As with 6.2, there will be new features in Classic as well, but there won't be any significant new things that are Classic only, for example.

    The biggest differences between Ext JS Modern Toolkit and Sencha Touch is that Ext JS is a multi-input framework, whereas Sencha Touch was touch-only (no real, direct keyboard or mouse support). Also, the Touch Grid is much improved in Ext JS Modern, and the MVC/VM feature set is well beyond what was in Sencha Touch. There are lots more of course, but best to see What's New.
    Don Griffin

    "Use the source, Luke!"

  6. #26

    Default

    Thank you for clarifying, I really appreciate it.

    Quote Originally Posted by dongryphon View Post
    The 6.2 release added considerably to the Modern Toolkit. We are pushing hard now on another large feature update to Modern for the second half of next year (as we announced at SenchaCon).

    As with 6.2, there will be new features in Classic as well, but there won't be any significant new things that are Classic only, for example.

    The biggest differences between Ext JS Modern Toolkit and Sencha Touch is that Ext JS is a multi-input framework, whereas Sencha Touch was touch-only (no real, direct keyboard or mouse support). Also, the Touch Grid is much improved in Ext JS Modern, and the MVC/VM feature set is well beyond what was in Sencha Touch. There are lots more of course, but best to see What's New.

  7. #27
    Ext JS Premium Member
    Join Date
    Dec 2010
    Posts
    2

    Exclamation How esasy is easy enough?

    you say it will be easy enough to change to modern later but what does that entail? Days or months? I know if depends upon the number of components but we are currently moving from 4 thru 5 to get to 6 and will need legacy browser support but don't want to spend another 6 months to move to modern. Thanks for the response in advance.


    Quote Originally Posted by suzuki1100nz View Post
    The ultimate goal would be a full merge of the toolkits.
    The barrier to this right now is the component toolkit differences and the need to support legacy browsers (Yes a lot of the community have customers that need this).

    My expectation is that once legacy browser support is no longer required (thats going to be a log while off) then the classic toolkit will be dropped after the usual support period - Those with existing classic applications should be able to easily rebuild there classic apps into modern.

    At the end of the day the modern toolkit is the full HTML5 CSS3 toolkit and those that aren't hamstrung by legacy support will want to be using this toolkit as it will be far more performant on smart phone, tablet and desktop for that matter.

    I suspect once component parity is achieved across the two toolkits the majority of developers will be using the modern toolkit and as I said it is easy enough to swap toolkits later if you are starting in classic right now because you need the richer component set.

  8. #28

    Default

    Quote Originally Posted by Ekontos View Post
    you say it will be easy enough to change to modern later but what does that entail? Days or months? I know if depends upon the number of components but we are currently moving from 4 thru 5 to get to 6 and will need legacy browser support but don't want to spend another 6 months to move to modern. Thanks for the response in advance.
    Is there any update on this question?
    I have the same query

    Regards,
    Charles

  9. #29
    Sencha Premium User alexander.urban's Avatar
    Join Date
    Nov 2013
    Posts
    324
    Answers
    9

    Default

    Quote Originally Posted by Charles_Gamble View Post
    Is there any update on this question?
    I have the same query

    Regards,
    Charles
    I am not really sure why you want to move to a modern-only app. Modern sucks on desktop, and classic sucks on smartphones.

    Moving from classic to modern IMO is a major rewrite of your application. Every user extension has to be ported, many component definitions have to be slightly modified, and everything has to be tested.

    Of course, you can keep the stores and models, which means that if you have done a good job taking apart stores and views, you can reuse maybe 30% of your application.

    By the way, moving from classic to modern means, first you move to universal (universal = classic + modern), and then you drop classic.

    So you could as well move to universal and then decide support both frontends.

Page 3 of 3 FirstFirst 123

Similar Threads

  1. More modern themes?
    By basememara in forum Ext: Discussion
    Replies: 1
    Last Post: 2 Dec 2011, 11:02 AM
  2. should GXT 2.0 look the same on all modern browsers?
    By jhudson888 in forum Ext GWT: Discussion
    Replies: 3
    Last Post: 17 May 2009, 10:44 AM
  3. Advantages of EXT j. over other Javascript toolkits
    By hihiren in forum Community Discussion
    Replies: 6
    Last Post: 14 Apr 2008, 4:28 AM
  4. extra node in tree - classic asp question
    By concep86 in forum Ext 2.x: Help & Discussion
    Replies: 6
    Last Post: 9 Feb 2008, 8:06 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •