1. #31
    Sencha User
    Join Date
    May 2010
    Posts
    53
    Vote Rating
    0
    dukeyboy is on a distinguished road

      0  

    Default


    The main thing is that Sencha needs to polish polish polish polish and just keep on polishing until ext shines like a diamond in every possible way.

    I am a refugee from Adobe Flex. Adobe builds Flex stuff and then say "it's finished!" and then it moves on to build the next shiny thing. Adobe does not polish, improve, polish, improve until Flex is best in class. I will never design another Flex app again. It is somewhat disturbing to see Sencha building new and shiny things when clearly ext needs lots and lots and lots more polishing. Animation software and all sorts or other tangents are clearly a drain on resources and focus, which should be going into the core product. What is the CTO of Sencha thinking? I am hoping that Sencha will continue to fix and improve and polish ext until it is the very best in its class, and then polish some more.

    The message has to be continually hammered that the documentation of ext remains woefully inadequate, although I and others continually say it, the documentation situation has not been fixed.

    For ext to succeed, Sencha has to stop all these distracting side projects like animation, fix the ongoing problem with documentation, and continue to polish ext. Fortunately, it appears at this stage that Sencha/Ed Spencer is continuing to work on ext, whether or not they maintain that focus remains to be seen. I'm hoping for ext to be a viable alternative to Adobe Flex, not yet another half baked, poorly documented, average product with the minimum feature set required to just get the job done.

    Did I mention that the ext documentation remains terrible?

  2. #32
    Sencha - Community Support Team edspencer's Avatar
    Join Date
    Jan 2009
    Location
    Palo Alto, California
    Posts
    1,939
    Vote Rating
    9
    edspencer is a jewel in the rough edspencer is a jewel in the rough edspencer is a jewel in the rough

      0  

    Default


    Quote Originally Posted by dukeyboy View Post
    The main thing is that Sencha needs to polish polish polish polish and just keep on polishing until ext shines like a diamond in every possible way.
    I couldn't agree more.

    Quote Originally Posted by dukeyboy View Post
    Animation software and all sorts or other tangents are clearly a drain on resources and focus, which should be going into the core product.
    The team working on Animator was recruited specifically to work on that product, it hasn't taken any focus away from Ext JS and Sencha Touch.

    Quote Originally Posted by dukeyboy View Post
    it appears at this stage that Sencha/Ed Spencer is continuing to work on ext, whether or not they maintain that focus remains to be seen. I'm hoping for ext to be a viable alternative to Adobe Flex, not yet another half baked, poorly documented, average product with the minimum feature set required to just get the job done.
    There is a dedicated team working solely on Ext JS, as there is for Touch. That won't change and our focus won't blur. As we grow as a company we are indeed adding projects but we're adding people faster and still actively recruiting more developers. I strongly believe we're getting much better delivering our goals with the last few releases. We're still far from perfect however

    Quote Originally Posted by dukeyboy View Post
    Did I mention that the ext documentation remains terrible?
    A while back I listed documentation as one of the things Ext JS 4 had to do better at. While we're nowhere near done yet, there is now close to 3x more API documentation than there ever used to be (as measured by total word count), plus 12 completely new guides and many more examples. I hope that demonstrates that we are very serious about providing excellent documentation, and will continue to improve it. We have a small team dedicated to documentation and we update it at least every week
    Ext JS Senior Software Architect
    Personal Blog: http://edspencer.net
    Twitter: http://twitter.com/edspencer
    Github: http://github.com/edspencer

  3. #33
    Touch Premium Member
    Join Date
    Aug 2007
    Posts
    21
    Vote Rating
    0
    vamsee.k is on a distinguished road

      0  

    Default


    I have been following Ext JS development for almost 4 years (right from the days when it was called yui-ext). Along the way I have developed applications that I had to upgrade from 1.x to 2.x to 3.x. For the last few months I was working on a fairly complex single page application that uses lots of grids, tab panels, accordions, etc. I started out with Ext 3.2, then used 3.3. Now I upgraded it to Ext 4.0.2 (planning to move to ext 4.0.4 next week). Before I started the migration to Ext 4.x, I did a complete study of the issues and made a plan for the upgrade. I had to prototype a few of the complex screens (using locking and infinite scrolling) upfront so that I don't hit any surprises. The documentation is not complete, however I am more used to reading the source code than the documentation, so I didn't face any major problems because of lack of documentation. Overall, my observation is that it is worth upgrading to Ext 4.x, however it requires careful planning and prototyping to avoid surprises.

    I completely support Sencha in deciding to overhaul the framework - the new architecture, class loading, charts, Ext.Loader, data package, etc are just the right foundation for developing web applications of the future. The code base is very well structure and it takes very high quality team to deliver such code (especially in JavaScript). I am eagerly waiting for Sencha Touch 2.0 which would share the platform code base with Ext JS 4.x.

    Overall, I would say that Ext JS 4.x is in the right direction and I am confident of deploying my application to production with the current build (though my release is 3 months away, so I am hoping to get some more builds from Sencha before my release :-) ). My advice to people who want to upgrade complex apps to 4.x is this - if you can invest time in prototyping and identifying the bottlenecks, then you can upgrade now, else wait for 4.1 (even then you need to invest time in prototyping, but will face fewer bottlenecks).

  4. #34
    Sencha User
    Join Date
    May 2010
    Posts
    53
    Vote Rating
    0
    dukeyboy is on a distinguished road

      0  

    Default


    It's because ext is so great that it is worth commenting on these things.

    It looks great and works great and is getting better all the time.

    No competing product can hold a candle to ext.

  5. #35
    Sencha User
    Join Date
    May 2010
    Posts
    53
    Vote Rating
    0
    dukeyboy is on a distinguished road

      0  

    Default


    It's also worthing praising the ext team for actively participating in these forums and for maintaining polite and well mannered attitude.

  6. #36
    Sencha User
    Join Date
    Sep 2010
    Location
    Norcross, GA
    Posts
    68
    Vote Rating
    1
    deskwideweb is infamous around these parts

      0  

    Default


    Quote Originally Posted by edspencer View Post
    A few thoughts: <snipping 1, 3 & 4>

    2) Sencha did not acquire Ext JS, we simply renamed the company. The company and the product both used to be called Ext JS - once we created another product that no longer made sense. There is no conspiracy theory or external purchaser, it's just a name.
    Whatever the case, as soon as ExtJS became Sencha, most of the focus seemed to go over to Sencha Touch.

    Also, something that's not been addressed, that I've repeated here twice. Ext3 was not built with IE9 and/or FF 4/5 in mind (we are fixing all sorts of IE9 issues in an Ext3 app). And it doesn't seem Ext4 was built with IE7 in mind. So what then, do we need two different frameworks?

  7. #37
    Sencha User
    Join Date
    Mar 2007
    Posts
    7,854
    Vote Rating
    4
    tryanDLS is on a distinguished road

      0  

    Default


    Also, something that's not been addressed, that I've repeated here twice. Ext3 was not built with IE9 and/or FF 4/5 in mind (we are fixing all sorts of IE9 issues in an Ext3 app). And it doesn't seem Ext4 was built with IE7 in mind. So what then, do we need two different frameworks?
    I'm not seeing very much in the way of bug reports/test cases to validate this statement. Ext 3.4 was released to address IE9.

  8. #38
    Sencha User
    Join Date
    Sep 2010
    Location
    Norcross, GA
    Posts
    68
    Vote Rating
    1
    deskwideweb is infamous around these parts

      0  

    Default


    Quote Originally Posted by tryanDLS View Post
    I'm not seeing very much in the way of bug reports/test cases to validate this statement. Ext 3.4 was released to address IE9.
    Fair enough, we will give Ext 3.4 a shot

  9. #39
    Sencha User
    Join Date
    May 2008
    Posts
    79
    Vote Rating
    0
    pdchapin is on a distinguished road

      0  

    Default Porting

    Porting


    Until there's a simple, well documented way of moving to 4, I see no reason to put myself through the effort. What conceptually bothers me is that the product is taking the tact of a lot of annoying packages of saying we know more about what you're doing than you do. Why, for instance, is it screwing with my body tag. I don't want you to be messing with parts of my application that don't use EXTjs.