Revision as of 16:47, 16 June 2010 (view source) Nedrichards (Talk | contribs) m ← Older edit		Revision as of 11:05, 21 June 2010 (view source) Nedrichards (Talk | contribs) m Newer edit →
Line 5:		Line 5:
	==Anatomy of an app ==		==Anatomy of an app ==
-	== Toolbar ===	+	=== Toolbar ===
	* Use it to act on the context.		* Use it to act on the context.
	* No menus		* No menus

---

Revision as of 11:05, 21 June 2010

Contents 1 Interaction architecture 1.1 Anatomy of an app 1.1.1 Toolbar 1.1.2 Sidebar 1.1.3 Content pane 1.2 Big screen mode 1.3 Panel

Interaction architecture

Netbook applications should expect to fill the whole of the screen on their zone (in small screen mode).

Anatomy of an app

Toolbar

• Use it to act on the context.
• No menus
• This is also your window decoration

Sidebar

• Use it to change the context.

Content pane

• Where the action is.

They are self contained experiences and all popups should be constrained and contained within the applications window.

Big screen mode

When on a big screen, not a netbook

Panel

• Quick tastes of interaction
• Just one screen, ideally page not scroll
• Get to what you want to use a lot, as quickly as you can
• Not a place to stay.