Reply to thread

Message

<blockquote data-quote="infinite.loop" data-source="post: 363349" data-attributes="member: 10723">for a start you could just copy/paste that into a wiki page.noone demands perfectly styled wiki pages. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />this indeed is a problem, MPI will not be able to adress this case in MediaPortal 1.the reason is that TV-Server is not &quot;supported&quot;, and i am not sure if we can add it (in MediaPortal 1).In MediaPortal 2, we do not have this problem anymore.what me might could still do is add a &quot;special section&quot; for these plugins inside the MPI application.So the user will still &quot;find&quot; these plugins when browsing the list inside MPI.The description should then tell the user that he has to &quot;manually&quot; install this extension.So you just upload your extension to the repository on the homepage (no MPI), but users will see it when browsing the list of extensions inside MPI.This will not make the installation easier for the end-user, but might draw more attention to you extension then and allows to browse &quot;all extensions&quot; in one application. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="infinite.loop, post: 363349, member: 10723"] for a start you could just copy/paste that into a wiki page. noone demands perfectly styled wiki pages. ;) this indeed is a problem, MPI will not be able to adress this case in MediaPortal 1. the reason is that TV-Server is not "supported", and i am not sure if we can add it (in MediaPortal 1). In MediaPortal 2, we do not have this problem anymore. what me might could still do is add a "special section" for these plugins inside the MPI application. So the user will still "find" these plugins when browsing the list inside MPI. The description should then tell the user that he has to "manually" install this extension. So you just upload your extension to the repository on the homepage (no MPI), but users will see it when browsing the list of extensions inside MPI. This will not make the installation easier for the end-user, but might draw more attention to you extension then and allows to browse "all extensions" in one application. :) [/QUOTE]

Verification