Reply to thread

Message

<blockquote data-quote="infinite.loop" data-source="post: 364453" data-attributes="member: 10723">Actually i am not sure what you are proposing. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused&nbsp; &nbsp; :confused:" loading="lazy" data-shortname=":confused:" />Because as i read your post, everything would stay as it is atm.Or do you propose that we should include 4TR as closed source binary version (or 3rd party application) in TV-Server and remove our current recording and scheduler parts?Technically this is possible, but we then would have this:Pro:
<ul>
<li data-xf-list-type="ul">User installs MediaPortal and allready has 4TR &quot;inbuild&quot;</li>
</ul>Con: <ul>
<li data-xf-list-type="ul">without access to the sourcecode of 4TR:<ul>
<li data-xf-list-type="ul">we can not fix bugs, we find</li>
<li data-xf-list-type="ul">we can not do changes we, or our users consider as required</li>
<li data-xf-list-type="ul">debuging issues is a big problem, if they are caused in the scheduler/recording section</li>
</ul></li>
<li data-xf-list-type="ul">if 4TR is &quot;stopped&quot; in 2 years, or goes commercial, then TV-Server does not have an recording or scheduler anymore</li>
</ul>As you can imagine, this is no option for us, nor our users.I only see these 2 options:<ul>
<li data-xf-list-type="ul">completelly integrate 4TR sources into MediaPortal/TV-Server svn, under gpl</li>
<li data-xf-list-type="ul">keep 4TR a community plugin where the core service/application stays closed source. if we can do changes to our TV-Server in order to allow you to improove 4TR, let us know. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></li>
</ul></blockquote>

[QUOTE="infinite.loop, post: 364453, member: 10723"] Actually i am not sure what you are proposing. :S Because as i read your post, everything would stay as it is atm. Or do you propose that we should include 4TR as closed source binary version[I] (or 3rd party application)[/I] in TV-Server and remove our current recording and scheduler parts? Technically this is possible, but we then would have this: [B][B][COLOR="Green"]Pro:[/COLOR][/B][/B] [LIST] [*]User installs MediaPortal and allready has 4TR "inbuild" [/LIST] [B][COLOR="Red"]Con:[/COLOR][/B] [LIST] [*]without access to the sourcecode of 4TR: [LIST] [*]we can not fix bugs, we find [*]we can not do changes we, or our users consider as required [*]debuging issues is a big problem, if they are caused in the scheduler/recording section [/LIST] [*]if 4TR is "stopped" in 2 years, or goes commercial, then TV-Server does not have an recording or scheduler anymore [/LIST] As you can imagine, this is no option for us, nor our users. I only see these 2 options: [LIST=A] [*]completelly integrate 4TR sources into MediaPortal/TV-Server svn, under gpl [*]keep 4TR a community plugin where the core service/application stays closed source. if we can do changes to our TV-Server in order to allow you to improove 4TR, let us know. :) [/LIST] [/QUOTE]

Verification