Education/Projects/JetpackForLearning/Profiles/MUPPLE - Revision history

Kemorgan65: Change link to Mupple download and bracketed instruction (the instruction needs to be confirmed, i.e. on how to install Mupple after download).

2015-11-25T21:19:09Z

Change link to Mupple download and bracketed instruction (the instruction needs to be confirmed, i.e. on how to install Mupple after download).

← Older revision		Revision as of 21:19, 25 November 2015
Line 10:		Line 10:
	2) MUPPLE II runs on Jetpack. Get your own Jetpack at https://addons.mozilla.org/en-US/firefox/addon/12025 (version 0.8.1).		2) MUPPLE II runs on Jetpack. Get your own Jetpack at https://addons.mozilla.org/en-US/firefox/addon/12025 (version 0.8.1).

	3) You are one-step away from your first MUPPLE II experience. Get the latest version at ~~http~~://~~purl~~.~~org~~/ou/~~mupple~~ (see ~~install~~ button ~~at the top~~ right ~~side of the page~~).		3) You are one-step away from your first MUPPLE II experience. Get the latest version at https://github.com/Laurian/MUPPLE (see download zip button in right hand column).

	You are now ready to trace and replay the web!		You are now ready to trace and replay the web!

TUllmann: /* Original Proposal */

2010-03-29T20:55:41Z

Original Proposal

← Older revision		Revision as of 20:55, 29 March 2010
Line 159:		Line 159:

	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.

			=Who did it?=
			MUPPLE II is brought to you by the Knowledge Media Institute of the Open University, UK.

			The MUPPLE team are:
			# Laurian Gridinoc (http://kmi.open.ac.uk/people/member/laurian-gridinoc)
			# Fridolin Wild (http://kmi.open.ac.uk/people/member/fridolin-wild)
			# Thomas Ullmann (http://kmi.open.ac.uk/people/member/thomas-ullmann)
			For more information visit the MUPPLE technology page: http://kmi.open.ac.uk/technologies/name/Mupple



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

TUllmann: /* Get started now! */

2010-03-27T00:07:59Z

Get started now!

← Older revision		Revision as of 00:07, 27 March 2010
Line 8:		Line 8:
	1) MUPPLE II is designed as Firefox Jetpack. Because it's cool, it is for free and open source. If you have not already switched to the 'world’s best browser', download it from http://www.mozilla-europe.org/en/firefox/ (recommended version: 3.6 and higher).		1) MUPPLE II is designed as Firefox Jetpack. Because it's cool, it is for free and open source. If you have not already switched to the 'world’s best browser', download it from http://www.mozilla-europe.org/en/firefox/ (recommended version: 3.6 and higher).

	2) MUPPLE II runs on Jetpack. ~~To get~~ your own Jetpack ~~plugin, install it~~ at https://addons.mozilla.org/en-US/firefox/addon/12025 (version 0.8.1).		2) MUPPLE II runs on Jetpack. Get your own Jetpack at https://addons.mozilla.org/en-US/firefox/addon/12025 (version 0.8.1).

	3) You are one-step away from your first MUPPLE II experience. Get the latest version at http://purl.org/ou/mupple (see install button at the top right side of the page).		3) You are one-step away from your first MUPPLE II experience. Get the latest version at http://purl.org/ou/mupple (see install button at the top right side of the page).

TUllmann: /* Get started now! */

2010-03-26T18:06:13Z

Get started now!

← Older revision		Revision as of 18:06, 26 March 2010
Line 8:		Line 8:
	1) MUPPLE II is designed as Firefox Jetpack. Because it's cool, it is for free and open source. If you have not already switched to the 'world’s best browser', download it from http://www.mozilla-europe.org/en/firefox/ (recommended version: 3.6 and higher).		1) MUPPLE II is designed as Firefox Jetpack. Because it's cool, it is for free and open source. If you have not already switched to the 'world’s best browser', download it from http://www.mozilla-europe.org/en/firefox/ (recommended version: 3.6 and higher).

	2) MUPPLE II runs on Jetpack. To get your own Jetpack plugin, ~~download~~ it at https://~~jetpack~~.~~mozillalabs~~.~~com~~/~~index~~.~~html (bottom of the page~~).		2) MUPPLE II runs on Jetpack. To get your own Jetpack plugin, install it at https://addons.mozilla.org/en-US/firefox/addon/12025 (version 0.8.1).

	3) You are one-step away from your first MUPPLE II experience. Get the latest version at http://purl.org/ou/mupple (see install button at the top right side of the page).		3) You are one-step away from your first MUPPLE II experience. Get the latest version at http://purl.org/ou/mupple (see install button at the top right side of the page).

Gridinoc: /* Technical Notes & Further Work */

2010-02-04T16:28:34Z

Technical Notes & Further Work

← Older revision		Revision as of 16:28, 4 February 2010
Line 121:		Line 121:
	* Slidebar javascript: http://github.com/Laurian/MUPPLE/blob/master/script/slide.js		* Slidebar javascript: http://github.com/Laurian/MUPPLE/blob/master/script/slide.js

	'If github has issues, you can see the raw sources:'		''If github has issues, you can see the raw sources:''

	* Jetpack code: http://purl.org/ou/mupple/script/core.js		* Jetpack code: http://purl.org/ou/mupple/script/core.js

