Bill thanks. No conspiracy involved in my last effort, just a few typos and simple errors! On the whole I agree with your changes: where you put in a fuller explanation of "why" I've deleted mine as its now redundant.
In the same way you changed my example where I had Artist=Beethoven to Composer=, I've changed your example of Artist=Haifetz to Performer=. This should make the example clear without getting caught up in a debate about how people choose to use "Artist" when we have this abundance of new tags to play with. Just a couple of things I don't understand: (1) In the web form section you wrote "Bill's Alternative: Just add a new "Browse by Tags" command to the main menu. The first step is for the user to select a tag to browse. This keeps the regular browse commands the same way they are now. I'm a bit leary of adding 6 or more lines to the list of choices in the existing Browse commands. I understand that it might be easier to implement the Multi-level Browse as a change to the behavior of the existing commands. However, I think it makes those commands more cumbersome to use." I don't understand the relevance of this to the web form. Did you mean this to go at the beginning of the discussion on the Remote UI behaviour? (2) Your note "Bill's Note: this isn't consistent with your specification about removing a menu item for browsing a tag that has already been browsed." ... I changed the spec to work the way I think you wanted it, there shouldn't be any more references to removing a menu item, unless I missed one (apart from where I said you can't browse a tag twice if its only legal to have one of them, eg Artist) (3) in the Web interface bit, you wrote "Bill's Note: I don't think this is a useful alternative. If you want to define a multi-level search, fine. It isn't a replacement for a browse.". Actually, I think it is - if you have the ability to see the result of the selection criteria you have entered so far, and if the selection boxes are prepopulated like Genre is, it is exactly equivalent to a browse. I wrote this because it occurred to me that the multi-level search (the extended version of today's Advanced Search) could be combined with the web version of the Multi-Level Browse. However, I'm not that bothered to be honest - I can see that some users will be more comfortable with seeing "browse" and "search" kept separate, if only because it maps better on to the Remote UI functions (which really do have to be different). Other than these, and a few minor tidies I've put in, no real issues. Here's a further amended version. Your turn! Regards Ceejay +-------------------------------------------------------------------+ |Filename: enhancement req mlb v2b.txt | |Download: http://forums.slimdevices.com/attachment.php?attachmentid=542| +-------------------------------------------------------------------+ -- ceejay ------------------------------------------------------------------------ ceejay's Profile: http://forums.slimdevices.com/member.php?userid=148 View this thread: http://forums.slimdevices.com/showthread.php?t=18767 _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
