[Sugar-devel] Some questions concerning saving methods on sugar

[Claudia Urrea]

Alberto,

The newest version of Scratch (16) allows you to save and retrieve projects
using
the regular folder UI. You can download it from
http://wiki.laptop.org/go/Scratch

You can also import pictures and sound from the journal, and download
projects
from the Scratch website. Please let me know if you have any problems.

Best,

Claudia

On Mon, Sep 20, 2010 at 10:02 PM, Gary Martin <garycmartin at googlemail.com>wrote:

> Hi Alberto,
>
> On 21 Sep 2010, at 02:39, Alberto Arruda de Oliveira <
> alberto.a.oliv at gmail.com> wrote:
>
> > Hello,
> >
> > I've been adapting an application to use as an activity, and I have some
> questions about the way to save on sugar.
> >
> > At first, I tried to just create a directory inside my Activity folder
> especially made for saving files, but it did not work, because of the access
> permissions to it, and, although we could simply manually change the folder
> permission for writing on that folder, we would have to do it for every
> single OLPC we installed our activity into and we didn't want that.
> >
> > Then, we started trying with the journal. Everything was going fine,
> until we discovered that another sugar activity, Scratch, implemented saving
> and loading on a similar fashion we previously wanted. It has a folder
> inside it's Activity directory with subdirectories related to each kind of
> Scratch project. Also, Scratch's Activity directory has the same access
> permission as any other sugar Activity installed.
> >
> > So, my question is, does anyone knows how Scratch implements it's save /
> loading method? is there any guide explaining how to do it without using the
> journal? Keep in mind that we do know that there are other directories we
> could use to save our files, but we would like to use our Activity directory
> if possible.
>
> Sorru, not much help, but my understanding is that Scratch has recently
> been updated to fix this long standing non-standard Sugar behaviour, and now
> uses the Journal to store it's state. Removal of explicit Save/Save as
> dialogues is a specific UI design goal in Sugar.
>
> If you try some other non-standard route you may well break/loose things
> like the various Journal backup and restore options, support in various
> distro environments, as well as activity and OS upgrades.
>
> --Gary
>
> > Thanks in advance ( and sorry for any english mistakes :] ),
> >
> > Alberto Arruda de Oliveira
> > _______________________________________________
> > Sugar-devel mailing list
> > Sugar-devel at lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>



-- 
Claudia Urrea, PhD
Director of Learning, Latinoamerica
OLPC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sugarlabs.org/archive/sugar-devel/attachments/20100920/01316304/attachment.htm