Hi folks,
In the newest OLPC-etoys image, the one with three clouds when you open etoys, I cannot figure out how to load a previously saved project.
Did someone forget an "open" button somewhere, or am I being dense?
Also, is there any way to save the image now? I'd like to default to "scale to fit" for example.
Tim
On Oct 4, 2007, at 19:42 , Timothy Falconer wrote:
Hi folks,
In the newest OLPC-etoys image, the one with three clouds when you open etoys, I cannot figure out how to load a previously saved project.
Did someone forget an "open" button somewhere, or am I being dense?
You need to open them from the Journal. This is how Sugar is designed, and we need to adhere to its philosophy to avoid confusion.
If you are not running in Sugar, you can drag and drop a project from a folder on your machine. However, in that case you should not use the Sugar toolbar but the classic orange navigator flap.
Also, is there any way to save the image now? I'd like to default to "scale to fit" for example.
I have been lobbying for making this the default if the actual display resolution is not 1200x900. Without success so far.
- Bert -
On Oct 4, 2007, at 19:42 , Timothy Falconer wrote:
Also, is there any way to save the image now?
There is - you need to change the permissions of the image, which is located in /usr/share/etoys
It's not something we can support, though, and it will be not possible once the OLPC security containers are enabled.
- Bert -
On Friday 05 October 2007 1:55 am, Bert Freudenberg wrote:
On Oct 4, 2007, at 19:42 , Timothy Falconer wrote:
Also, is there any way to save the image now?
There is - you need to change the permissions of the image, which is located in /usr/share/etoys
The conventional place to store per-user preferences and files is ~/.<app>. What is the problem if an image is saved to ~/.etoys/<name>.image?
On XO, ~/.etoys/etoys.image can be symlinked to /usr/share/etoys/ so it cannot be overwritten.
Subbu
On Oct 5, 2007, at 5:15 , subbukk wrote:
On Friday 05 October 2007 1:55 am, Bert Freudenberg wrote:
On Oct 4, 2007, at 19:42 , Timothy Falconer wrote:
Also, is there any way to save the image now?
There is - you need to change the permissions of the image, which is located in /usr/share/etoys
The conventional place to store per-user preferences and files is ~/.<app>. What is the problem if an image is saved to ~/.etoys/<name>.image?
For one, it would use twice the disk space. We need to retain a clean copy. Secondly, the etoys image traditionally is not supposed to be saved - all user content is in projects.
Now, it would be a shame to not be able to do this. I have repeatedly asked for contributors to make Squeak on OLPC be useful as a Smalltalk environment once kids have grown out of Etoys. Alas, without response so far. You're very welcome to change this.
On XO, ~/.etoys/etoys.image can be symlinked to /usr/share/etoys/ so it cannot be overwritten.
Because of the security architecture on the XO, traditional Unix file locations do not necessarily work. You can't simply write to the home directory. There is per-activity storage though which could be used for this (it's supposed to hold configuration data that is global to all activity instances). But since this has not been implemented yet and the spec is shifting, I do not yet know the exact location.
- Bert -
etoys-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
subbukk -
Timothy Falconer