Gridinoc: /* Technical Notes & Further Work */

2010-02-04T16:27:34Z

Technical Notes & Further Work

← Older revision		Revision as of 16:27, 4 February 2010
Line 120:		Line 120:
	* Slidebar html code: http://github.com/Laurian/MUPPLE/blob/master/slidebar.html		* Slidebar html code: http://github.com/Laurian/MUPPLE/blob/master/slidebar.html
	* Slidebar javascript: http://github.com/Laurian/MUPPLE/blob/master/script/slide.js		* Slidebar javascript: http://github.com/Laurian/MUPPLE/blob/master/script/slide.js

			'If github has issues, you can see the raw sources:'

			* Jetpack code: http://purl.org/ou/mupple/script/core.js
			* Slidebar html code: http://purl.org/ou/mupple/slidebar.html
			* Slidebar javascript: http://purl.org/ou/mupple/script/slide.js


	We adapted some cross-site scripting style strategies in order to achieve a tight coordination between Jetpack and the code in the slidebar; therefore we use a hidden iframe (fed with data URIs) to communicate from the slidebat to jetpack (which listens for the load event), while from jetpack to slidebar or to any tab we inject script tags with raw code or JSONP.		We adapted some cross-site scripting style strategies in order to achieve a tight coordination between Jetpack and the code in the slidebar; therefore we use a hidden iframe (fed with data URIs) to communicate from the slidebat to jetpack (which listens for the load event), while from jetpack to slidebar or to any tab we inject script tags with raw code or JSONP.

Gridinoc: /* Get started now! */

2010-02-04T16:25:16Z

Get started now!

← Older revision		Revision as of 16:25, 4 February 2010
Line 10:		Line 10:
	2) MUPPLE II runs on Jetpack. To get your own Jetpack plugin, download it at https://jetpack.mozillalabs.com/index.html (bottom of the page).		2) MUPPLE II runs on Jetpack. To get your own Jetpack plugin, download it at https://jetpack.mozillalabs.com/index.html (bottom of the page).

	3) You are one-step away from your first MUPPLE II experience. Get the latest version at http://purl.org/ou/mupple/ (see install button at the top right side of the page).		3) You are one-step away from your first MUPPLE II experience. Get the latest version at http://purl.org/ou/mupple (see install button at the top right side of the page).

	You are now ready to trace and replay the web!		You are now ready to trace and replay the web!

Gridinoc: /* Get started now! */

2010-02-04T16:24:54Z

Get started now!

← Older revision		Revision as of 16:24, 4 February 2010
Line 10:		Line 10:
	2) MUPPLE II runs on Jetpack. To get your own Jetpack plugin, download it at https://jetpack.mozillalabs.com/index.html (bottom of the page).		2) MUPPLE II runs on Jetpack. To get your own Jetpack plugin, download it at https://jetpack.mozillalabs.com/index.html (bottom of the page).

	3) You are one-step away from your first MUPPLE II experience. Get the latest version at http://purl.org/ou/mupple (see install button at the top right side of the page).		3) You are one-step away from your first MUPPLE II experience. Get the latest version at http://purl.org/ou/mupple/ (see install button at the top right side of the page).

	You are now ready to trace and replay the web!		You are now ready to trace and replay the web!

Gridinoc: /* Technical Notes & Further Work */

2010-02-01T13:08:14Z

Technical Notes & Further Work

← Older revision		Revision as of 13:08, 1 February 2010
Line 116:		Line 116:

	The current [[http://github.com/Laurian/MUPPLE prototype code]] is quite hard to follow, it has grown organically around various real and supposed limitations of Jetpack.		The current [[http://github.com/Laurian/MUPPLE prototype code]] is quite hard to follow, it has grown organically around various real and supposed limitations of Jetpack.

			* Jetpack code: http://github.com/Laurian/MUPPLE/blob/master/script/core.js
			* Slidebar html code: http://github.com/Laurian/MUPPLE/blob/master/slidebar.html
			* Slidebar javascript: http://github.com/Laurian/MUPPLE/blob/master/script/slide.js

	We adapted some cross-site scripting style strategies in order to achieve a tight coordination between Jetpack and the code in the slidebar; therefore we use a hidden iframe (fed with data URIs) to communicate from the slidebat to jetpack (which listens for the load event), while from jetpack to slidebar or to any tab we inject script tags with raw code or JSONP.		We adapted some cross-site scripting style strategies in order to achieve a tight coordination between Jetpack and the code in the slidebar; therefore we use a hidden iframe (fed with data URIs) to communicate from the slidebat to jetpack (which listens for the load event), while from jetpack to slidebar or to any tab we inject script tags with raw code or JSONP.

Gridinoc: /* Technical Notes & Further Work */

2010-02-01T05:21:56Z

Technical Notes & Further Work

← Older revision		Revision as of 05:21, 1 February 2010
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 ~~because~~ a ''reboot'' of MUPPLE II is required, and we plan to do it in February.		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.