Reply to thread

Message

<blockquote data-quote="ajp8164" data-source="post: 862968" data-attributes="member: 64375">Not easy, and not do-able in the 1.3 time frame (at least by me ;-)&nbsp; Dealing directly with the database will introduce a lot of risk in terms of time to understand, design, complete. I have no idea what the impact of changing the table schema of the tv database would be, nor do I understand the process for upgrading existing database installations. For 1.3 (at least) we'll need to stick with the current architecture. I can make some slight enhancements (including dumping the idea of skin settings being involved at all - just stick with MediaPortal.xml). I'll also rewrite the wiki to make it simple to understand and use.&nbsp;In principle I could agree that storing genre mapping information in the database makes sense but I'm not on board with putting color information in the database. Color info should live as close to the UI as possible; that's why I initially placed it all in SkinSettings.xml even though I &quot;demoted&quot; it to MediaPortal.xml - and I really only did that because the Configuration tool cannot be made to easily deal with multiple skins (let alone the whole client/server issue).&nbsp;I'm going to simplify the existing implementation by removing the skin settings override capability (taking skin setting completely out of the design) and reworking the wiki instructions. I know this doesn't solve some of the recently discussed design issues but we're getting close to 1.3 and I want to make this thing as usable as it can be given where we're at.</blockquote>

[QUOTE="ajp8164, post: 862968, member: 64375"] Not easy, and not do-able in the 1.3 time frame (at least by me ;-) Dealing directly with the database will introduce a lot of risk in terms of time to understand, design, complete. I have no idea what the impact of changing the table schema of the tv database would be, nor do I understand the process for upgrading existing database installations. For 1.3 (at least) we'll need to stick with the current architecture. I can make some slight enhancements (including dumping the idea of skin settings being involved at all - just stick with MediaPortal.xml). I'll also rewrite the wiki to make it simple to understand and use. In principle I could agree that storing genre mapping information in the database makes sense but I'm not on board with putting color information in the database. Color info should live as close to the UI as possible; that's why I initially placed it all in SkinSettings.xml even though I "demoted" it to MediaPortal.xml - and I really only did that because the Configuration tool cannot be made to easily deal with multiple skins (let alone the whole client/server issue). I'm going to simplify the existing implementation by removing the skin settings override capability (taking skin setting completely out of the design) and reworking the wiki instructions. I know this doesn't solve some of the recently discussed design issues but we're getting close to 1.3 and I want to make this thing as usable as it can be given where we're at. [/QUOTE]

Verification