23 Oct 2012 11:43 AM #11
I've gone ahead and reported it as suggested.
This still does not ease usage.
Currently, in our current practices, it means, checking out, each of the 3 files, that correspond, to what would normally be 1 file.
There's the meta file. the js file that is generated on save, and than the file that is deployed, to the .net project.
and this can easily become, tedious, when you find yourself when possibly having to also edit corresponding views, stores, models. and controllers.
So that leaves the minimum, of 3 files, and a potential for 12 or more files, that would have to be checked out, to be able to work gracefully, in architect without having to worry about the save failing.
23 Oct 2012 12:56 PM #12
I think your product could go a long ways towards helping us TFS (team foundation server) users out by:
- first checking if a file is read-only before ever making a change (in-memory or file)
- prompting user that file is read-only so we have the chance to grab latest from TFS before any in-memory edits are made.
- monitoring local file for read-only state and changes since last opened or last checked.
24 Oct 2012 9:19 AM #13
Part of this will come in the next patch release to 2.1. You'll be notified of file changes that occur outside of Architect. With the option to reload the entire project.
2.2 will allow for individual files to be reloaded.
Note however that if you're editing a file that could possibly be stale this is bad. Perhaps we should visually show files that are readonly in the inspector?Phil Strong
Sencha Architect Development Team