[IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
sdaly.be at gmail.com
Sat May 30 14:25:15 EDT 2009
Actually my first idea communicated to Gary was for the dots to be
kids avatars and the center to be different Activity icons ending with
Upon reflection I do fear however that it will lead to confusion,
Learners will believe each icon represents its Activity "loading",
present on the machine. And, even the avatars might generate confusion
since they won't represent other Learners like in the Neighborhood
That said I feel there is a real opportunity to call upon Sugar
graphic elements to communicate core Sugar brand values at boot time:
fun, friendly, colorful, collaborative, etc.
I encourage anyone with an idea to post a GIF mockup or even a
screenshot mockup on the wiki - rapidly if possible.
On Sat, May 30, 2009 at 8:12 PM, Gary C Martin <gary at garycmartin.com> wrote:
> On 30 May 2009, at 18:50, Walter Bender wrote:
>> On Sat, May 30, 2009 at 1:07 PM, Frederick Grose <fgrose at gmail.com>
>>> For Sugar, the new "Hello World" tutorial could be its boot
>>> Activities for
>>> Learners: Each development tool (Pippy, Turtle Art, Etoys, others,
>>> Forth) should provide an Activity to build the start-up sequence.
>>> could play with the tools to build an endless variety of start-up
>>> modify and preview from a library of saved sequences, learn all
>>> sorts of
>>> things about the system, the different tools, and of course,
>>> designate one
>>> sequence to display on the next boot.
>> Fred has sparked an idea. What if we replace the dots with activity
> Hmmm, activities shown might not be installed and then lead to
> confusion (unless you are considering the difficult step of pre-
> generating boot graphics at shutdown).
> There's a fine line between cool eye-candy – and there are plenty of
> cool Sugary lickable animations we could try, activity icons being
> one – and boot UI feedback utility :-)
> Now... If the technical boot stages could be made clear (device/
> keyboard checks, network detection, certain key services, etc) it
> could be of real use to have some simplified abstract icon for each
> stage so you'd have an idea for what really might be going on (or
> where a boot/hardware problem was) – but realistically that's more of
> a long term UI opportunity**.
> ** Sebastian: Do you know just where/when each progress update is
> triggered, and what major boot landmark could be sensible to visually
> indicate success of?
>> Walter Bender
>> Sugar Labs
>> IAEP -- It's An Education Project (not a laptop project!)
>> IAEP at lists.sugarlabs.org
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
More information about the IAEP