2005-03-25, 06:09 PM
Time to chime my two cents in here. What it really sounds like you need is something like myHTPC and Meedio have which is a meta data database. It allows you to define views, and pretty much any type of information that you want. You then retrieve the information given a particular view of the data.
I do agree, that a common database is good for future development, but it also means that some of the quick changes to plugins will need to follow a more formal process instead of changing on the fly. It also means managing and maintaining the common database format. If a plugin that uses the common database needs something specific added, then it should be submitted to the group for review, and discussion before it gets implemented.
This would definitely affect Reven the most, since he's doing more frequent updates than the rest of the group. But, it also provides the development community a common place to retrieve some of this extra information that GBPVR doesn't store by default, and would benefit the end user when they switch plugins for whatever reason. They don't have to run an export process, just start up the new plugin and the appropriate information is there.
You also have to agree on what is the mimimum information that has to be stored. Plugins will also have to coded so that they gracefully handle missing data or features that they expect to be there.
Anyways, those are my thoughts. Good idea, and one that I think needs to happen in the long run.
I do agree, that a common database is good for future development, but it also means that some of the quick changes to plugins will need to follow a more formal process instead of changing on the fly. It also means managing and maintaining the common database format. If a plugin that uses the common database needs something specific added, then it should be submitted to the group for review, and discussion before it gets implemented.
This would definitely affect Reven the most, since he's doing more frequent updates than the rest of the group. But, it also provides the development community a common place to retrieve some of this extra information that GBPVR doesn't store by default, and would benefit the end user when they switch plugins for whatever reason. They don't have to run an export process, just start up the new plugin and the appropriate information is there.
You also have to agree on what is the mimimum information that has to be stored. Plugins will also have to coded so that they gracefully handle missing data or features that they expect to be there.
Anyways, those are my thoughts. Good idea, and one that I think needs to happen in the long run.