Utkarsh has made some feature pages but I am also losing track.
Multiple users I believe is a much bigger question. The Sugar on Ubuntu
uses the same login for Sugar as for Ubuntu - so each user is separately
identified. However, on an XO, the activities belong to a single user -
olpc. This would have to be changed as it is for the Sugar on Ubuntu to
enable all users to share the same installed activities. Independent
datastores come for free in this scenario; however, I think that
downloaded pdfs and media files should be stored in a separate shared
datastore to prevent duplicate use of storage. There is some serious
design work that is needed before this can be reliably implemented.
Specifically, the Sugar on Ubuntu requires a logout and login to change
desktops and to change users. In the case of the XO, I advise teachers
to have the students close the lid between classes so the XO can be
brought back from sleep and not rebooted. The battery will last for
quite a long time in this scenario.
One advantage of logging out and then in is that all activities in a
user's session are closed while the new login starts activities as
needed. This simplifies keeping track of what activity is the
responsibility of which user.
Tony
On 06/03/2016 07:59 AM, Walter Bender wrote:
Tony,
Is there a feature page associated with all of these changes. I am
having trouble following it all.
FWIW, I am very much in favor of encouraging reflection of any sort --
even simply naming an entry -- upon closing an activity. And I could
live with the idea of discarding an entry if the user chooses to at
exit for an unnamed entry. But I guess I need to understand the
details of the interaction.
As far as support for multiple users, there are some questions about
the usecase I have: for example, do the students typically do a reboot
in between, or just hand off the machine?
-walter
On Fri, Jun 3, 2016 at 3:01 AM, Sebastian Silva
<sebast...@fuentelibre.org <mailto:sebast...@fuentelibre.org>> wrote:
El 03/06/16 a las 01:52, Tony Anderson escribió:
> I am not proposing to re-enable that feature. The purpose is to enable
> the user to provide a title for the Journal object.
Maybe I misunderstood. Isn't that what the name-your-journal-entry on
exit dialog used to do?
> Why are we not using the alert which Utkarsh has implemented for the
fiddle save? It works. It looks good. He has the code in hand.
If the purpose is the same - then - is Utkarsh's implementation better
looking? More functional? Or does it have a different purpose?
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
<mailto:Sugar-devel@lists.sugarlabs.org>
http://lists.sugarlabs.org/listinfo/sugar-devel
--
Walter Bender
Sugar Labs
http://www.sugarlabs.org
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
