Sorry, I don't have any Doc reference at hands.
Eventually someone of the Atelier team has.
Out of practical observation
there is a quite fundamental shift in the editing paradigm between Studio and Atelier.
Studio does Server based editing. What you change is there and during your changing session
you lock the Class, Routine, ... So you act as single owner at that time and
anyone else trying to change something gets an immediate alert.
It's the "Highlander Principle" (according to the film) "There can be only One" http://wiki.c2.com/?HighlanderPrinciple
It's based on classical LOCK logic. "Pessimistic Locking"
Atelier acts on your local copy and no one else might know unless you use some source control. !!
At compile time your copy is checked and if it was changed you get a nice Text-Diff to decide how to to proceed.
So we see "Optimistic Locking" or "Versioning".
You can easily reproduce this:
- open some Class or Routine in Studio and do any change (e.g. Comment) but no compile or save
- open the same with Atelier. - no alert
- change it in Atelier. - no alert
- save it in Atelier. NOW you get your alert from server but you keep your local copy.
- save your copy in Studio. - you are the winner
- do some dummy change in Atelier (I found no other way)
- save it in Atelier and you get the Text-Diff with your version and the actual server version
but as in past you get no hint how many changes you may have missed.
I think at that point latest anyone should have understood the importance of source control.
to know of an intended change in advance and his history later.