On Tuesday, March 15, 2011 12:37:14 PM UTC+1, Jens wrote: > > On Saturday, March 12, 2011 9:58:11 AM UTC+1, Thomas Broyer wrote: >> >> >> It's even better than that ;-) >> The user has to click a "lock" button to be able to edit the objects >> (creates a working copy). The form then switches to read/write mode and the >> "save" button appears. But the save button only saves changes to the working >> copy; there's a distinct "unlock" button that overwrites the "public copy" >> with the "working copy" (and another "free" button to "unlock" the "public >> copy" and simply discards the "working copy"). >> A user can keep his working copy for days, or even weeks or months. >> > > Uhh..so if I work on my private copy for 2 weeks and then unlock it to > update the public copy, a second user can destroy my work by unlocking his > copy a day later and thus overwriting my 2 weeks of work? :) Having working > copies is a nice idea but merging them back into one public copy seems > tricky. But of course it depends on the application. >
There's no need to merge, because when you do a working copy, you're locking the public version. The idea of a working copy is that you work in private, and the public version stays the same until you "publish" your work. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
