8 Feb 2012 2:29 PM #1
Large Application Support
I've just downloaded Designer 2.x and am trying to open 1.2x file, a rather large beast with approximately 70 windows and 60+ data stores. The project opens in 1.2.x although is unstable (2,105kb in size) and prone to freezing. In 2.x, the file opens but freezes on screen resize.
8 Feb 2012 2:44 PM #2
Send us the file and we'll fix the problem.--
8 Feb 2012 4:02 PM #3
Impressive! I opened the app and I noticed it took a while (Designer was probably expanding the legacy format to our newer file system based format).
Save the project in a folder on its own and you should be good. Just for kicks I started poking around and I noticed you can dramatically reduce the size of your tree by using a model to generalize some of the common field configurations in your stores.
Also, you need to select an initial view (right mouse click on the view you want to launch by default).
Is this an average size project for you? Because if it is, we might consider putting a search box in the project inspector, this thing is HUGE.--
8 Feb 2012 4:09 PM #4
Yeah, the size is a bit cumbersome. For development, we break into individual folders and then save the components to the toolbar, importing each piece as we go. It'd be great if there was a dynamic load process - save the component and the master view automatically updates.
I estimate we're probably about 2/3's of the way there with the number of screens. It'd be great if Designer were fast enough that we could edit directly on the large project - I'll load it up with your suggestions and see what we get. Does 1.2x support the model structure to reduce code size?
8 Feb 2012 4:21 PM #5
Sub-projects: interesting concept. We'll take it for a spin with the team and see if there's something we can do for a future release (2.0 is on lockdown scope-wise).
Models were introduced in Designer 2. You can update for a significant discount if you do it now, by the way.--
10 Feb 2012 8:34 AM #6
Yeah this should be several projects. We need to reach out to Doug and find out the pain points of that so we can understand how to allow projects to share "stuff". This thing has like 100 stores!
Doug this is a lot of work are you sure you want to keep this project public for all to see? I can pull it downPhil Strong
10 Feb 2012 2:04 PM #7
- Join Date
- May 2010
- Guatemala, Central America
- Vote Rating
I counted 70 views.
I have 57 view files in my hand written PR application (still in progress) which 8 are "base" view classes (I use OOP a lot) so I have +/- 49 unique views.
Did you already build the final application for this project?
How big file you got?
Regards.UI: Sencha Architect 3.x / ExtJS 4 & 5
Server side: JEE / EJB 3.x / CDI / JPA 2.x/ JAX-RS / JasperReports
Application Server: Glassfish / WildFly
Databases: Oracle / DB2 / MySQL / Firebird
If you like my answer please vote!
12 Feb 2012 12:25 PM #8
Yes, please pull it down if you don't mind. I've still got a problem in that I cannot open the file in Designer2 for more than 30 seconds without it crashing. I'm on an HP Pavilion dv6, Windows 7, plenty of RAM and a speedy processor. On open of the file, the initial open takes > 1 minute and within the next minute I get the "Sencha Designer has stopped working..." error. Saving the file immediately on open doesn't help either.
Grrr. I'd love to upgrade to Sencha Designer but am not sure that its possible.
12 Feb 2012 12:32 PM #9
The final project is just over 2.4M in size - this is front end, uncompressed. The real is the sheer number of files; we've created a batch script which compiles everything in order, obfuscates and then compresses into a single JS file; don't know the size of that yet.
And all for front end - the backend is Postgresql stored proc based with a Rails MVC in the middle (although Rails is really doing nothing except handling the passthrough).
13 Feb 2012 5:05 AM #10
Definite pain point...
Unfortunately the workflow for large applications is not well supported...
We have a similarly large app, 50+ stores, 40+ controllers and 100+ views...
Having everything in one project restricts multiple developers and the designer does not cope.
Based on the designer internal architecture I doubt this is going to be resolved any time soon....
The only real way forward is multiple projects but then sub-projects or object sharing needs to implemented in some form.
i.e. If we reference a shared window/store or whatever we don't want to redefine it in every project. We want to, perhaps, have a single shared object project and include this into all the other projects.
The multi-project route also helps to allow multiple developers working on the same overall project at the same time.
But then the question really becomes is Sencha then building a full development environment as opposed to a designer only...
At this point I believe there may be a conflict of interest as there are numerous other tools out there for broadbased application development (e.g. Aptana). Finding the ideal way to integrate designer into an existing development workflow is probably a better short-term goal with full development environment the longer term ideal...
It is a great tool, but needs to be utilised in the right context where its strengths (design) are easily taken advantage of. Beyond this you start fighting with the tool and it start impacting workflow... Better to revert to more mature tools at this point (As before eclipse/aptana).
My two cents...