Type-kun said:
draggable semi-transparent [tag editing] box
This is a great idea. I just tested this with a script, and it is very convenient so far.
Posted under General
Type-kun said:
I think making collection pools into tags will arise additional discontent from users, much worse than we have now. Also, how would we deal with pools like pool #1193 then? Is it a collection or a story, considering Zun at the end?
Though I agree that dividing pools into 'collections' and 'stories' is a huge step to finding a compromise between what we are discussing, we risk to clutter the interface too much by doing that, so it needs further planning. Also that's serious additional work for mods, considering there is 6000+ pools by now.
pool #1193 is a collection. ZUN image is not the actual ending image. It's just a playful thing Danbooru users do, which means it's not a priority to be considered. New posts in this theme are still being actively drawn on pixiv.
Gardening pools is not much more heavier than gardening tags. With tag script, it's possible to go through those 6000+ and change the collections into tags in a couple of weeks. Only if Albert agree to make the fourth tag type of course.
Type-kun said:
As for spoilers... pools positioned above image raised different problem, 'warning' you about the contents of every image. Seriously, I'd rather discover that image is 'heart-warming' or 'soul-crushingly depressing' myself, while reading it, not before reading it. Especially so for long, story-heavy strips.
And I doubt arguing like that will get us anywhere. Opinions are just split between 'above picture' and 'below picture' - it's a matter of user preference and hence begs for option in user profile. As well as some other things. Now, while danbooru is still undergoing renovations and is unstable, may be the best time to suggest some UI tweaks and configurable options. While RoR and proper MVC make danbooru modular by design, user options are typically pain in the ass for developer and have less chances to be implemented when things get stable.
I'd rather be warned before hand for certain pools than NOT warned. Admittedly I wanted to be able to blacklist entire pools but it doesn't seem possible to do so with the old software.
Type-kun said:
I think making collection pools into tags will arise additional discontent from users, much worse than we have now. Also, how would we deal with pools like pool #1193 then? Is it a collection or a story, considering Zun at the end?
Though I agree that dividing pools into 'collections' and 'stories' is a huge step to finding a compromise between what we are discussing, we risk to clutter the interface too much by doing that, so it needs further planning. Also that's serious additional work for mods, considering there is 6000+ pools by now.
Why the hell would we want to make Collection Pools into Tags?! 90% of the time I wouldn't be searching for a tag for collections. Hell I wouldn't even know they existed if they weren't listed as pools or when they updated it. Yet again WHY are we even considering changing this.
It seems to be another Change for the Sake of Change thing. Which we're finding out is more and more counterproductive and bug creating than NOT changing it.
Also remember 99.999% of the userbase will NOT Install scripts to fix stupid changes.
Edit: Also that change will probably break the server... Again.
Updated
Zelinkokitsune said:
Why the hell would we want to make Collection Pools into Tags?!
Pools are ordered. They should be for ordered content. Collections are not ordered.
It also solves the problem of posts being in 5+ pools. The bar takes up too much space when that happens.
I'm actually curious about why these collections were made into pools in the first place. Was it because tags are supposed to be objective, which collections are not? That doesn't seem like a good reason to use pools instead of tags.
Zelinkokitsune said:
Hell I wouldn't even know they existed if they weren't listed as pools or when they updated it.
So you think it wouldn't be possible to find them if they were tags?
Couldn't you just look in the sidebar of posts you see? That's how you usually find tags already.
Zelinkokitsune said:
It seems to be another Change for the Sake of Change thing. Which we're finding out is more and more counterproductive and bug creating than NOT changing it.
Reasons that it would be a beneficial change have already been mentioned in this thread. It's not just for the sake of change at all.
Zelinkokitsune said:
Also remember 99.999% of the userbase will NOT Install scripts to fix stupid changes.
What reason would you have for wanting to fix it in the first place? To me, it looks like you just don't like change, and have been complaining about everything that was changed.
Also, this isn't the kind of change that can be fixed by scripts.
Serlo said:
There's a solution to all 3 of these complaints. Put the bar at the top and bottom and adding mouse controls satisfies the browsing. Adding the option to hide the bar and only displaying one bar at a time solves the clutter.
...Or make the pool navigation float, instead of repeating it multiple times. I've suggested this multiple times and all concerned parties have conspicuously neglected to address it. (Not even getting into the other usability concerns I addressed at the same time.)
DschingisKhan said:
...Or make the pool navigation float, instead of repeating it multiple times. I've suggested this multiple times and all concerned parties have conspicuously neglected to address it. (Not even getting into the other usability concerns I addressed at the same time.)
I forgot to comment on it earlier, but I think it's a great idea.
Specifically so I don't have to scroll anywhere to advance in a comic pool; I could keep the mouse in one spot.
You're not getting an answer because you've asked a difficult question. Floating objects in website design is another kettle fish all together. I'm not strictly against the idea, but I am very leery of how it would interact with the rest of danbooru's design, which, as another user pointed out, was one of the cleanest on the internet.
So far, danbooru is completely flat and mostly static. Aside from ads, header notices, "you have mail/upgrade for $20", and those running scripts, danbooru's appearance looks the same everyday for everybody. It's like pages in a newspaper, only with a fancier way of moving between pages.
It's very easy to mess up a website design by allowing different parts of the website to float about. I've seen plenty of ugly sites than have tried to keep static sidebars and it's gone so horribly wrong despite the site following most of the rules. Crucially, floating objects and edge panels tend do poorly on small browser windows.
I think pool navigation is only needed if you're browsing the pool. It can be done similar to the the new search navigation feature: http://i.imgur.com/p8IqB2B.jpg
Dbx said:
I think pool navigation is only needed if you're browsing the pool.
Good idea. The pools converted to subjective tags concept also has some merits but would create a ton of work.
I suggest the following:
Combine pool navigation with tag search navigation, such as
post #1369500
opens up a navigation bar for pool 6473 above and/or below the picture. Only one such navigation bar is needed since usually you only browse one pool/tag search at a time.
List the pools above the tags again, without nav buttons just like tags.
This would streamline the site without taking away functionality. Pools would visually act as tags without being one.
Type-kun said:
Please, no. I'm so glad we moved away from this.
It was horrible when you had it being about 10 lines + because the name of the pool was long or had large words as the font we used for the sidebar isn't all that efficient.
The pool navigation needs to be a full sized bar for it to be NOT horrible and being able to not only list the full name of the pool in one line but actually have it be in a font size one could read!
This is starting to get confusing. Let me try to sum up some of the options we have:
And a few of the arguments against them:
#7 is currently looking like the most realistic, practically speaking.
Toks said:
- 7. Add types to pools, so that they can either be series or collections. In a bar at the top of the image, list the active pool first, followed by series pools it is in. In a bar at the bottom of the image, list the active pool first, followed by all other pools (series and collections).
I assumed that the series will be in a bar above the image and the collections will be listed in the sidebar.
Toks said:
5a. Longer pool names will look squished in the sidebar.
Maybe this will incentivize people to choose shorter pool names (instead of jokes and references) or not create a pool at all if they cannot describe what the pool should contain with only few words.
S1eth said:
I assumed that the series will be in a bar above the image and the collections will be listed in the sidebar.
That's better than what I said. I like it.
S1eth said:
Maybe this will incentivize people to choose shorter pool names (instead of jokes and references) or not create a pool at all if they cannot describe what the pool should contain with only few words.
For option #5, both series and collections would go in the sidebar. For series, choosing shorter names isn't an option, as the artist is almost always the one to choose it.
For collections in the sidebar, I agree that they should have short names.
Edit: But the active pool still needs to be at both the top and bottom of the image. If it's not, you need to scroll back up after reading a comic page.
Toks said:
Edit: But the active pool still needs to be at both the top and bottom of the image. If it's not, you need to scroll back up after reading a comic page.
If I can hide the bottom one just like how I can hide the query navigation thing now, I don't mind. (some others will want to hide the top bar)
BTW, is there a way to unhide/restore that navbar without manually deleting the cookie? (I assume it uses a cookie)
