Jump to content


calandril

Member Since 5 Oct 2011
Offline Last Active 24 Nov 2011 20:59
-----

Topics I've Started

Web streaming plugin

30 October 2011 - 18:39

As there are already programmer on the webinterface track, I though about doing something smaller to getting my feets wet with the e*2 platform.
Before having a e*2 box I have programmed some webstreaming software for series and movies from internet providers for my DLNA Server.
Since I have a media box with the capability to execute custom code, i would like to program something similiar for this platfrom.
I think there is no plugin at this time for streaming megavideo or divxstage etc. content on the box right now, or is there?
I found something for the XMBC platform (xstream) that looks promissing, but unfortunately the UI is thightly coded in the plugin. I tried some refacturing, but it seems a lot of work probably it is better to start new.
Does this plugin idea sounds interessting? Does any one like to join?
Right now I have a bit hard time getting in the e*2 development platform.
Currently I use PhyDev fro eclipse for developping Python code. Does anyone has setup a sample eclipse project for creating an e*2 plugin? Or any other hints/sources?
To get streaminfg running I am curently analyzing the ARD/ZDF Mediathek Plugins, is this a good starting point, or are there more easy plugins to study?

What to do about the webinterface?

5 October 2011 - 18:22

I do not know if this is the correct place for my request...

The webinterface is a important part of an installation. Maybe it is a good idea to start a open source implementation.

I think it is not realistic that a single person will come up soon with a coomplete replacement on his own.
As many users seem to have an affinity to programming, it should be possible to break down the implementation in more isolated tasks.
I am quite new to the enigma platfrom. I have obeserved that many users (like me) are willing to
to give back to the community by improving the existing code base. I think this project can be a good point, since it is really needed.

To start such a project it is necessary to collect information like:[list]
[*]What is the current functionality of the webinterface?
[*]What functions are needed first, which should be changed?
[*]What is good, what is not needed, what is missing, what should be improved?
[*]Is partial of the code reusable because it is from a different developper, coded under a different license or code from a time with different license restrictions?
[*]Can code from other source be used?
[/list]
Is it possible to break the webinterface into different layers?
For example:[list]
[*]basic functionality in from of a library that canbe reused by other plugins/projects
[*]a webservice interface that allows external clients access to the box. For example for Webbrowsers, Android/iPhone Apps, Partner-Box-Applications, Desktop Progs like TV-Browser Plugin etc.
[*]A Webinterface (using JQuery?).
[/list]
My vision would be to offer basic functionality for other plugin developpers too. The basic functions might be bundled in an extension lib along the enigma 2 api – let it name something like 'openbox api'. Inside the lib can be gathered general functionality that might be reused. In this way other developpers may contribute, too.
Hardware dependend functionality should be encapsulated with an api.
If we use a versioning system for the libs, the plugin manager can use these for gathering plugins that work seamlessly together.

Does this visIon seem realistic?
Maybe we can use this complicate situation as a chance to integrate the existing extentsions and bring the whole platform a step forward?