13 Jun 2013 2:44 AM #1
I love Sencha Touch. I have been working with it for almost 2 years, since 1.0.
HOWEVER, I am damn tired of having my development environment being a mess after ANY upgrade. ANY! BUG FIX POINT RELEASES, EVEN.
Do you guys care about this?
It has the effect of making me not want the fixes, for fear of having to deal with this.
13 Jun 2013 8:53 AM #2
Can you elaborate on any issues you're having?
15 Jun 2013 4:49 AM #3
- Join Date
- Mar 2007
- St. Louis, MO
- Vote Rating
I personally don't have issues with any of my apps with upgrading even with dot releases where lots may change. I think it's about how much you override or if you are doing things properly also.Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
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 firstname.lastname@example.org
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.
15 Jun 2013 9:28 AM #4
Sometimes I've run into issues - like the scrolling issue on PhoneGap on Android that the 2.2 release caused. But it was quickly fixed when 2.2.1 went out.
17 Jun 2013 1:14 AM #5
Sorry for my expressed frustration and slow followup. We had a malware infection in oursite in the meantime that got into my computer here too.
What I was frustrated with was upgrading cmd on the way to 2.2.1 from 2.2.0
Why replace the startup splash screens, overwrite the app.sccs and app.js files? the scss and app.js were fine, but you have to manually run around.
when the build blew up, so did I.
17 Jun 2013 1:26 AM #6
jattardi - that was the reason for the upgrade at this late stage in our project. Working now, scroller fixed, but I still don't understand why they replace the resources images like splash screen, icons.
upgrading to 2.2 from 2.1 was tricky... mostly because of the font replacement for iconMask, and I expected to work for that one. but a point release that wanders around my stuff during upgrade and places bird droppings in my source code just does not seem right.
17 Jun 2013 1:29 AM #7
>> I think it's about how much you override or if you are doing things properly also.
Good point. but not the case. I understand that. It was the messing with the build enviroment that PO me.