773
edits
Education/Projects/JetpackForLearning/Profiles/expressionWidjets: Difference between revisions
Education/Projects/JetpackForLearning/Profiles/expressionWidjets (view source)
Revision as of 03:25, 1 February 2010
, 1 February 2010→Project Status
| Line 13: | Line 13: | ||
== Project Status == | == Project Status == | ||
* phase two [http://taboca.github.com/Expression-Widgets/ Project Home Page, Video, and Prototype Install] | * phase two - [http://taboca.github.com/Expression-Widgets/ Project Home Page, Video, and Prototype Install] | ||
* phase two - [http://github.com/taboca/Expression-Widgets Source Code] | * phase two - [http://github.com/taboca/Expression-Widgets Source Code] | ||
* phase one[http://blog.taboca.com/jetpack-for-learning-submission Original Proposal] | * phase one - [http://blog.taboca.com/jetpack-for-learning-submission Original Proposal] | ||
=== Moving forward === | === Moving forward === | ||
| Line 23: | Line 23: | ||
* As students can share their statements under a same ongoing session, the system should explore interactive scenarios where teams can build more complex document-based structures together, such as a collaborative diagram. At this point it is not possible for user A to clone statements from user B. | * As students can share their statements under a same ongoing session, the system should explore interactive scenarios where teams can build more complex document-based structures together, such as a collaborative diagram. At this point it is not possible for user A to clone statements from user B. | ||
* Improve compatibility with server-side repositories. There are identified challenges as the system interacts with an existing wiki page. As an example, the image widget stores the image bits information using inline data in the wiki which can lead to huge sections in the wiki. We need to evaluate this model and also how wiki systems can deal with external applications. At this stage, the implementation of the transport mechanism deals with the wiki page using a hidden iframe. It is important to move to explore real web services interfaces as a means to read/write on behalf of users. | * Improve compatibility with server-side repositories. There are identified challenges as the system interacts with an existing wiki page. As an example, the image widget stores the image bits information using inline data in the wiki which can lead to huge sections in the wiki. We need to evaluate this model and also how wiki systems can deal with external applications. At this stage, the implementation of the transport mechanism deals with the wiki page using a hidden iframe. It is important to move to explore real web services interfaces as a means to read/write on behalf of users. | ||
== Concept of Widgets == | == Concept of Widgets == | ||