1. #11
    Ext JS Premium Member
    Join Date
    Jan 2009
    Posts
    31
    Vote Rating
    1
    blakel is on a distinguished road

      0  

    Default


    Quote Originally Posted by mitchellsimoens View Post
    I have seen a lot of posts about people not having success with Ext JS 4 but I must say (and I'm not a core dev) that I do not see most of the bugs. I have not come across a problem that I couldn't fix myself.

    I think there are a few reasons:

    1) People with large 3.x apps haven't ported to 4.x because: a) Tons of APIs were broken so it's difficult and time consuming to migrate to 4.x b) The performance of 4.x is so bad that people have given up porting until the performance improves

    2) No one is starting large apps in 4.x because the performance is so bad

    3) 4.x probably works well (as in correct behavior, not performance) in the simplest cases but because of 1 & 2 anyone who would be pushing the library to get to the less obvious bugs isn't even developing against 4.x right now.

  2. #12
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    36,754
    Vote Rating
    828
    mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute

      0  

    Default


    Quote Originally Posted by blakel View Post
    I think there are a few reasons:

    1) People with large 3.x apps haven't ported to 4.x because: a) Tons of APIs were broken so it's difficult and time consuming to migrate to 4.x b) The performance of 4.x is so bad that people have given up porting until the performance improves

    2) No one is starting large apps in 4.x because the performance is so bad

    3) 4.x probably works well (as in correct behavior, not performance) in the simplest cases but because of 1 & 2 anyone who would be pushing the library to get to the less obvious bugs isn't even developing against 4.x right now.
    1. a) This should be expected when going to a new major release. I agree it would have been great to stick with how we have been doing things but do you not agree that sometimes it's good to take a leap into something? b) I cannot dispute that there are performance problems. Biggest culprit is IE with FF having some problems. IE shouldn't be that big of a surprise and FF has memory leaks. I'm not saying it's not Ext JS' fault, I'm saying the browsers need to also keep progressing in their own right. I have no performance hit with Chrome and yes, I have been creating lots of things, some of which are doing a lot of experimental stuff that takes the framework out of it's comfort zone.
    2. This is just not true. "No one" should be "Many" and just like other major releases Ext JS has gone through, there are problems at the beginning but they are worked through and improved. Since I have gone through this before I know to just keep pushing forward and performance will catch up.
    3. See my #2
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  3. #13
    Ext JS Premium Member
    Join Date
    Jan 2009
    Posts
    31
    Vote Rating
    1
    blakel is on a distinguished road

      0  

    Default


    Yes, sometimes it is necessary to break APIs. However it is frustrating when the API is broken is very subtle ways.

    An example off the top of my head is the "border" config option for Panels (it is probably inherited from a superclass, but I don't have the docs with me at the moment). In 3.4 it is a boolean and in 4.x it is a number. On top of that, last time I tried it doesn't even seem to have any effect. No matter what value you give it there still seems to be a border. I don't know if this is a bug or if it just works differently in 4.x. This leads to numerous visual problems when you had nested panels with "frame: true".

    I shouldn't have said "no one". I don't know what everyone else is doing. I do know that there are very serious performance problems with basic elements such as Tab Panels that are especially bad in IE8.

    Yes IE8 sucks and I wish we didn't have support it, but it's not like IE8 can't have good performance. IE8 works pretty well with an equivalent application written against 3.4.

    My main complaint is that it seems 4.0 was pushed out too early. As it stands any sufficiently complex application using 4.0 is unusable by ~50% of global users (IE8 and lower).

  4. #14
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    36,754
    Vote Rating
    828
    mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute

      0  

    Default


    Looks like the docs are wrong here... I set mine to false all the time and it adds 4 new CSS classes to the body that remove the borders but IMO the expected behavior is to not have border around entire component. IMO for border, you should do this in CSS but this behavior shouldn't have changed going from 3.x to 4.x so I will create a test case to make sure. I'm sure there are other changes but it's part of the migration, IMO.

    Trust me, if it was feasible we would drop IE altogether. I think Nige found an extra layout call in TabPanel which has helped the tab switching. This was one of the bugs that I would say would be worked through. Will let you know if I am remembering correctly on this if he gets back to me or I find it in Jira.

    Yes, I have heard many people say that 4.x was pushed out too early. I wasn't part of the decision or discussion so I am an outsider but yet kind of an insider. What I saw was that for the testing that we did, it looked good. We can't test in every scenario, I find bugs when I am developing with 4.x so this is why we had a developer preview process so that we could get a feel for what kind of things need to be worked on and maybe we wouldn't have released it if we knew about the performance problems (idk, I am not part of that decision).

    I understand people's frustrations, I do. When 3.x came out I was frustrated with certain bugs but now that I see what actually goes on behind the scenes I am confident that they will decrease as time goes on.
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  5. #15
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    36,754
    Vote Rating
    828
    mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute

      0  

    Default


    Got ahold of Nige and he said it affected it a lot and that the fix is in 4.0.5 which is the current version we are developing against. Another guy states that 4.0.5 also had some improvements on the render selectors. 4.1 will have Grid performance improvements and somewhere there is still some room for improvements on the render selectors. So they are making great strides and things are getting better.
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  6. #16
    Ext JS Premium Member
    Join Date
    Jan 2009
    Posts
    31
    Vote Rating
    1
    blakel is on a distinguished road

      0  

    Default


    This is all good news. I don't doubt that the kinks will get worked out. It's just frustrating to have to explain to the higher ups why we spent thousands of dollars on an upgrade license but then when the final version actually came out we can't use it yet.

    Don't get me wrong. I love ExtJS, I think it is brilliant piece of software and wish I was the one that thought of it . It is just a jarring experience working with 2.x and then 3.x and things going so smoothly and then trying to move to 4.x where we can't use it at all because of the performance problems.

  7. #17
    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 mitchellsimoens View Post
    Thank you for your words and I would agree. I have been using Ext JS since the beginning and just this year been hired on at Sencha so I have been the complainer many times before. This also tells me that releasing a new major version has always have problems
    ExtJS4 is not a "new major version". It's a new framework. Ext3 is not especially compatible with FF4/5 and IE9 and Ext4 is not especially compatible with FF3 and IE7/8. Add lack of backward compatibility, and if Sencha isn't working furiously to ensure backward compatibility and compatibility with all major browsers in a near-future major version (4.5? 5.0), then I see Ext adoption going downhill fast. Indeed I suspect that with the acquisition of Ext by Sencha this was the plan all along: abandoning ExtJS, to focus on Sencha.

  8. #18
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    36,754
    Vote Rating
    828
    mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute

      0  

    Default


    Quote Originally Posted by blakel View Post
    This is all good news. I don't doubt that the kinks will get worked out. It's just frustrating to have to explain to the higher ups why we spent thousands of dollars on an upgrade license but then when the final version actually came out we can't use it yet.

    Don't get me wrong. I love ExtJS, I think it is brilliant piece of software and wish I was the one that thought of it . It is just a jarring experience working with 2.x and then 3.x and things going so smoothly and then trying to move to 4.x where we can't use it at all because of the performance problems.
    All I can say is thank you for still loving Ext JS. We will continue to work on any problems and improvements.
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  9. #19
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    36,754
    Vote Rating
    828
    mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute

      0  

    Default


    Quote Originally Posted by deskwideweb View Post
    Indeed I suspect that with the acquisition of Ext by Sencha this was the plan all along: abandoning ExtJS, to focus on Sencha.
    Sencha didn't acquire Ext JS. Ext merged with some other projects to form Sencha. Not matter what anyone says, Ext JS 4 is still of the same blood that Ext JS 3 and before are. Sure there are new things, something I would expect from a new major version.
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  10. #20
    Sencha User
    Join Date
    Jun 2011
    Posts
    19
    Vote Rating
    0
    tejas@reach1to1.com is on a distinguished road

      0  

    Wink


    I have upgraded one of my project module from EXTJS3.x to EXTJS 4.0.2a.....in the way found lots of ERROR but tackle it...thanks to my Team & Sencha Communities.......I m Loving it

Turkiyenin en sevilen filmlerinin yer aldigi xnxx internet sitemiz olan ve porn sex tarzi bir site olan mobil porno izle sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli porno izle siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir. Mesela diğer sitelerimizden bahsedecek olursak, en iyi hd porno video arşivine sahip bir siteyiz. "The Best anal porn videos and slut anus, big asses movies set..." hd porno faketaxi