jednie wrote:I will try to include a first version of a mobile template in the next release. It will likely be a scaled down version that includes all data in a single column so there won't be any horizontal scrolling needed. The way it will likely work is that you will pick the template that you want to use on the login page and it will save a cookie to your browser so that the next time you login it will remember your previous setting.
That'd be slick. I like "down & dirty". Something simple & straight-forward.
jednie wrote:I hadn't thought of this before. I can see this tab containing a listing of all that genre's that meet the search criteria with columns called Artist, Songs, Albums that include a count of each item that includes this genre. Is this what you have in mind?
It wasn't what I was picturing, but I think it gets me what I "meant" a lot better than what I was thinking!
If I understand you, that keeps a consistent interface also, which I like!
jednie wrote:I am not sure that I understand what you have in mind here. Are you thinking that a tab will be used to define the category and a cloud will be used to define a sub-category?
With a big database, multiple Genre's become visually messy to me. So I switched to a single Genre entry. Then, like allmusic.com does, I put sub-genre's (styles) into a different field that supported multiple entries.
An example of my current entries are:
Genre: Pop/Rock
Conductor: Hard Rock; Heavy Metal; Contemporary Pop/Rock; Hair Metal; Arena Rock; Country-Rock
This organization gives me a cleaner genre list to look at (instead of 100's of Genre's). I can then search for Artists that primary did Pop/Rock, but dabbled in Country-Rock. When I had everything stuffed in Genre, it worked fine for searches, but browsing just looked ugly with hundreds of Genre's :\
I'm thinking this would require a couple of configuration entries. Assuming Genre is changed as you described above, there would have to be the ability optionally "turn on" the use of the other multi-entry fields. So lets say that I'm going to turn on the "Conductor" tab. It could act exactly like the Genre tab above - UNLESS, I (through a second configuration entry) state that Conductor is sub to Genre. In that case, when I select the Genre Tab, I then get the "styles (Conductor Entries) with totals, and navigate downward from there. Of course any of the "little used" multi-entry fields we optionally turn on, needs to become searchable just like the other fields are. I think this would ad a lot of versatility, allowing some tayloring to how each of us deal with the extra meta-data we're all trying to squeeze in.
Another possibility is if someone wants R&B from the 60s. I would additionally designate the "Composer" field as a sub to genre. It would add yet another search field, and on the cloud side, it would add a "Composer" data to go with the "Conductor" tab. (I identify the active decades of the groups in the Composer field). I'm still considering how this would be presented on the screen.....
LOL and if you wanna tweak the mediamonkey developers, add the ability of us to rename these odd-ball fields we're finding a use for: "Composer <-> Style" and "Conductor <-> Active Years". <g> I just picture a lot of versatility for those of us that taylor our music library to this level.... (yeah... i have no life)
jednie wrote:Coming soon: SSL, RSS feeds, more context menu options and an improved album view.
Sounds great!