Education/Projects/JetpackForLearning/DesignCamp/Projects/MUPPLE: Difference between revisions
< Education | Projects | JetpackForLearning | DesignCamp
Jump to navigation
Jump to search
No edit summary |
|||
| Line 9: | Line 9: | ||
== Really Short Term Goals == | == Really Short Term Goals == | ||
*distinguish between edit/play workflow | *[done] distinguish between edit/play workflow | ||
*expand the domain specificity, and open page, select tab on click | *[done] expand the domain specificity, and open page, select tab on click | ||
*create pseudo domains | *fork/clone page/pane <strike>create pseudo domains</strike> | ||
*add snapshot and Ubiquity command actions (pre LISL idea) | *add snapshot and Ubiquity command actions (pre LISL idea) | ||
*make a coherent annotation style | *make a coherent annotation style | ||
*link back from page to the slidebar | *[in progress] link back from page to the slidebar | ||
*export/import to RDF/XML | *export/import to RDF/XML | ||
*proof-of-concept FOAF/twitter based collaboration | *proof-of-concept FOAF/twitter based collaboration | ||
Revision as of 23:24, 10 March 2010
MUPPLE
For background info check the project profile.
Status
UI style is stable, some consistency check are needed; basic "actions" like link, form and note actions work and are persisted
Really Short Term Goals
- [done] distinguish between edit/play workflow
- [done] expand the domain specificity, and open page, select tab on click
- fork/clone page/pane
create pseudo domains - add snapshot and Ubiquity command actions (pre LISL idea)
- make a coherent annotation style
- [in progress] link back from page to the slidebar
- export/import to RDF/XML
- proof-of-concept FOAF/twitter based collaboration
- 2 sample workflows
Long Term Goals
- REBOOT, rebuilt it from scratch to mach the JetPack reboot
- Use OpenAnnotations style, to enable collaboration with other tools
- create a way to have 3rd party actions (sandboxed?)