home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
New Webinterface
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="samuel337" data-source="post: 128858" data-attributes="member: 10347"><p><a href="http://hevea.sourceforge.net/" target="_blank">http://hevea.sourceforge.net/</a></p><p></p><p>Hmm, looks good. I'm for using this instead in principle; will have to see how it works in reality.</p><p></p><p></p><p></p><p>I agree completely. The IIS option is there purely because some people already have web servers running and want it on that computer. It won't be the standard/recommend/supportedway of running it.</p><p></p><p></p><p></p><p>There was going to be some sort of abstraction layer; I just hadn't gotten that far yet. But you're proposing an abstraction layer used by both the web service and web app right? Can I ask what sort of abstraction you're proposing?</p><p></p><p></p><p></p><p>I couldn't be bothered getting an account to get access, but I assume that your plugin is a plugin for the TV server right? How does it differ from TvControl.dll?</p><p></p><p>Just to clarify for everyone; ECP2 is for controlling MP clients, and only to be installed on MP clients.</p><p></p><p></p><p></p><p>What kind of requests are you talking about?</p><p></p><p>I created a general UDPMCHelper class to implement this, so if you want, go to the mp-webinterface sf SVN repo, and get the file in trunk\source\ECP2Assembly\clsUdpMCHelper.cs. It should be pretty straight forward to use.</p><p></p><p>This is different to the UdpHelper class in MP btw, which is a unicast Udp helper.</p><p></p><p></p><p></p><p>Well, it doesn't really make sense to have two web interfaces, one for controlling it and another for the TV server. BTW, as the music databases are still client-based, it would be quite tedious to use straight SQL and connect to each SQLite database individually (e.g. you'd have to ensure that each MP client has the database folder shared first).</p><p></p><p>The remote control feature isn't just your typical remote control. Imagine you're watching a channel while you're browsing the web interface tv guide, discover something good on another channel, and all you'd have to do is click the program, select an MP client and it'll automatically switch that client to that channel. </p><p></p><p>----------</p><p></p><p>I think right now there's really two parts to this project: one is the main web interface, and the other is the web server and other communication components. I think the first target for the project is to get the TV functionality working first. We already have the TvBusinessLayer and TvControl, so apart from the web server and ECP2 (which will only play a minor role initially), the backend bits are mostly there already.</p><p></p><p>Most of you already have some sort of web server going on anyway, so I think work on the web interface should be able to go forward from ideas to actual implementations.</p><p></p><p><strong>One question though - are we discontinuing any support for the old tv engine in this new web interface?</strong></p><p></p><p>I might shift my attention over to working on the web server for the time being, seeing as its the most needed component at the moment.</p><p></p><p>I love this momentum <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite6" alt=":cool:" title="Cool :cool:" loading="lazy" data-shortname=":cool:" /> </p><p></p><p>Sam</p></blockquote><p></p>
[QUOTE="samuel337, post: 128858, member: 10347"] [url]http://hevea.sourceforge.net/[/url] Hmm, looks good. I'm for using this instead in principle; will have to see how it works in reality. I agree completely. The IIS option is there purely because some people already have web servers running and want it on that computer. It won't be the standard/recommend/supportedway of running it. There was going to be some sort of abstraction layer; I just hadn't gotten that far yet. But you're proposing an abstraction layer used by both the web service and web app right? Can I ask what sort of abstraction you're proposing? I couldn't be bothered getting an account to get access, but I assume that your plugin is a plugin for the TV server right? How does it differ from TvControl.dll? Just to clarify for everyone; ECP2 is for controlling MP clients, and only to be installed on MP clients. What kind of requests are you talking about? I created a general UDPMCHelper class to implement this, so if you want, go to the mp-webinterface sf SVN repo, and get the file in trunk\source\ECP2Assembly\clsUdpMCHelper.cs. It should be pretty straight forward to use. This is different to the UdpHelper class in MP btw, which is a unicast Udp helper. Well, it doesn't really make sense to have two web interfaces, one for controlling it and another for the TV server. BTW, as the music databases are still client-based, it would be quite tedious to use straight SQL and connect to each SQLite database individually (e.g. you'd have to ensure that each MP client has the database folder shared first). The remote control feature isn't just your typical remote control. Imagine you're watching a channel while you're browsing the web interface tv guide, discover something good on another channel, and all you'd have to do is click the program, select an MP client and it'll automatically switch that client to that channel. ---------- I think right now there's really two parts to this project: one is the main web interface, and the other is the web server and other communication components. I think the first target for the project is to get the TV functionality working first. We already have the TvBusinessLayer and TvControl, so apart from the web server and ECP2 (which will only play a minor role initially), the backend bits are mostly there already. Most of you already have some sort of web server going on anyway, so I think work on the web interface should be able to go forward from ideas to actual implementations. [B]One question though - are we discontinuing any support for the old tv engine in this new web interface?[/B] I might shift my attention over to working on the web server for the time being, seeing as its the most needed component at the moment. I love this momentum :cool: Sam [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
New Webinterface
Contact us
RSS
Top
Bottom
