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
Development
General Development (no feature request here!)
MDAPI: Pros and Cons
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="draktheas" data-source="post: 38221" data-attributes="member: 17330"><p>Personally, I understand not opening yourself up to legal action. However, I would like to point out that no legal counsel in their right mind would attempt to take legal action on support for a generic plugin framework that is in use by at least 5 other applications. Nor on a policy of non-tolerance regarding posting or discussion of decrypting signals. </p><p></p><p>As long as the MDAPI framework is supported generically (which it has to be in order to make use of all the plugins available) and the policy of non-tolerance on the boards holds, I can't see any reason not to add support for this.</p><p></p><p>I have been planning on writing support for MDAPI for over 2 months now and still plan to do it as soon as I am done with the TechnoTrend Premium support. Whether I do it as a patch or within MP, I will do it nonetheless. I prefer that it be a part of MP as that opens up a whole lot of useful plugins that MP developers won't have to write or duplicate and saves a lot of work. </p><p></p><p>I personally want to use it for Network multicasting, so I can watch on any computer in the house and there are a number of good plugins for that already written in MDAPI.</p><p></p><p>In my opinion, outlawing MDAPI as a framework from MP, is kind of like outlawing blow torches because they can be used to light a crack pipe. We just have to have a policy of 'no smokin' crack' (ahem, on the boards).</p><p></p><p>Just my 2 cents,</p><p>Drak</p></blockquote><p></p>
[QUOTE="draktheas, post: 38221, member: 17330"] Personally, I understand not opening yourself up to legal action. However, I would like to point out that no legal counsel in their right mind would attempt to take legal action on support for a generic plugin framework that is in use by at least 5 other applications. Nor on a policy of non-tolerance regarding posting or discussion of decrypting signals. As long as the MDAPI framework is supported generically (which it has to be in order to make use of all the plugins available) and the policy of non-tolerance on the boards holds, I can't see any reason not to add support for this. I have been planning on writing support for MDAPI for over 2 months now and still plan to do it as soon as I am done with the TechnoTrend Premium support. Whether I do it as a patch or within MP, I will do it nonetheless. I prefer that it be a part of MP as that opens up a whole lot of useful plugins that MP developers won't have to write or duplicate and saves a lot of work. I personally want to use it for Network multicasting, so I can watch on any computer in the house and there are a number of good plugins for that already written in MDAPI. In my opinion, outlawing MDAPI as a framework from MP, is kind of like outlawing blow torches because they can be used to light a crack pipe. We just have to have a policy of 'no smokin' crack' (ahem, on the boards). Just my 2 cents, Drak [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
MDAPI: Pros and Cons
Contact us
RSS
Top
Bottom