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

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

883 bytes added , 29 January 2010

773

edits

@@ Line 43: / Line 43: @@
 * (feedback/paula) Difficult to understand the save mechanism
-=== Widgets ===
+== 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.
+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.
 * 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;