Normal
Sorry for dragging up this thread, but I've recently discovered this plugin and combined with FanArt and the XFace skin and I absolutely love it.I need to look more at the code this evening, but I may (note, I'm not certain) volunteer to abstract the data access into more of a provider type implementation which would allow us to have a .dll that implements SQLite and another that implements MSSQL (and if someone wanted, they could do a MYSQL).In my mind, I'm thinking a set of base classes that define the object and provide methods that each implementation would override to actually load the data into and out of the data store. Via a config file entry, would you be able to specify which .dll you want.Maybe we can exchange some email and I could provide a skeleton of what I'm thinking and if you approve, I'll go ahead and do it. Not to sound like an *ss, but I don't really want to spend a lot of time writing something that won't be added. (I'd prefer to use the same code everyone else is using, that way when a bug is fixed, I don't have to try and merge the fix in the "special" version I'm running.)Thoughts?
Sorry for dragging up this thread, but I've recently discovered this plugin and combined with FanArt and the XFace skin and I absolutely love it.
I need to look more at the code this evening, but I may (note, I'm not certain) volunteer to abstract the data access into more of a provider type implementation which would allow us to have a .dll that implements SQLite and another that implements MSSQL (and if someone wanted, they could do a MYSQL).
In my mind, I'm thinking a set of base classes that define the object and provide methods that each implementation would override to actually load the data into and out of the data store. Via a config file entry, would you be able to specify which .dll you want.
Maybe we can exchange some email and I could provide a skeleton of what I'm thinking and if you approve, I'll go ahead and do it. Not to sound like an *ss, but I don't really want to spend a lot of time writing something that won't be added. (I'd prefer to use the same code everyone else is using, that way when a bug is fixed, I don't have to try and merge the fix in the "special" version I'm running.)
Thoughts?