Thanks, Steven! Still have some questions though:
the API supports accessing the library and fields
- Can the database engine be accessed via the API? If not, is there any dll that can be double used from MB?
public Library_GetFilePropertyDelegate Library_GetFileProperty;
public Library_GetFileTagDelegate Library_GetFileTag;
public Library_GetLyricsDelegate Library_GetLyrics;
public Library_GetArtworkDelegate Library_GetArtwork;
public Library_QueryFilesDelegate Library_QueryFiles;
These are only for tracks from MB's own database and table, right? And only possible with their own fields, or? (And no write access, but I guess the other functions can do that.)
If so, I am more interested in general SQL Lite access functions since I will have my own DB and table (after your suggestion). Since you already use SQL Lite, I was thinking to double use the function-library MB already uses itself, via calling the same dll (or via the API). To evade having to add another dll myself, just for the same DB access (not same DB, just same engine=SQL Lite)
i would need to add support and can do. For the panels, i will need a good idea of how you think it should be implemented
- Would it be possible to use the current Music Library (including filtering) and default (what's it called?) organizing panels?
In the music library I would just have to be able to feed my table into it (with similar, but also extra track fields e.g. "ghost file yes/no") or have a distinct menu item under it in the library dropdown, or what were you thinking? Maybe there are other options.
-About the panels: First, that's only needed if the above is not possible. I just need a tab to display my ghost music tracks the exact same way as MB displays any track list today. (Except for some extra fields maybe (like "ghost file" yes/no.)
So, just a list of tracks with fields (and if possible all the other things that come with it, such as the different views, the different filters, the mouse context menus, ordering, etc..). I could actually also use this latter solution for my Radio Dig plugin (which has a limited amount of fields.)
Concerning good ideas, I am afraid I am not much of use, especially since I don't (have time nor will to
) know your code, but maybe the function that you use to display a track list panel can have an extra parameter and that parameter tells it what source it should take (MB itself or a plugin-propagated source; this source being a handle, pointer, class-object whatever you use today, or maybe even a database connection).
Thanks in advance, whatever and however you would get this done.