etoys-dev October 2006

etoys-dev@lists.squeakfoundation.org

24 participants
53 discussions

[Etoys] Testing at 1200x900
by Bert Freudenberg 20 Oct '06

20 Oct '06

I tried today to run my trusty CRT in a 1200x900 mode, but the a-test board with image build 118 would not let me. I could only make X11 work at 1152x864 and set the virtual resolution to 1200x900. This is inconvenient but I think we should test projects at their actual size. Same goes for sugar-jhbuild. If your machine does at least 1280x960 you could run Sugar at the right resolution by giving the right arguments to Xnest. - Bert -

3 3

[Etoys] Menu bug
by karl 20 Oct '06

20 Oct '06

If you turn a menu with the halo and dismiss it with the menu close button it's tranformation morph is left behind on the desktop. karl

2 2

[Etoys] Etoys via YUM
by Bert Freudenberg 19 Oct '06

19 Oct '06

See http://etoys.laptop.org/ - Bert -

3 4

[Etoys] A few notes on Bookmorph
by Milan Zimmermann 19 Oct '06

19 Oct '06

Hi, There are a few confusing things about Bookmorph that I wanted to mention (the first for a long time). Neither of them are bugs, so I'll try to be brief: 1. This was very confusing to me when I first used the Bookmorph years ago. The page controls (> < etc) are way too small, for first time user the Bookmorph looks like an empty page without any way to move around. (I know there is baloon popus on the controls, but I remember I did not put mouse over them, as they seemed insignificant) Once user knows the little ants are controls it's good, but I would really like to have the page controls very large and stand out, perhaps ellipses with color background, because there seems lots of space across. There seems enough space even without making the dark ribbon on top taller. (I think on the small OLPC screen the controls must be almost unnoticable.) 2. Another confusing thing is that the only way to move to book around is to bring the hallos. That by itself is ok, with two comments: - All other non-trivial object presentations, (not sure how to express it, so by example) such as "Sound" "Movie Player", "All Scripts" can be picked up by left-clicking (red) somewhere in the non-input area. The BookMorph cannot, only by invoking the halo. It would be nice to pick it up by left-clicking on the darker control ribbon on top. - Also, unlike other morphs that are a composition, if user first right-clicks (yellow) on the dark "ribbon" with the controls, a halo is brought on it (AllignmentMorph), not on the outermost book frame. Just wanted to mention this, Milan

3 4

[Etoys] Keyboard shortcuts
by Bert Freudenberg 19 Oct '06

19 Oct '06

For those who are wondering why Alt-p etc. does not work when running in Sugar, you can edit /usr/share/sugar/kbdconfig which sets the matchbox window manager keyboard shortcuts. In sugar- jhbuild, modify source/sugar/shell/data/kbdconfig because otherwise the installed copy will be overwritten when rebuilding sugar. - Bert -

1 0

[Etoys] File storage
by Bert Freudenberg 18 Oct '06

18 Oct '06

Just found this in the mail attached below: > Activities get a limited, secure file area of > their own to do with as they please, and access to the document store > for actual documents. Most activities will use the file area for > things > like config files, but some might elect to use it to keep their own > sqlite database or some such. So we can count on using files for some of our storage needs. - Bert - Anfang der weitergeleiteten E-Mail: > Von: Ivan Krstić <krstic(a)solarsail.hcs.harvard.edu> > Datum: 11. Oktober 2006 12:08:17 MESZ > An: Ian Bicking <ianb(a)colorstudy.com>, sugar(a)laptop.org, > dcbw(a)redhat.com > Betreff: Re: [sugar] Content types > > Ian Bicking wrote: >> There's other aspects too. Is the data versioned? Some data >> should be. > > The data store provides integration with the differential storage > engine > which activities are free to use or not use, as makes sense for each > item they store. > >> And there's a mime registration use case too -- you need a custom >> viewer >> to view application/xml+x-olpc-chat. > > Well, *maybe* you need a mime database, but it's for the case where > the > common viewing app for a format is not the app that created the file. > So, for example, with the chat logs -- if you find the logs in the > journal, the journal can start the chat app's log viewer for you > without > consulting a mime database, since it knows that the chat app > created the > logs. > > If you find the logs through a resource browser, it can do the same > since the logs have a tag indicating the originating application. > > But without a configurable mime mapping, you can't use either of these > mechanisms to say "actually, chat logs are just text files, and I'd > rather open those up in vim". > >> From what I >> know of the plan for the storage system, I think it should be >> possible >> to delegate areas of storage to activities. > > This has been my plan. Activities get a limited, secure file area of > their own to do with as they please, and access to the document store > for actual documents. Most activities will use the file area for > things > like config files, but some might elect to use it to keep their own > sqlite database or some such. > >>> This is an interesting question; we can't necessarily allow every >>> activity to access the data store of every other activity. If >>> you've >>> marked something "private" and any activity can access that >>> thing, it's >>> no longer private because some activity could just pipe the thing >>> over a >>> network socket. >> >> We need watermarks! Haha, j/k. I assume the storage manager would >> handle this issue. > > Yes, it would. > >> I actually imagine many different browsers, not a single one. An >> image >> browser. An any-kind-of-content browser. A history browser. A >> privacy/purging browser. A where'd-all-my-disk-space-go browser. >> Just >> because there won't be a singular hierarchical view of the storage >> doesn't mean we should leave out views of the storage! > > Fully agreed, although the security implications are non-trivial. > >> We really don't need to use names and magic to figure out file >> types. If >> we care about content types at all we should just use MIME types. > > +1. > > -- > Ivan Krstić <krstic(a)solarsail.hcs.harvard.edu> | GPG: 0x147C722D > _______________________________________________ > Sugar mailing list > Sugar(a)laptop.org > http://mailman.laptop.org/mailman/listinfo/sugar

