Sencha Architect crashes when project is reopened (corrupted project source?)

[jasonehle]

Is there a way to provide "user settings" outside of the XDS?

Our team is evaluating using Sencha for our platform going forward, and we work accross a variety of configurations.

Currently it appears that when a dev updates the XDS from source control, we must everytime go in and alter the exportpath. This is a pain.

You should be able to provide a pointer in the XDS project file to a local config that overrides the settings in the XDS. The local config wouldn't get checked in and thus overwritten by the last guy who changed the path and committed to source control.

Maybe I'm missing something obvious... hope so... please let me know how we're supposed to use this in a team environment. I've read the "Collaboration" information that I could find, but it doesn't mention anything at this level.

Other than that - Architect2 is an incredible piece of software. I hope it will work out for us. I can see myself spending many years in this IDE

Regards,
Jason

[aconran]

User settings are written to a file called .architect (and typically excluded from source control).

The export path is currently a project level setting. We can look into migrating it to a user level setting and/or allow the user level setting to override it.

[jasonehle]

We can coordinate the paths on our end for now at least where the OSs are the same. Its a few seconds every time after updating - not super critical - but it would be great to consider it for the .architect file. Thank you for the quick reply