Denis, > 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.
> 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. So I assume you are in agreement that the original Engage player must stay until all of the features people expect are ported over? I'm fine with that, though I hope that the wiki page will evolve to include as many stakeholders as possible. Multiple people co-developing the codebase is a good thing I think. I'm happy to help do some reviews, though I have limited capacity... Chris _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
