[Sugar-devel] [DESIGN] Name object on Activity exit revisited

[Sebastian Silva]

Not every time you do an activity are you doing work worth committing.
For instance I work with a lot of terminals, that I reuse and there's no
point in committing terminal sessions.

So imho Sugar should not force you to commit if you don't want to.


El 02/06/16 a las 12:36, Walter Bender escribió:
>
>
> On Thu, Jun 2, 2016 at 12:34 PM, Sebastian Silva
> <sebastian at fuentelibre.org <mailto:sebastian at fuentelibre.org>> wrote:
>
>     El 02/06/16 a las 11:37, Walter Bender escribió:
>
>     >
>     > I don't recall there ever being a 'Don't Save" dialog. I do
>     recall the
>     > dialog to enter a "commit message" upon exit. I'm all for the
>     latter!!!
>
>     Yes the proposal is a 'commit message' with a 'don't commit' option. I
>     was never a fan of the former but having the option would change
>     my mind.
>
>     Can you help point Utkarsh to when this was removed? Thanks!
>
>
> It was sometime before 0.96 because it was in that release I added the
> "Write to Journal Anytime" feature.
>
> But I am confused as to what problem we are solving here.
>
> I think we should require commit messages in Sugar the same way we
> require them in our own work. But that said, the decision to commit is
> made numerous times through out the lifecycle of an activity, not just
> at closing. For example, Turtle, Write, and many others will write
> whenever the activity goes to the background. And Turtle saves
> whenever you run code. So how does a "don't commit" option work exactly? 
>
> -walter
>
>
>
> -- 
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20160602/ba44b32b/attachment.html>