I use Ext Designer daily (latest version) and I find that it regularly crashes. This, I believe, is due to the size of my project file (around 1.7mb).
It wouldn't be so bad, but when crashing (especially during saving), it wipes out the entire project file (bringing it back to 0kb). Fortunately I have hourly backups, but still not desirable... it kinda puts fear in your heart every time you hit the save button
The product, otherwise, is awesome.
If something could be done to improve support for large files, that would be great.
Can you view how much memory XDS is using?
On Winblows, you can pull up the task manager and look under processes.
On Linux, run ps (consult your man page for the appropriate switches like "-aux"). Or, if you don't want to fiddle with it too much, try the "top" command.
I've seen XDS (aka Designer) get very sluggish or freeze up after about 1GB of memory usage. My home PC has 8GB of RAM with about 6GB open... So, memory isn't really the issue on my hardware. However, if your development platform is, say, a laptop with only 1GB of memory... then you can expect it to crash very quickly.
Perfection as a goal is a nice idea that can point one in a specific direction. However, since "perfection" is an ever changing (evolving?) and moving target, one must admit that perfection can never be obtained...
When in doubt, check the d4mn source code!
And here are my terms...
I don't care if you use my source code. (Known as "Code.")
I don't care if I get any monetary compensation.
I do care to receive credit for Code provided. So, please keep my name in the comments for Code provided.
Code is provided without warranty "AS-IS" and I claim absolutely no warranty nor liability to the quality, security, and run-ability on any platform.
By using Code, you accept all risk inherit with Code regardless if Code has known and yet to be discovered bugs.
You are welcome to change and improve the Code to best meet your needs.
I don't care if you use the Code in a commercial or open-source project.
You are not required to contact me prior to using the Code.
Sorry to be the bearer of bad news, but unfortunately Ext Designer v1 has this issue... it won't be fixed, as Sencha Architect has become the new norm.
Can you re-import the view files from the .js? Sadly, no... I thought the exact same thing when it happened.
In the end, we resorted to making 5 minute interval zipped backups of our .xds file, just in case something happened. If you don't have a backup... yeah, I truly do feel your pain.
If you can upgrade to Sencha Architect, we've found it to be MUCH more stable and usable then Ext Designer ever was. We've never had the 0kb crash issue and the project is no longer in one .xds file anymore, so source control is possible.