1 0

[Etoys] Performance improvements form 3.9 (backported) #2
by Marcus Denker 18 Oct '06

18 Oct '06

In Squeak 3.8 (and thus OLPC Squeak), we changed Squeak to call #initialize by default on #new. The attached changeset fixes some instance creation methods (e.g.of Rectangle, LookupKey, Point) to not call #new (as there is no initialize method), but use #basicNew instead, thus saving a lookup and call to the empty #initialize method.

4 10

[Etoys] User Images Links on www.squeak.org Announcement
by Brad Fuller 18 Oct '06

18 Oct '06

All, The Squeak WebTeam is providing a place to describe and access commonly used images created by users. If you have an image that you believe others would like to use (a good example is the v3.9 developers image), please let us know and we will include the description and link location on the "download" page of the squeak.org web site. We are also offering to store your image on the ftp.squeak.org site, but it is not mandatory (you can keep your own location to save squeak.org space and WebTeam labor.) If you would like to donate your image, return the following information to: webteam(a)lists.squeakfoundation.org ----- Image Name: <The name that represents the image> Creator: <Who developed the image> Description of Image: <Include the contents of the image, how it might be used, who would benefit from it's use, etc.> Image Base: <the version used to create this image, e.g. 3.8-6665> Image Filename: <the name of the image> Image full URL: <The full path to the latest .image file or directory. Or state if you'd like the WebTeam to host your image - you'll need to provide a location from which we can ftp the file(s)) ----- Thanks, Squeak WebTeam

1 0

[Etoys] User Images Links on www.squeak.org Announcement
by Brad Fuller 18 Oct '06

18 Oct '06

1 0

[Etoys] latest status of save/revert in bookmorphs
by Scott Wallace 18 Oct '06

18 Oct '06

Hi, all, Update 1071bookSaveRevert-sw undertakes to merge and bring out the best features of each of the two disparate schemes formerly in place. (1) As before, all revertibility is predicated on an explicit prior "save for later revert." (2) From the user's point of view: when going through a tutorial housed in a BookMorph whose author has earlier done a "save entire book", the user can choose either of the following items from the main Book menu at any point: [a] revert this page [b] revert entire book. The single-page revert discards any changes the user may have made to the page, and reverts it the pristine version the author has prepared for it. The "entire-book" revert discards any changes the user may have made anywhere in the book, including page insertions, page deletions, edits on a page, and page-sorting, and restores the original list of pages in the original order. (3) The normal authoring procedure will be to create the BookMorph, get it into exactly the state you want it to be in when the user first loads it, then choose "save entire book for later revert" from the Book menu. Except in unusual circumstances, this will probably be the final step in publishing a BookMorph-based tutorial. Any pre-existing BookMorph content can be made "revert-friendly" by loading it, then telling it to "save entire book for later revert," then republishing. (4) Note that when using the "short form" of the Book control panel, clicking on its menu icon will now bring up a "short form" of the Book Menu, which offers the "revert" commands and a few other things of general interest to non-author users of the book, such as "find." For the more author-like options relating to building the book, switch to the long form of the Book control panel. (5) Finally, note that the Viewer for a BookMorph now offers tiles for revert-this-page and revert-entire-book, so authors wanting to bring the "revert" feature to the attention of their users can make their own "revert" buttons and position them on their pages. Cheers, -- Scott

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

etoys-dev October 2006