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
Products
TV-Server
For The Record - The rule-based scheduling suite
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="joboehl" data-source="post: 201349" data-attributes="member: 23490"><p>dvdfreak, sorry just jumping in now. </p><p></p><p>I agree with i-loop. Looking at the code (or the least the schematics) help a lot to estimate the coding effort to integrate your solution. </p><p></p><p>I don't know how many classes, interfaces or how your API looks like. I can see a lot of integration points all over the place from the TVEngine and the scheduler. </p><p></p><p>You see, refactoring TVE3 is a big change, adding a last updated column to a table is not that big of a change. Maybe we can find somewhere in the middle?</p><p></p><p>Don't get me wrong, I known your features are good, I respect and understand your architecture proposal, but it's something we can't change that easily, especially during a freeze and not knowing how much change we actually need. Without that, we don't know how much we can break in TVE3 for example. </p><p></p><p>As of now, TVE3Server structure is defined and new code should obey to it. Can it be improved? Probably, but it's how it is for V1. We are focusing on having it stable and reliable. You are more than welcome to help on it. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p></blockquote><p></p>
[QUOTE="joboehl, post: 201349, member: 23490"] dvdfreak, sorry just jumping in now. I agree with i-loop. Looking at the code (or the least the schematics) help a lot to estimate the coding effort to integrate your solution. I don't know how many classes, interfaces or how your API looks like. I can see a lot of integration points all over the place from the TVEngine and the scheduler. You see, refactoring TVE3 is a big change, adding a last updated column to a table is not that big of a change. Maybe we can find somewhere in the middle? Don't get me wrong, I known your features are good, I respect and understand your architecture proposal, but it's something we can't change that easily, especially during a freeze and not knowing how much change we actually need. Without that, we don't know how much we can break in TVE3 for example. As of now, TVE3Server structure is defined and new code should obey to it. Can it be improved? Probably, but it's how it is for V1. We are focusing on having it stable and reliable. You are more than welcome to help on it. :thx: [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Products
TV-Server
For The Record - The rule-based scheduling suite
Contact us
RSS
Top
Bottom