Reply to thread

Message

<blockquote data-quote="ajp8164" data-source="post: 837053" data-attributes="member: 64375">Re: Skin engine enhancements (themes, guide colors, skin functions, weather settings.Hi all,Love the passionate debate ;-)&nbsp; Great software built by great - and passionate people!I am thankful to you all for help in making these new features better - I really do enjoy working with the MediaPortal team... if only my day job was as fun and interesting <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" />Indeed genres can be read from the TVDB and in the current/latest revision *they are*.&nbsp; The &quot;unmapped&quot; genres list (see the configuration tool) lists the genres in the TVDB that are not mapped to any &quot;MP&quot; genre.&nbsp; Recall that the &quot;MP&quot; genres are simply genre names that *I made up* (a sane person only needs approx. 5-7 genres; anything more makes the guide look like a rainbow = unreadable).After reading through all the ideas and giving it some think time I have to agree that the best long term solution will be to have each MP genre associated with a list of search terms which can be used to determine which TVDB genres best match.&nbsp; For instance; if the MP genre is &quot;Sports&quot; then the list of search terms might include &quot;sport, tennis, baseball, football, soccer, basketball, racing&quot; etc.&nbsp; The list of search terms will be matched with the TVDB genre names using a logical OR on a case-less sub-string basis.&nbsp; The list of search terms will be stored in MediaPortal.xml and editable via the configuration tool.&nbsp; There will have to be a list of search terms for each language and the language used would have to be whatever language MediaPortal is currently set to (in MP settings).&nbsp; For best results we'll need to seed the list of search terms (for each language) best we can.If we can agree on this kind of solution I can whip up the implementation fairly quickly as it's just extending the current implementation.<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" /> for everyone's help and support!</blockquote>

[QUOTE="ajp8164, post: 837053, member: 64375"] [b]Re: Skin engine enhancements (themes, guide colors, skin functions, weather settings.[/b] Hi all, Love the passionate debate ;-) Great software built by great - and passionate people! I am thankful to you all for help in making these new features better - I really do enjoy working with the MediaPortal team... if only my day job was as fun and interesting :D Indeed genres can be read from the TVDB and in the current/latest revision *they are*. The "unmapped" genres list (see the configuration tool) lists the genres in the TVDB that are not mapped to any "MP" genre. Recall that the "MP" genres are simply genre names that *I made up* (a sane person only needs approx. 5-7 genres; anything more makes the guide look like a rainbow = unreadable). After reading through all the ideas and giving it some think time I have to agree that the best long term solution will be to have each MP genre associated with a list of search terms which can be used to determine which TVDB genres best match. For instance; if the MP genre is "Sports" then the list of search terms might include "sport, tennis, baseball, football, soccer, basketball, racing" etc. The list of search terms will be matched with the TVDB genre names using a logical OR on a case-less sub-string basis. The list of search terms will be stored in MediaPortal.xml and editable via the configuration tool. There will have to be a list of search terms for each language and the language used would have to be whatever language MediaPortal is currently set to (in MP settings). For best results we'll need to seed the list of search terms (for each language) best we can. If we can agree on this kind of solution I can whip up the implementation fairly quickly as it's just extending the current implementation. :thx: for everyone's help and support! [/QUOTE]

Verification