Hello,
we, the University of Osnabrueck, would like to propose a new architecture for
the engage player.
As we all know the current engage player has some problems.
No plugin is really independent from the other plugins, you just can't simply
extend the player without having to adjust other plugins.
New developers have to know the coherences before they are able to start
developing.
Besides the 'shared-resource' folder contains the whole player structure, the
player and its plugins, means, the plugins are not in its related OSGi modules.
We want to solve this problems and many others as well with the following
proposal:
- implementing a strict plugin-architecture using backbone.js
- every single component is a plugin
- event-based data exchange
- no plugin knows about another plugin but can listen to events thrown by
another event
- unification of technologies (such as html5 and flash)
- extension of new technologies (such as WebVTT)
For a more detailed technical overview have a look at the New Engage Player
page at JIRA (http://opencast.jira.com/wiki/display/MH/New+Engage+Player ) and
feel free to comment.
We didn't plan every detail right now, it's just an idea, so we do have a lot
of open questions to be solved, e.g.:
How can we use backbone.js best to use it as the plugin provider?
What about other (open) standards, e.g. MediaFragments?
How to solve the streaming issues (support, interchangeability of streaming
servers, etc.)?
Sincerely,
Denis Meyer
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
