Reply to thread

Message

<blockquote data-quote="mbuzina" data-source="post: 66005" data-attributes="member: 12382">Hi All,I am just wondering that MP has code for Browsing Videos, Music, Pictures etc. which are all seperatley coded, stored in a seperate database etc. I know this may sound a bit like (unfortunatley dead) WinFS idea, but why not set up code that browses &quot;media&quot; by it's properties (e.g. Artist, Album, Actor, Genre, Date, Folder, Source / Program, Favorites, Playlists etc.)?This would implicate a complete new design of database (away from the multiple DB version to a single DB storing all &quot;Items&quot;)That would save a hell of a lot of code, allows for more integrated searching for &quot;things&quot; (e.g. Music Videos could be part of My Music instead of Video).The database I am picturing at the moment would have a starting table for everything you could play (item like, Song, TV Show, Movie etc.) and another table for everything &quot;containing&quot; items (like Gernres, Folders, etc.). Some things would probably end up in both (TV Station contains TV Shows, but can also be an item for play this channel).Sorry for the long post, but I just wanted to ask the dev community if it would be worthwhile putting some effort into DB design, mapping classes etc for such a setup?Thnx!</blockquote>

[QUOTE="mbuzina, post: 66005, member: 12382"] Hi All, I am just wondering that MP has code for Browsing Videos, Music, Pictures etc. which are all seperatley coded, stored in a seperate database etc. I know this may sound a bit like (unfortunatley dead) WinFS idea, but why not set up code that browses "media" by it's properties (e.g. Artist, Album, Actor, Genre, Date, Folder, Source / Program, Favorites, Playlists etc.)? This would implicate a complete new design of database (away from the multiple DB version to a single DB storing all "Items") That would save a hell of a lot of code, allows for more integrated searching for "things" (e.g. Music Videos could be part of My Music instead of Video). The database I am picturing at the moment would have a starting table for everything you could play (item like, Song, TV Show, Movie etc.) and another table for everything "containing" items (like Gernres, Folders, etc.). Some things would probably end up in both (TV Station contains TV Shows, but can also be an item for play this channel). Sorry for the long post, but I just wanted to ask the dev community if it would be worthwhile putting some effort into DB design, mapping classes etc for such a setup? Thnx! [/QUOTE]

Verification