Reply to thread

Message: <blockquote data-quote="Oxan" data-source="post: 677611" data-attributes="member: 97484">Re: AW: Updated version for MediaPortal 1.1.1I haven't tried yet, but seen your experience with it I don't think it works <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" /> Hi,I am not related to the topic you quote (in fact, this is the first time I see it), but I really like the idea. This isn't a really offical release of MPWebServices, but I just integrated all patches flying around, fixed some reported bugs and updated the DLLs to the ones from Mediaportal 1.1.1, to have it work. At the technical side, you're right (at least for me). I'm basically a Linux user and PHP/Python programmer and haven't done much with .NET (nor am I planning to do something with it). But because Linux just sucks for multimedia (mainly because of missing drivers...), I decided to use MediaPortal+Windows for TV. Btw, in my version, I moved the config.xml outside the document root of the webserver, so at least that issue is fixed. My changes (basically the source of this version) is available on <a href="http://github.com/oxan/mpwebservices" target="_blank">github</a>, and I'm currently the only developer (aside from gemx, but he's busy with other things). I'm willing to accept any patches that make sense, so you can help. The problem is that I'm also quite limited in my time, so I haven't worked a lot on it yet, aside from fixing the things that I use (SOAP interface and streaming). I think it's the best to discard this project and just focus (with all of us) on the MPWeb code layer. I don't know the current state of it, but it seems like there are only some HTML designs yet. If someone with experience in .NET (you! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" /> ) would set up the basics, I'm glad to help with it. I think it's important to start with a working basic library (the MPWeb Code Layer), so that people can start building stuff on top it and help improve it. It would also be nice to design the API in a way that would allow it to easily port it to MP2, so all the apps that are going to use it also work with MP2. That would be really nice when MP2 gets stable. I totally agree with the rest of your post, but I think having to install and configure a separate webserver after the webservice is just painful. We should provide the option, but also bundle some kind of webserver. For more information, you can just ask (or send me a private message, possibly in Dutch, i'm sadly not that good at English).</blockquote>

Verification