Results 1 to 4 of 4

Thread: Understand the diffrece between extjs and touch

  1. #1
    Sencha User
    Join Date
    Feb 2012
    Vote Rating

    Default Understand the diffrece between extjs and touch

    Hi. I written Lots of code using ExtJS 4.0.7 these days
    If I want my apps to run on mobiles as well how difficult is it to move to sencha touch?
    What are the diffrences?

  2. #2
    Sencha Premium User mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Gainesville, FL
    Vote Rating


    There isn't too much difference. You use the config object quite a bit and there are some syntax differences but the feel of the two is very similar.
    Mitchell Simoens @LikelyMitch
    Modus Create, Senior Frontend Engineer
    Need any sort of Ext JS help? Modus Create is here to help!

    Check out my GitHub:

  3. #3
    Sencha User
    Join Date
    May 2012
    Blumenau - Brazil
    Vote Rating

    Default Differences between ExtJS and Sencha Touch


    Why ExtJS and Sencha Touch have different cores?
    An example is the getHtml method defined in Ext.dom.Element.

    el.getHTML(); // I guess it's wrong, in the guides (!/guide/class_system) is written: use getHtml instead of getHTML

    Sencha Touch
    el.getHtml(); // I guess it's right

    Jlio Csar Batista - blog - twitter
    Web Developer

  4. #4
    Sencha Premium User suzuki1100nz's Avatar
    Join Date
    Apr 2011
    New Zealand
    Vote Rating



    There are a lot of differences, that depending on the complexity of your application can result in a lot of rework to translate it into the Touch framework. So much so in fact some community members have simply massaged their ExtJS apps to run on tablets (primarily for use on the tablet - not mobile as this requires a completely different UI interaction with the reduced screen real estate).

    Some differences that essentially have stopped us using shared UI code between Touch and ExtJS:
    (some simple stuff we fixed with overrides and im sure Sencha will address in the future)

    - Config object is the big difference with generated setters and getters at run-time in Touch
    For us to use shared code between the frameworks we had to ensure we used setters and getters and added the accessors via our extensions to the ExtJS framework

    - element access in ExtJS - el and getEl no such thing in touch, touch has element
    Create an override and add the function getEl() to touch and problem solved with shared code

    - Obviously ui components in Touch are lightweight-"ish" and don't have the bloat like ExtJS

    - No layout managers in touch (doLayout() doesn't exist. Touch layouts are simple vbox, hbox... and are handled by CSS3 not javascript. As a result its faster

    - We hit a difference in model and data store behavior between the 2 frameworks where Touch considers any model object with the same id or idProperty as essentially the same object and will update any datastore that has that object in it with a page load - Not so with ExtJS

    - A lot of missing features in touch with components that you get with ExtJS- Component validation (vtype), errors.....

    - Missing key components. Grid (Yes there is a ux for this but it should be rolled into the framework) We use grids in our Mobile and tablets apps...

    Ultimately Touch is very similar to ExtJS and you should understand it very quickly and get a feeling for some of the differences.

Posting Permissions

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