Hi Chris, On 21.11.2012, at 5:31 PM, "Brooks, Chris" <[email protected]> wrote:
> Hi Denis, > > At a quick glance this all looks great, but here are my concerns: > > 1. Is this going to open up cross browser testing issues? Lots of problems > in the past with IE support/etc., and I imagine this will continue. Are the > resources around to test this new interface? It's not just a new interface, it's the whole architecture that we want to change. And I think there will be some cross-browser issues as usual but only in some of the views of some plugins. I hope the frameworks that we want to use handle their functionality issues in different browsers "on their own", e.g. backbone.js-events. > 2. Is UoO going to port existing functionality from the current engage player > to the new one? E.g. we're building dependencies on the logging features > that are in the current one, but this isn't generally considered a priority > for the UI. Will these changes be ported over as well? Is it just a > technology change, or is there a functionality change as well? At first we just want to provide the architecture and some basic plugins (e.g. the videodisplay (html5, flash?)), after that we can talk about porting existing plugins or create new ones from scratch. So basically it's a whole new engage player. Our hope is that it is much easier to write and integrate new plugins. > I like most of what you have written, but I don't know the technologies very > well. Regards, > > Chris > ________________________________________ > From: [email protected] > [[email protected]] on behalf of Denis Meyer > [[email protected]] > Sent: 21 November 2012 10:22 > To: [email protected] > Subject: [Opencast Matterhorn] Proposal: New Engage Player > > 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] > _______________________________________________ _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
