Confirmed users
70
edits
Education/Projects/JetpackForLearning/Profiles/MUPPLE: Difference between revisions
Education/Projects/JetpackForLearning/Profiles/MUPPLE (view source)
Revision as of 05:21, 1 February 2010
, 1 February 2010→Technical Notes & Further Work
| Line 145: | Line 145: | ||
As we already mentioned, a LISL implementation on top of the Ubiquity's [[Labs/Ubiquity/Parser_2|Parser 2]] might allow for a tight integration between LISL and existing Ubiquity commands, and it might leverage the [[Labs/Ubiquity/Parser_2/Localization_Tutorial|localization possibilities of the parser]] if needed. | As we already mentioned, a LISL implementation on top of the Ubiquity's [[Labs/Ubiquity/Parser_2|Parser 2]] might allow for a tight integration between LISL and existing Ubiquity commands, and it might leverage the [[Labs/Ubiquity/Parser_2/Localization_Tutorial|localization possibilities of the parser]] if needed. | ||
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 | 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; therefore we did not add extra functionality just for the sake of a prototype, we believe that 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. | ||