Education/Projects/JetpackForLearning/Profiles/MUPPLE: Difference between revisions

Jump to navigation Jump to search
Line 141: Line 141:
Moreover, think of the possibilities that the sole command ''translate'' from Ubiquity could bring to MUPPLE: ''collaboration that spans language barriers''.
Moreover, think of the possibilities that the sole command ''translate'' from Ubiquity could bring to MUPPLE: ''collaboration that spans language barriers''.


Right now the prototype as UI is pretty much what we envisioned, but with partial functionality; this is mostly due not to the difficulties in added the envisioned functionality, but when observing, hands-on, that some activities must be separated, namely editing a workflow and "replaying" a workflow have to be distinct, as controls, as visual state communicated to the user; we did not add extra functionality for the sake of a prototype because  a ''reboot'' of MUPPLE II is required, and we plan to do it in February.


A ''reboot'' of MUPPLE II is required, and we plan to do it in February. After learning how to fly a Jetpack we can now focus on core functionality, code clarity and unit testing.
After learning how to fly a Jetpack we can now focus on core functionality, code clarity and unit testing.


=Original Proposal=
=Original Proposal=
The initial [[vision MUPPLE II|vision of the MUPPLE II]] Firefox Jetpack talks more about the motivation and introduces a use case to write collaboratively a paper using Web 2.0 webpages.
The initial [[vision MUPPLE II|vision of the MUPPLE II]] Firefox Jetpack talks more about the motivation and introduces a use case to write collaboratively a paper using Web 2.0 webpages.
Confirmed users
70

edits

Navigation menu