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

Education/Projects/JetpackForLearning/Profiles/MUPPLE (view source)

2 bytes removed , 1 February 2010

Confirmed users

70

edits

Revision as of 03:30, 1 February 2010 (view source) Gridinoc (talk \| contribs) (→‎Technical Notes & Further Work) ← Older edit		Revision as of 03:30, 1 February 2010 (view source) Gridinoc (talk \| contribs) (→‎Technical Notes & Further Work) Newer edit →
Line 139:		Line 139:
	Xpointerlib proved quite useful in prototyping [[http://gridinoc.name/blog/2009/10/ubiquity-history/ recording]] and [[http://gridinoc.name/blog/2009/10/sharing-ubiquity-commands/ sharing]] of Ubiquity commands; having them as recordable actions in MUPPLE could enable the creation of workflows based on an ''open market'' of Ubiquity commands and provide by this a straight forward way in extending MUPPLE functionality.		Xpointerlib proved quite useful in prototyping [[http://gridinoc.name/blog/2009/10/ubiquity-history/ recording]] and [[http://gridinoc.name/blog/2009/10/sharing-ubiquity-commands/ sharing]] of Ubiquity commands; having them as recordable actions in MUPPLE could enable the creation of workflows based on an ''open market'' of Ubiquity commands and provide by this a straight forward way in extending MUPPLE functionality.

	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''.