jmarshall Wrote:Regarding reorganisation, I see a couple of things:
1. If we assume that a source contains only one type of videos (eg only movies) then for sure it could be listed in the main "Movies" overview node. We could for instance have sources://movies/ to complement sources://video/, the former showing only those sources which have content set to "movies". The problem, ofcourse is that XBMC allows you to set content type on any folder, so it could well be a subfolder. Perhaps this could be discouraged (it certainly simplifies things), or we could have a content type "mixed" or some such.
Personally I always like making stuff stricter with less special cases.
I think if we first take a step back and look at why the subfolder thing may have been needed and used we can see if its possible to omit it. What I believe is that a user in some shape or form uses the files view to navigate the media, if so it may make sense to set smb://foo/ as movies but smb://foo/bar as tv shows, because they have this weird structure on their NAS and do not wish to have both as seperate sources in their organization. Another use case may be that they add smb://foo but set content on smb://foo/movies and smb://foo/tvshows as they only want to show foo (the computer) in the file list, as it gives easier navigation.
Both of these cases are IMO just for organization and if we can have a better scheme for organization we can remove that sub folder stuff. IMO the sources node should be just a place where you specify sources for your library, with that definition the organization of this node does not matter as it shouldn't really be used to navigate the content. In that regard adding both of the sources in each of the cases above is an ok requirement IMO. As for the first case it seems to me that we could easily have the a root folders content setting take precedence over what it may be in recursive. Hope I am making some sense
jmarshall Wrote:2. The reorganisation will allow basically any structure - so smartplaylists and nodes could be placed relatively flexibly - the main "Overview" nodes would simply be folders that contain other nodes, so certainly the user could manually add some sources in there, but I think I'd prefer it to be automated if at all possible. eg I'm not sure if a listing of:
...
The former is easy to specify as the "Files" node is auto-filled with all sources of type "Movies". The latter must either be specified manually, or we must have some sort of "combined listing" where we list both the "Files" node and the "overview" node (similar to a multipath.) Personally I prefer the first, with the latter allowed via manual config.
Cheers,
Jonathan
I'm not really sure (could be because I haven't had my coffee yet) if you are talking about the root or what should be listed in the movies section? but I'd like the root of the library to be something like:
Movies (autogen)
TVShows (autogen)
Sources (here we add whatever we want in the other nodes, it is unorganized in the aspect of navigating media and just a way of getting data into the library).
VirtualNode1
VirtualNode2
...
VirtualNodeN
(Sorted in a natural way) All VirtualNodeX are stuff the user can specify via something similair to smart playlists.