Architecture Manual
Jump to navigation
Jump to search
- Overall architecture
- The interaction between Sugar and Activities, especially collaboration
- DBus protocols
- etc.
Wish List
- How are .pyc files in builds created? Will they be regenerated automatically if I change a .py file and delete the .pyc file?--Mikus Grinbergs 2008-5-14 http://lists.laptop.org/pipermail/sugar/2008-May/005696.html
Making builds
Our documentation on how to make your own build is pretty spartan right now. Reading
- OS images to understand the end result, then read
- Building custom images
- Puritan
is a good start. Olpc-update and Clean-install procedure explain how to update your XO to your custom build, you will first need a Developer key.
Try the process out and help us document it better!
Architecture pages
- Category:Developers
- Category:API
- Category:Python
- Category:Hardware
- Category:Battery & Power
- Category:Firmware
- Category:Firmware ROM
- Category:Git
- Category:Peripherals
- Category:Software development
- Category:Telepathy
- Hardware
- Wireless
- Power management
- XO Power Draw
- Hardware Power Domains
- Customizing NAND images Includes keyboard configuration
- Keyboard layouts
- IMEs
- Open Firmware
- Tag editing
- Checking the Layout configuration
- Peripherals
- Sugar Architecture
- Sugar architecture review 1
- OLPC Python Environment
- Sugar Architecture/API
- Localization
- Software components
- Activities
- Collections
- Bitfrost
- XS Server Software
This article is a documentation stub, an outline for a real manual. Maybe it should be expanded, maybe it should be killed — discuss..