I'm fairly new to JRiver and I'm finding the customisation of views a little confusing. As far as I can see there are 3 different view "libraries", each maintained independently. Library views (i.e. the main MC front-end), Web views, and DLNA views. I mainly use an external controller/browser via DLNA but also like to browse via MC itself for maintaining the library and tagging etc, therefore I like to have my library views the same as my DLNA views so that my collection is browsed in the same way, but have to set them up and maintain them independently.
Is there merit in having one central Views Library, and then in each of the servers you simply select which views from the Library you want to use for that server?
To maintain backwards-compatibility, the upgrade process could automatically create central views from views that already exist in the separate servers, prefixing them with a name such as "[Library Server] Albums by Artist" or "[DLNA Server] Genres" and pre-select them in each server?
From the software developers' point of view, it also means that enhancements to the views only need to be made in one place?