Hi Andreas,
Hi Diego -
As nice as it sounds I don't think switching to 3.9 is a real option at this point. There is quite a bit of heritage to the OLPC line of images that would need to be recreated in 3.9 and it would be quite a gamble to switch the basis for OLPC at this point (remember: summer is supposed to be the drop-dead date for the first several million OLPC units).
Sure. In fact I'm not proposing switch to 3.9. I propose to "backport" the Small-Land changes to OLPC image.
One thing that would be helpful though is if you could point out where the relevant portions of this work in 3.9 are - porting it to OLPC sounds a lot more viable than porting OLPC to 3.9 ;-)
Do you remember the BigBang* changesets? I think I remember you used them as an counter example for the declarative monticello model.
In any case, I can do the port for myself in case you like it.
Cheers,
- Andreas
Cheers,
-- Diego
Diego Gomez Deck wrote:
Hi folks,
Almost all of the features you're talking about are already implemented (and working for years) in the Small-Land image.
In beginner mode, the dockbars can't be removed nor moved nor sized. But in non-beginner mode, the standard halos are available to handle the dock-bars.
More to say: This Small-Land changes are already included in 3.9. I propose to use/expand THIS work instead of create another implementation.
Cheers,
-- Diego
Bert,
Thank you for the feedback!
Why did you make that flap unremovable? I can't even get a halo on it. It should be visible by default, I agree, but shouldn't there be a way to hide it, too?
I was thinking about the classroom setting, where the teacher wouldn't want to deal with dissappearing menu bars. (For that matter, The earlier Japanese version of Etoys suppress the halo for Navigator flap. It has certain advantages, as many number of kids dismiss the navigator when they learned how to delete a morph via "X" icon.)
From the flap menu, it should be able to hide and show the "Sugar Navigator Flap." (But clearly my logic of it is flawed and it didn't work quite as expected.) I'm not sure if allowing the manipulation on it via halo is a good idea. (For some demo purpose, it would be absolute fun to be able to script that bar, though...)
-- Yoshiki