Quote:
Originally Posted by pilotbob
The main reason would be to see if I have more SF than Mysteries or that I have alot more of Terry Brooks than Dan Brown.
Tag clouds do the same thing, they are just more visible and you can see realtive differences easily. For example, go look at my LibraryThing author cloud at http://www.librarything.com/authorcl...?view=PilotBob (I think it's public) and you can quickly see that I have read alot of Diane Cary and Terry Brooks (about the same) and I've read a decent amount of Tom Clancy and Michael Crichton (the same as each other) but less than the first two. Of course this is all relative to my current library. The biger it is, the more popular.
As I said, sort by count and cloud are not as much wanted, but if you are writing the queries to figure out the count it is just a different way of displaying them based on that data.
What I think is more important is that ALL the tags are a single list and that the I have an easy way to focus in on the tags for example, if I click on "toread" I want to then see that within my "toread" items I also have items taged as "mystery" and "romance". And if I add "mystery" to my selected tags I can easily see that "Christie" and "Clark" are tags for the more filtered items.
BOb |
Two ideas come to mind:
1) Adjusting the font size in the view based on count.
2) When a tag is selected, create a subtree of tags that the books matching it also have.
I'm not sure why you want a flat list of tags. The reason for the tree structure is to allow you to more quickly browse the list of tags.