<p dir="ltr">Hi,<br>
Here is Mr. Anderson's suggestion on 'Save As Popup's design. It would be great to have everyone's suggestions and ideas on it.</p>
<p dir="ltr">Regards,<br>
Ütkarsh Tiwari</p>
<div class="gmail_quote">---------- Forwarded message ----------<br>From: "Tony Anderson" <<a href="mailto:tony_anderson@usa.net">tony_anderson@usa.net</a>><br>Date: Jul 15, 2016 10:55 PM<br>Subject: Re: Save As<br>To: "Ütkarsh Tiwari" <<a href="mailto:iamutkarshtiwari@gmail.com">iamutkarshtiwari@gmail.com</a>>, "Sebastian Silva" <<a href="mailto:sebastian@fuentelibre.org">sebastian@fuentelibre.org</a>><br>Cc: <br><br type="attribution">
<div text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div>On 07/15/2016 03:49 PM, Ütkarsh Tiwari
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi,
<div> I have a little confusion about the feature which I
need to clear. Here is what's in my mind. Please correct me if
I am wrong.</div>
<div><br>
</div>
<div>1) If the user '<b>starts'</b> a new activity from 'home
view' - On close the alert pops up - [ XXXXXXX ] 'Save'
'Quit' .</div>
<div><br>
</div>
<div>Action on save - A new instance is created with the new
name while the original instance remains intact with the
previous name.</div>
</div>
</blockquote>
<br>
Since the user started new, there is no original instance. You
create a new instance (metadata). If the user gives you a title, you
save the instance with that name. If the users clicks quit, you save
the new instance (metadata) and quit (no document is saved). <br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>2) If the user <b>'resumes' </b>activity - On close the
alert pops up - [ XXXXXXX] 'Save' 'Quit' .</div>
<div><br>
</div>
<div>Action on close - A new instance is created with the
'overwitten' data and a new name while the original instance
with the original data remains intact ?</div>
</div>
</blockquote>
<br>
This one has three possible actions: <br>
<br>
1. The user clicks on save (not changing the title). You save the
object (with the document). You delete the document at the original
handle. This results in a 'save' - the user has the modified
document in the Journal. From your point of view, there are now two
objects in the Journal, the original metadata file and the new
object.<br>
<br>
2. The user changes the title and clicks on save. You save the
object as in case 1 and you leave the object with the original
handle untouched. Now the Journal has two objects each with its own
file.<br>
<br>
3. The user clicks on quit. You save the metadata file and quit. The
resumed document remains unchanged in the original entry. The new
entry has no document file.<br>
<br>
This is more confusing because of the way Sugar works. On the one
hand, the Journal is a record of documents created by the user. On
the other it is a log of the user's activity with the XO.
Conceptually, I would like to see the Journal show only objects
which have a document with a user-supplied-title. <br>
<br>
With the 'remotejournal', that script should upload the metadata
file for all objects. If an object has a document with a title
supplied by user, the metadata and the document should be uploaded
to the server. In the first case, the metadata file should be
deleted locally (since a copy exists on the server for statistical
analysis). In the Journal, one of the metadata fields is a boolean
named 'keep'. It's use in Sugar was undefined until Walter used it
for his Portfolio activity. <br>
When true, this item shows as a star filled in with a color. If
false, the star shows the background color. <br>
<br>
The idea is that the remotejournal when it uploads a document, marks
it as 'keep'. This signifies that there is a local copy of the
document. If the user clears the star, the remotejournal should
delete the local copy of the document. If the user clicks on a clear
star, the remotejournal should download that document from the
server making a local copy. <br>
<br>
This way the user can delete documents from the local datastore to
save space and still be able to access it when needed for further
use.<br>
<br>
So the remotejournal will eliminate the 'clutter' of the Journal.
This script should run each time Browse connects to the school
server keeping the Journal view compact and with only meaningful
entries. <br>
<br>
It would also be easy to write a 'recovery' script which would sync
the local datastore entries to those on the server leaving all
'keep' stars cleared. The user could then request that needed
documents be downloaded. <br>
<br>
I hope this helps.<br>
<br>
Tony<br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>Regards,</div>
<div>Ütkarsh Tiwari</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Jul 11, 2016 at 11:14 PM, Tony
Anderson <span dir="ltr"><<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,
Utkarsh<br>
<br>
It appears that Dave Crossland (see sugar_dev) concludes
that you are correct - the best thing in the alert is to
leave the project name blank.<br>
I am leaning this way as well. It shows that a name is
needed.<span><font color="#888888"><br>
<br>
Tony<br>
</font></span></blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div data-smartmail="gmail_signature">Regards,<br>
Ütkarsh Tiwari<br>
<br>
<br>
<br>
</div>
</div>
</blockquote>
<br>
</div>
</div>