Implement a user-space virtual file system reflecting the container structure. I.e., there should be a directory for each container, subdirectories for subcontainers, and files for actual music files. Tags of containers could e.g. be provided as text-files inside the container folder.
The configuration would be the same as for a browser (in fact, the filesystem hierarchy should look like the contents of a browser). Especially, there should be an option for filtering, defining "valuenode" layers.
The benefits:
no need to write an extra "wtf" plugin, since one could just copy the folders in the VFS,
other programs could use the container structure without knowing anything about OMG's internals,
ideal to prepare containers to copy on portable players / share with friends
Implement a user-space virtual file system reflecting the container structure. I.e., there should be a directory for each container, subdirectories for subcontainers, and files for actual music files. Tags of containers could e.g. be provided as text-files inside the container folder.
The configuration would be the same as for a browser (in fact, the filesystem hierarchy should look like the contents of a browser). Especially, there should be an option for filtering, defining "valuenode" layers.
The benefits: