Difference between revisions of "MozCC Development"
| Line 8: | Line 8: | ||
== Planned Features == | == Planned Features == | ||
| + | |||
| + | === MozCC NG === | ||
| + | |||
| + | * Split extraction and presentation into two, decoupled extensions. | ||
| + | * Define a communication mechanism between the two (events?) that others can emulate | ||
| + | * Distribute as an [http://developer.mozilla.org/en/docs/Multiple_Item_Packaging XPI Bundle] | ||
| + | * Stability and performance for the "core" extension | ||
=== MozCC 2.4.x === | === MozCC 2.4.x === | ||
Revision as of 20:16, 19 February 2007
MozCC is written using Javascript and XUL. The source repository is hosted in the cctools project at SourceForge.net in the mozcc2 module.
Contents
Planned Features
MozCC NG
- Split extraction and presentation into two, decoupled extensions.
- Define a communication mechanism between the two (events?) that others can emulate
- Distribute as an XPI Bundle
- Stability and performance for the "core" extension
MozCC 2.4.x
(may get rolled into 2.6)
- Support for Flock (post 0.7.x)
MozCC 2.6
- Restructure code to wrap all the functionality in a single object (to prevent namespace collisions)
- Support for licensing of embedded objects (images, etc).
- Support for i18n
Notes/Links
- http://blog.mozilla.com/faaborg/2007/02/04/microformats-part-4-the-user-interface-of-microformat-detection/ Ideas on exposing embedded metadata in the UI
Future Directions
- Personal Metadata Store: allow users to browse metadata collected by MozCC
Other Firefox Extension Points
- Scrapbook -- license information should travel with scraped content
