17 Jan 2012 1:30 PM #11
Empower the community
I think Sencha actually have an opportunity here to empower the extended community to assist more than they currently are.
Weekly builds (or Source access) would encourage developers to work actively with Sencha to resolve issues rather than sitting waiting for an unknown release to drop
The tone of the comments from the community I think supports this.
17 Jan 2012 2:29 PM #12
I think Sencha are in something of a Catch-22 - damned if they provide dates and don't make them, damned if they don't provide dates at all. Given the debacle that was the 4.0 release, I can appreciate Sencha not wanting to be burned again.
I also think that a normal customer response to this would be to ask for smaller point releases, so as to lower sensitivity to dates - smaller, more frequent updates obviates the need for dates, to some degree.
The problem here, is that 4.0 performance was so bad that it forced the team to go back to the drawing board on the layout engine. While I can't and won't speak for the team, or anyone at Sencha, I can imagine that it would be nearly impossible to turn out small releases while this refactoring took place (and remember, it needs to take place just to fulfill the performance promises of 4.0!)
With all of that said, I hope Sencha gets it right, and not fast. Unfortunately for me, I no longer have the luxury of being an early adopter or tester, as I've blown major delivery schedules over 4.0. I eagerly await whatever results...
17 Jan 2012 2:36 PM #13
I agree with your thoughts with regards to major rewrites etc, its very difficult to post a date and stick to it.
Now however, we have moved past preview and into Beta mode, it should be feasible that there is a weekly build with x issue resolutions included. Some incremental progress will be very well received I'm sure.
I also still stress that there is an opportunity here to engage the community further and have them actually assist in this process. whether a weekly update or 6 monthly update, if the community is at the end of the pipeline receiving the drop, they will offer little more value than pointing out something doesn't work and sending it back.
If you can gear the development pipeline to include the community along the way, having community submit fixes for issues, and test cases for faults etc, that is how you drive yourself out of a messy situation like this.
I guarantee the community contains many experts in different areas of the code base, who will provide valuable input if given the opportunity.
17 Jan 2012 9:13 PM #14
17 Jan 2012 11:23 PM #15
20 Jan 2012 7:06 AM #16
I concur with what other have said. ExtJS upgrades are an important part of our product roadmap. Given that we don't have an ExtJS roadmap (even a rough one), it makes it somewhat challenging for us.
21 Jan 2012 7:13 AM #17
Extjs for multi - Application
Here an example for multi-application with MVC architecture, using Ext.app.* and Ext.Loader. Try it
Might be a suggestion to include other versions.
21 Jan 2012 7:28 AM #18
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Software Engineer
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 email@example.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.
23 Jan 2012 6:57 AM #19
Questions application bundles
In development, a bundle has the same folder structure that the application. I use
Ext.Loader for use the new dynamic dependency loading capability.
In production, could I use the newly-introduced Sencha SDK tools to obtain all clases in a single file. Then, I have one file to load for a bundle. Could be use asynchronous loading to load these bundles in my app on demand.
13 Feb 2012 8:17 AM #20
I was working to extend Ext.application from MVC to HMVC.
I show an example builded with HMVC architecture.
The application contains bundles, its has the same folder structure like application.
The bundle's controllers has the same application bus event.
The bundles have optional main view to be injected in application viewport (shell) by a defined placeholder. (I use Ext.ComponentQuery to view-discovery, view-injection).