OLPC Human Interface Guidelines/The Laptop Experience/Introduction: Difference between revisions
Line 10: | Line 10: | ||
{|border=1 cellpadding=1 cellspacing=0 style="float: right; width: 175px; border: 1px #666666 solid; border-collapse: collapse; background: #f9f9f9;" |
{|border=1 cellpadding=1 cellspacing=0 style="float: right; width: 175px; border: 1px #666666 solid; border-collapse: collapse; background: #f9f9f9;" |
||
!style="background:#D6784C"|API Reference |
!style="background:#D6784C"|API Reference |
||
|- |
|||
|[[Sugar Architecture/API/shell|Package sugar]] |
|||
|- |
|- |
||
|[[Sugar Architecture/API#Package_sugar.shell|Package sugar.shell]] |
|[[Sugar Architecture/API#Package_sugar.shell|Package sugar.shell]] |
Revision as of 19:40, 7 March 2007
Introduction
Most developers are familiar with the desktop metaphor that dominates the modern-day computer experience. This metaphor has evolved over the past 30 years, giving rise to distinct classes of interface elements that we expect to find in every OS: desktop, icons, files, folders, windows, etc. While this metaphor makes sense at the office—and perhaps even at home—it does not translate well into a collaborative environment such as the one that the OLPC laptops will embody. Therefore, we have adopted a new set of metaphors that emphasize community. While there are some correlations between the Sugar UI and those of traditional desktops, there are also clear distinctions. It is these distinctions that are the subject of the remainder of this section. We highlight the reasoning behind our shift in perspective and detail functionality with respect to the overall laptop experience.
API Reference |
---|
Package sugar |
Package sugar.shell |
- Desktop : Neighborhood
- Menubar : The Frame
- Hierarchical Filesystem : Journal
- Applications : Activities
- Files : Objects