• Roadmap
• Projects
• Coding
  • Module Owners
  • Hacking
  • Get the Source
  • Build It
• Testing
  • Releases
  • Nightly Builds
  • Report A Problem
• Tools
  • Bugzilla
  • Tinderbox
  • Bonsai
  • LXR
• FAQs

Inital Project Milestones

The work has been divided up in to 3 initial milestones. The first milestone centers around getting a configuration in shape to port and test on small devices; the second involves porting and test planning; and the third milestone involves testing, evaluation, and building a roadmap for future work. An overview of tasks in each milestone is provided below.

Milestone 1

• Combining libraries,
• Making use of Linux system libraries where ever possible
• Implement more efficient and cleaner service APIs, etc.
• Code cleanup in various parts of mozilla,
• Removal of classes not necessary needed for small devices
• Configure options were added to disable features or components that included a variety of extra testing and debugging code, and some obsolete networking protocols such as finger and gopher.
• FTP has been removed but can be turned back on if required
• A lightweight preference system and chrome registry were developed and integrated.
• Tuning and memory use options to modify the standard desktop build of mozilla to better suit limited resource (No VM) devices were also enabled including disabling disk cache and reducing memory cache
• Current configure options for building minimo are found here
• The full list of Milestone 1 tasks can be found in Bugzilla under tracking bug 213938
• Initial test builds for Intel desktop machines have been created and pushed to ftp. Sanity checks have been run to test basic function of the minimo configuration. Initial testing looks good with only a few small regressions discovered and repairs are underway.
• The work has resulted in some reduction of footprint for the Mozilla Seamonkey suite, but also Memory footprint of the Minimo configuration has been cut by 40% over a full Seamonkey Mozilla Browser build (start up memory use is at about 10MBs on the Linux desktop test system).
  • PID SIZE RSS SHARE %MEM TIME CPU COMMAND
  • 10823 11672 11M 6964 9.2 0:05 0 Minimo
  • 10922 13124 12M 9224 10.5 0:02 0 TestGtkEmbed
  • 11168 20688 19M 8388 15.7 0:09 0 mozilla-bin

Milestone 2

• Milestone 2 will focus on porting and building a test plan to evaluate the completeness and suitability of the configuration on a few handheld devices.
• Minimo is currently ported to run on standard Linux desktop distributions, Windows, and ARM devices.
• Builds of minimo currently run and are being tested on Sharp Zaurus c7x0, Compaq 3950 iPAQ and 5555 iPAQ Linux based devices, leveraging work being done on the familiar Linux distribution and work underway on the handhelds.org project
• Several screenshots are avialable showing what the current version Minimo looks lilke on the iPAQ
• We are having problems finding the older 3950, and 5450 iPAQ devices and have shifted some work to the 5555. If you have a line on 3950's or 5450's drop us an e-mail.
• Current build instructions and tips are available here. Additional work is underway to describe how to build the full toolchain and install minimo on one of the target test devices
• Minimo build and alive test results are now visible on tinderbox ports page for a cross-compilation target=arm-linux gcc-3.3.1, and iPAQ test run.
• Pre-built packages of Minimo are now available on the Familiar Project's "IpkgFind: Your familiar search engine"
• Some work also seems to be underway for porting and distribution on PlayStation 2 with full versions of Mozilla Applications and porting for Minimo.

Milestone 3

• Execute tests and prepare a comprehensive evaluation that will report on additional work will be required to transform the TestGTKEmbed test application and minimo configuration into full fledged products that could ship to consumers.
• Profile of current memory use under simulated browsing sessions, and fixing any discovered memory leaks and bloat where possible.
• General testing of the TestGTKEmbed and the minimo configuration
  • Graceful degradation of any component or feature that has been removed from the standard mozilla build
  • General stability and correctness in loading top sites and selected browser tests in the areas of networking, security, performance.
• Feasibility of reducing the configuration to run on 32MB no VM devices.
• Additional footprint reduction tasks for the next round of development
• Comparison to features available on other microbrowser in the marketplace
• Adjusting content for best display and use on small screens.
• Generating a list of tasks to track for future work.

---