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

Jump to navigation Jump to search

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

Revision as of 20:41, 29 January 2010

167 bytes added ,  29 January 2010
→‎Widgets
Line 43: Line 43:
* (feedback/paula) Difficult to understand the save mechanism
* (feedback/paula) Difficult to understand the save mechanism


== Widgets ==
== Concept of Widgets ==


The concept of widgets is more like a wrapper or connector to a remote resource that can be incorporated to the expression experience. The real challenge now is to let participants to use the natural Web and be able to take the content from onlne remote apps in a way that the content can be edited and presented at the same time. For example if a remote service provides a drawing app, it is important the meta-data ( source ) and also the rendered views to be kept all together. We envision that user A may create Drawing A, and user B may want to clone drawing A as drawing B, using the meta/data and not the rendered view, and modify. The full R/W social cycle is the end goal.  
Widgets are helper applications that lets users to create and channel content into the session. The challenge now is to let participants use the natural Web ( apps and content available online ) and be able to associate the content from these apps into the experience. To illustrate a scenario, imagine that user A creates a drawing DA and user B may want to clone the drawing DA as drawing DB. User B wants to see the rendered view of DA as part of his/her moment of visualization. When it is time to edit, the original meta/data must be cloned and a editing view must exist. At this point, being the drawing app a Web-based app, the URL of the app must be loaded with the DA data feed into it. User B can then edit the drawing and again new meta/data and a rendered view must be generated and associated as an input from user B.  


At this point some widgets are local wrappers to remote apps, like the textify. In other cases we have local widgets - JavaScript code that is bundled together with the Expression Widgets prototype.  
At this stage, some widgets are local wrappers to remote apps, like the textify case. In other cases, we have local widgets - JavaScript code that is bundled together with the Expression Widgets prototype.  


* Canvas-based drawing apps - We need a very simple drawing app that can be canvas-based however the data to be kept as markup/meta-data and not pixels;  
* Canvas-based drawing apps - We need a very simple drawing app that can be canvas-based however the data to be kept as markup/meta-data and not pixels;  
Mgalli
773

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/197832"

Navigation menu