Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 199951" data-attributes="member: 21313">Sure, understandable.&nbsp; But sometimes you have to break some eggs to make an omelet <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />The basic question is this: does TvScheduler offer a big enough improvement to do some real rework in TVE3?If it's not considered to be worthwhile, I can deal with that, let's move on then.&nbsp; If it is considered worthwhile, let's talk about the symbiosis I propose.Hehe <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />&nbsp; TvScheduler's guide data is far more detailed as the one kept in TVE3, so I can't use its database even if I wanted to.&nbsp; All I could do is try and duplicate the data (but then still, useful information would be missing), but as tourettes pointed out, it would be rather stupid in the long run to keep all data in two databases.I consider the plugin I provided really as a temporary tool, to test TvScheduler further, to make it actually do something practical.The fear of breaking something is understandable, but I think noone is suggesting this should be part of next week's release.&nbsp; Let's branch of the code, change things, and then when things are stable again we can merge this back into the trunk.&nbsp; Hey, it may even turn out to be much less of a hassle than is feared <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Nope, not yet, I'll try to pop on to IRC later today, perhaps some devs are online then too...</blockquote>

[QUOTE="dvdfreak, post: 199951, member: 21313"] Sure, understandable. But sometimes you have to break some eggs to make an omelet :D The basic question is this: does TvScheduler offer a big enough improvement to do some real rework in TVE3? If it's not considered to be worthwhile, I can deal with that, let's move on then. If it [I]is[/I] considered worthwhile, let's talk about the symbiosis I propose. Hehe ;) TvScheduler's guide data is far more detailed as the one kept in TVE3, so I can't use its database even if I wanted to. All I could do is try and duplicate the data (but then still, useful information would be missing), but as tourettes pointed out, it would be rather stupid in the long run to keep all data in two databases. I consider the plugin I provided really as a temporary tool, to test TvScheduler further, to make it actually do something practical. The fear of breaking something is understandable, but I think noone is suggesting this should be part of next week's release. Let's branch of the code, change things, and then when things are stable again we can merge this back into the trunk. Hey, it may even turn out to be much less of a hassle than is feared :) Nope, not yet, I'll try to pop on to IRC later today, perhaps some devs are online then too... [/QUOTE]

Verification