Sugar Components: Difference between revisions

From OLPC
Jump to navigation Jump to search
Line 28: Line 28:


And these Modules:
And these Modules:
* frame -- Manages the sugar ui side frames.
* frame
* home -- Manages the sugar ui center for the Mesh, Friends, & Donut views.
* home


==Sugar's Shell Module==
==Sugar's Shell Module==

Revision as of 15:21, 27 February 2007

Sugar Components

This is a continuation of Understanding sugar code. Here, we are in the middle of walking through a sugar shell initialization to see all of the packages and utilities used in the sugar environment. Previously, we saw how Fedora is set up to launch sugar within a python context. Sugar had python launch Matchbox as an X windows environment, and DBUS as an interprocess messaging bus. After importing serveral python libraries (sys, os, gtk, & gobject), and some sugar environment libraries (env, logger, profile, & TracebackUtils), sugar is now going to continue setting up by importing special core python libraries and instantiating various classes and routines... Let's see what happens:

Sugar Module Imports

The sugar-shell has already imported python and sugar environment modules, but now, sugar starts to import Component Modules:

>>> from view.FirstTimeDialog import FirstTimeDialog
>>> from view.Shell import Shell
>>> from model.ShellModel import ShellModel

This looks a good bit like a Model, View, Controller design pattern.

Sugar's View Module

This thing's python path is sugar.view

It includes these packages:

  • ActivityHost
  • BuddyIcon
  • BuddyMenu
  • FirstTimeDialog
  • OverlayWindow
  • Shell
  • clipboardicon
  • clipboardmenu
  • stylsheet

And these Modules:

  • frame -- Manages the sugar ui side frames.
  • home -- Manages the sugar ui center for the Mesh, Friends, & Donut views.

Sugar's Shell Module

Sugar's Model Module