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?
What to do about the webinterface?
Started by calandril, 05 Oct 2011 18:22
4 replies to this topic
Re: What to do about the webinterface? #2
Posted 5 October 2011 - 18:48
Welcome on this forum.
Did you check this thread? http://openpli.org/f...e2-openplugins/
It's not specific about the web interface, but about creating a common repository in which everbody can start developing. It may take some time before all's in place.
I can't answer your specific questions now, but maybe the users can post their wishes in here in this thread.
Did you check this thread? http://openpli.org/f...e2-openplugins/
It's not specific about the web interface, but about creating a common repository in which everbody can start developing. It may take some time before all's in place.
I can't answer your specific questions now, but maybe the users can post their wishes in here in this thread.
Many answers to your question can be found in our wiki: http://openpli.org/wiki
Re: What to do about the webinterface? #3
Re: What to do about the webinterface? #4
Re: What to do about the webinterface? #5
Posted 30 October 2011 - 18:44
As I have seen work has already been started on another thread...
http://openpli.org/f...post__p__223070
Hardware: Master VU Uno 4K SE 1x Mut@nt HD51.4K & 2x ZgemmaH9T
Software : Pli (v7) (7.1rc) 2019
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users