Good day,

I'm guessing you're trying to save the python code of your current program,
you can save it from
the turtle art activity and it'll be saved in your journal, which you can
open with Pippy activity and copy
the code, save to a file in the terminal and share that file to a host via
any means of your choosing.

Since it's a liveuser each session is lost and you can't use a flash drive,
although that depends on your
VM so you can also easily copy the file.

One reason why it's difficult to save some files outside Sugar is that the
files in Sugar are meant to be run
in Sugar and Sugar creates journal objects and these objects are mostly
linked to tmp files which can be deleted
after they're used.

Hope this helps.

-- 

Ibiam Chihurumnaya
ib...@sugarlabs.org



On Mon, May 24, 2021 at 3:55 AM <pn.fri...@xoxy.net> wrote:

>
> Hello, I'm using live image Fedora-SoaS-Live-x86_64-32-1.6.iso, which boots 
> into Sugar v0.116. My only motivation for now is to use the Turtle Blocks 
> activity. Turtle Blocks (on a virtualized x86-64 guest on VirtualBox!) runs, 
> as per a thoroughly unscientific benchmark, at least 30x faster than the 
> no-install JavaScript version on a nonvirtualized web browser. Hence this 
> choice of software stack.
>
>
> The problem: I can program, run, debug without a problem; but I can't save my 
> work on any storage outside the Sugar virtual machine. I've installed the 
> Terminal activity, ftp and sftp clients, etc... so it's just a matter of 
> knowing which file I have to squirrel away (or bring back if I'm trying to 
> resume work on
>
> Which files should I be exfiltrating in order to snapshot the current
> state of Turtle
> Blocks? How do I cause those files to be created using the Sugar/Turtle 
> Blocks user interface?
>
> Thanks very much for any information,
> --Ken Irusta
>
> _______________________________________________
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
_______________________________________________
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Reply via email to