773
edits
Education/Projects/JetpackForLearning/Profiles/expressionWidjets: Difference between revisions
Jump to navigation
Jump to search
Education/Projects/JetpackForLearning/Profiles/expressionWidjets (view source)
Revision as of 03:21, 1 February 2010
, 1 February 2010→Concept of Widgets
No edit summary |
|||
| Line 36: | Line 36: | ||
Widgets are helper applications that can help participants to create and format content into the collaborative session. In this context, a major challenge is how 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. | Widgets are helper applications that can help participants to create and format content into the collaborative session. In this context, a major challenge is how 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 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. The end goal is to keep all the widgets online and not a local repository with installed code. Participants should be able to simply import widgets that are being referenced from the wiki-based documents. This model suggests a highly scalable widget architecture where participants can be creative | 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. The end goal is to keep all the widgets online and not a local repository with installed code - what we have at this stage ( 0.5.8 release ). Participants should be able to simply import widgets that are being referenced from the wiki-based documents. This model suggests a highly scalable widget architecture where participants can be creative and express their ideas with online apps available on the web. It may also be interesting to explore licensing and expose the culture of flexible licenses to the participants session. This way, knowing that an online app can generate content under flexible licenses, such as creative commons, users may experience improved collaboration opportunities. | ||
A number of current widgets implemented and locally added to the ExpressionWidgets JetPack application. These widgets should be considered as examples of applications that can support participants to express their thoughts for an ongoing session: | |||
* (done) Textify - http://www.texify.com/ | * (done) Textify - http://www.texify.com/ | ||