[udig-devel] Commit and save

[Jody Garnett]

I wonder if we can fix up the language for this one?
- Commit / Revert are part of the editing workflow
- Save is part of the Open / Save workflow used for individual Maps
- There is another workfow for "temporary" data; Create Feature Type 
starts this workflow - and we should have some kind of "Export" option 
to end it.

The Map Open/Save workflow will try and clean up the other workflows so 
you don't lose work (so it will perform a commit, or perform an export 
as needed).

Here is the page from the developers guide:
- http://udig.refractions.net/confluence/display/DEV/User+Interface+Workflow

Suggestions on how to present these ideas (or simplify them) are greatly 
welcomed.
Jody
> The only difference is that save will also export the in-memory layers 
> to shapefile and replace them in the map.  We've been trying to 
> reconcile the two for a while as well...
>
> As for which should you use... It doesn't really matter.  But 
> temporary/in-memory layers should be quicker to save out but obviously 
> they are in memory so if you crash you'll lose your work.
>
> Jesse
>
> On 1-Nov-07, at 1:18 AM, Silvia Franceschi wrote:
>
>> Hi all...
>> just a stupid question... :-)
>>
>> What is the main different between save and commit? Is save related 
>> to some operations and commit to others or are they both usable for 
>> the same porpoise?
>> I know that the save command saves the new layers and the commit not 
>> but when editing a layer what should I use?
>>
>> Thanks for help...
>>
>> Silvia
>> _______________________________________________
>> User-friendly Desktop Internet GIS (uDig)
>> http://udig.refractions.net
>> http://lists.refractions.net/mailman/listinfo/udig-devel
>
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel