Sugar design review 3

Overview

The basic components of the framework are activities, the home page, and the people page. "Home page" and "People page" are slide in window activated by special keys.

The Sugar UI framework

Activities

• Each activity will be a fullscreen window. This is important given the limited size of the display.
• Each activity will have a close button in the top-right corner, transparent to not cover the eventual content.
• The framework will not provide docks, like a default toolbar bar or a menubar. Activities author will decide to use toolbox, toolbars or whatever is more appropriate. Though we will probably provide some guidelines.
• Activities are shared by default. When opening a new activity the buddies window (with the chat collapsed) will be showed for a few seconds, and a "shared" checkbox (or similar) will allow the user to keep this activity private.
• When activating an activity, the buddies window (with the chat collapsed) is displayed for a few seconds, to show the kids who are around and to give user a clue that other people can actully be present on the page.

Web browser activity

Sketch activity

Presence window popping up for a few seconds

Home

• Home is a visual representation of the active activities, either currently followed by the user or just shared on the network around him.
• It will be the start page. It's a good start point because, from the active activity, kids will get an idea of what they can do with the laptop and see that there are other buddies around them.
• It will also be the page kids open when they want to do something different or just get back to an activity they was previously working on.
• It will allow to start new activities. Probably just a new button bringing up a list of possible activities (Web, Sketch, Music composition, for example)
• It will be feature an incremental search entry.
• It will be activated by an home button. In the first revision of the hardare it will be possible to navigate it using arrow keys. For this to be convenient the home and the arrows button should both be located near the keyboard and the mouse pad.
• With the next hardware revision we hope to be able to use thumbwheel for navigation.
• It will slide in also when hitting one of the screen edges with the cursor (probably).
• Activities will have to be ordered/filtered so that those that the user has currently open, the most active and the most relevant will have higher priority.

The simpler implementation would probably be a grid. Activities that the user has currently open could be graphically differentiated and would have higher priority in the grid order

Diana had more interesting idea. In the center we would display the activities the user is currently following. While the external circle would host activities shared on the network. The limited space on the internal circle could be used to limit the number of activities a kid can keep contemporarily open.

Creating a new activity

Buddies window

• The presence window and the chat window from Sugar review 2 will be merged in an unique slide-in
• There will probably be a way to collapse/uncollapse chat
• It will be activated by a "People" button (one of the function keys at the top of the keyboard)
• It will slide in also when hitting one of the screen edges with the cursor

The people window

My blog

• A special activity always accessible from "Home"
• Organized and navigable by date
• It will keep track of the activities the kid partecipated or created during the day. It give us a way to get back to them even when they are not active anymore.
• Part (the explicitly posted diary entries most likely) of it will be visible to the other kids, for example by double clicking on someone in the buddies window.
• Other kids blogs will not appear in the Home window, to not clutter it
• It will allow the kids to post diary entries.

My Blog

Notes

• I think it would be nice to have a set of activity shared, similarly to how I have buddies in the presence window with the bots hack. We need to see this work out of the box. -- marco
• We had a discussion about invites and about the necessity of some kind of notification while working on the fullscreen activities (for invites but also in general). Not yet very well defined, so I'd rather push to the next iteration. -- marco