<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Again, I have not been clear.<br>
<br>
The intent in the 'backup restore' option is that Journal objects
such as Terminal and Log activities would be saved to a log
directory on the school server <br>
and deleted from the local Journal (and so not appear at all). This
means the statistical benefits of recording everything would be
retained (where a school server is available) but the items would
not clutter the Journal View.<br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 06/02/2016 08:01 PM, Sebastian Silva
wrote:<br>
</div>
<blockquote
cite="mid:30540f5e-b27a-20a1-07b8-465e8c14cccc@fuentelibre.org"
type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<p>El 02/06/16 a las 12:50, Walter Bender escribió:<br>
</p>
<blockquote
cite="mid:CADf7C8sSBFO7pY8tq7SWtGYn46=HTd5++neqo3AaHfRFfq1pWw@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jun 2, 2016 at 1:38 PM,
Sebastian Silva <span dir="ltr"><<a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:sebastian@fuentelibre.org"><a class="moz-txt-link-abbreviated" href="mailto:sebastian@fuentelibre.org">sebastian@fuentelibre.org</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>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.</p>
<p>So imho Sugar should not force you to commit if you
don't want to.<br>
</p>
</div>
</blockquote>
<div><br>
</div>
<div>We had long ago talked about letting some activities
opt out. Regardless, adding the commit message back with
an opt-out button is fine with me, but I still don't
understand what problem we are solving. </div>
</div>
</div>
</div>
</blockquote>
Good question. I hope Tony can answer that. If I understood him
correctly he's trying to avoid having many journal objects
currently having exactly the same name thus being
indistinguishable from each other.<br>
<br>
<blockquote
cite="mid:CADf7C8sSBFO7pY8tq7SWtGYn46=HTd5++neqo3AaHfRFfq1pWw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>If I understand it, Tony also wants to circumvent the
relaunch last instance by default as well. In the case
of your Terminal example, it would mean you'd have
Terminal instances in your Journal for each time you
used the Terminal unless you too the time to go to the
Journal and search for a previous instance. I think that
makes the spam problem worse, not better.</div>
</div>
</div>
</div>
</blockquote>
I tend to agree with you on that one. Tony makes a valid point
that Sugar, more often than not, is used by many learners who may
not expect to open somebody else's work by default.<br>
<br>
Just a detail in your conclusion, is that, by having a `don't
commit` option, I would have probably no journal objects at all
for Terminal.<br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>