This is starting to get confusing. Let me try to sum up some of the options we have:
1. Put the pool bar at the top, exactly like Danbooru 1.
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).
Really go with #1 and #7.
Option 3 WOULD work IF the sidebar was significantly wider But that starts to lead to problems of the browsing area being squished by a combination of that and the adspace so you get thinner columns and thus going from a preferred 4x4 to something like 3x6 (with row 6 being 1 image) or 2x8 which no one wants.
Number 6 just clutters up the site with more pointless tags. And really it defeats the point of having pools as it starts a shift towards "ALL POOLS ARE TAGS" which is a very very stupid idea
Number 6 just clutters up the site with more pointless tags. And really it defeats the point of having pools as it starts a shift towards "ALL POOLS ARE TAGS" which is a very very stupid idea
The idea behind #6 is that pools would be limited to comics and other series. So it's actually "all collection pools are tags".
That said, #7 is starting to look better if only because it requires less work and less change.
The idea behind #6 is that pools would be limited to comics and other series. So it's actually "all collection pools are tags".
That said, #7 is starting to look better if only because it requires less work and less change.
It's much easier to do and manage in both adding to and searching as you'd have them all listed "Collection - X" instead of them scatter shot all over the pools. Just hope we don't get a series called "Collection" in the future that gets popular enough to become a pool...
The only way we'd practically do #6 is to use a massive project to do so or a bot/script to do but considering just how many images would be effected Danbooru could be down for days if not a week considering the sheer volume of images to be checked and changed.
Also remember some of the Collection Pool Names for the collections are rather long So we run the same problem that putting the full pool names in the top left corner. That you're gonna get 3+ line long tags on the side.
It's much easier to do and manage in both adding to and searching as you'd have them all listed "Collection - X" instead of them scatter shot all over the pools. Just hope we don't get a series called "Collection" in the future that gets popular enough to become a pool...
Adding "Collection" to the name wouldn't be a good idea. Keeping the names short would allow them to fit in the sidebar. It also looks better shorter.
Zelinkokitsune said:
Also remember some of the Collection Pool Names for the collections are rather long So we run the same problem that putting the full pool names in the top left corner. That you're gonna get 3+ line long tags on the side.
I think almost all can fit on 1-2 lines. The ones that end up taking 3+ lines are comic names.
While I prefer float+alpha, the solution proposed by Dbx isn't too bad either.
In the endgame, there really should be some segregation between sequences and flat collections, though. They are simply not the same thing.
Zelinkokitsune said:
...considering just how many images would be effected Danbooru could be down for days if not a week considering the sheer volume of images to be checked and changed.
On what authority are you even making this assertion? Does the site go down when jxh makes a new alias or changes an implication (like all the legwear stuff)?
Kindly stop poisoning the well with ill-informed dreck just because you hate all forms of change.
But considering how many times we've had Danbooru down due to various bugs this will probably require downtime once more. And then downtime to fix another problem.
And really the changes being presented and made are usually just "Feel Good" changes than actually fixing real problems.
But considering how many times we've had Danbooru down due to various bugs this will probably require downtime once more. And then downtime to fix another problem.
Changing pools to tags would require no downtime at all, from my understanding.
The short downtimes we've been having is while Albert puts out updates.
Changing pools to tags would require no downtime at all, from my understanding.
The short downtimes we've been having is while Albert puts out updates.
Figured you need some scripting to make sure everyone got it.
I'm Still very much against making these into tags and rather having the 'collection' pools being made into ones called "Collection - NAME" although I'm not sure WHY we need this change as searching by comic is already marked by Fandom...
Figured you need some scripting to make sure everyone got it.
I'm Still very much against making these into tags and rather having the 'collection' pools being made into ones called "Collection - NAME" although I'm not sure WHY we need this change as searching by comic is already marked by Fandom...
Because the "Copyright - " prefix on pools is neither limited to series pools nor is it something that the site can consistently use to segregate series from collections. Giving pools a series/collection type would allow this.
Putting the "Collection - " prefix on collection pool names is still a bad idea. Putting collections in the sidebar and series in the top bar is enough to tell them apart, and it takes up less room than that prefix.
... All users on Danbooru are required to protect interests in the storyline of any piece of work ... As such, the destructive power of spoilers are taken very seriously on Danbooru ...
Many collection pools spoil a comic before you've read it. Hiding the pools at the bottom often spoils the story if you read the comic without realizing it's part of a story it's not the start of.
So "the changes being presented and made are "Feel Good" changes, not solutions to real problems" is inaccurate at best and a lie either to dismiss others or to troll at worst. (I feel like danbooru is turning me into a lawyer with all this quoting policy and documentation to back and refute arguments.)
These problems weren't addressed until now because we've been waiting for danbooru 2 to clear up lots of issues all at once. The original idea was that "testbooru":testbooru.danbooru.us would be used to iron out the bugs before rolling it out, but as ever, forcing yourself to use the code you're writing to in the real world is the only way to do it.
So we were always going to have to do this and we're going to keep having to do this for at least a few more weeks to solve the problems (there's more than the spoilers issue, thought that would be enough). That's just how software development goes. I understand you're distressed at the 90's-tastic new index page design and all the downtime interrupting your flow, but that's nothing new.
So let's get rid of pools all together. Problem solved! No Spoilers as there are no pools!
Also the collection pools up top can help me avoid art as the ultra long form comics which often get "Soul Crushingly Depressing" or are part of 'Tribute' pools you can't tell from thumbnail so If I want to avoid them bam I can easily avoid it with a top mounted tag. And there have been "Soul Crushingly Depressing" tagged images which are not that at all.
Maybe if we added blacklists for pools it might help there.
Also quoting xkcd? Seriously?
I'm still trying to find all the pressing problems which the interface changes fixed. I've yet to find any. I mean other than making the color coded tagging system kind of pointless.
You selectively ignore half of what others say and dismiss and mock the other half. You are self-righteous in your demands for others to explain things to you and self-entitled to the right to have things your way. I've attempted to satisfy your complaints, and I could answer your latest, but I shan’t bother with you any more. Stop posting before you piss the rest of the forum off.
However, despite myself, I think pool blacklists sounds like a surprisingly neat solution to the problem.
Edit: Though it could be annoying when trying to compromise about what goes on the blacklist. Plus the problem isn't hiding collections from the index (though that's another complaint of mine from a while ago) but to stop it appearing at the top, which there are neater solutions too.
Edit: And to chime in, I think Dbx's solution falls short of stopping a collection spoiling the comic before you read it.
You selectively ignore half of what others say and dismiss and mock the other half. You are self-righteous in your demands for others to explain things to you and self-entitled to the right to have things your way. I've attempted to satisfy your complaints, and I could answer your latest, but I shan’t bother with you any more. Stop posting before you piss the rest of the forum off.
However, despite myself, I think pool blacklists sounds like a surprisingly neat solution to the problem.
Edit: Though it could be annoying when trying to compromise about what goes on the blacklist. Plus the problem isn't hiding collections from the index (though that's another complaint of mine from a while ago) but to stop it appearing at the top, which there are neater solutions too.
Edit: And to chime in, I think Dbx's solution falls short of stopping a collection spoiling the comic before you read it.
If Pool starts with "Collection" Set to bottom. Else Pool Name to top. Or something like that.
I mean its should be possible.
And short of removing all pools to avoid spoiling anything this is probably the best solution
If Pool starts with "Collection" Set to bottom. Else Pool Name to top. Or something like that.
I mean its should be possible.
And short of removing all pools to avoid spoiling anything this is probably the best solution
If comic pools are only on the top, you still need to scroll back up after reading each page. That was my main problem with the old system.
An option to blacklist all collection pools sounds nice, but I think we should decide where the pools will go first.
The more I think about it, the more I think this is the best solution:
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).
This solves all of these issues:
Multiple collection pools at the top shift the image down.
Collection pools at the top or sidebar spoil the content of the image.
If series pools are not listed at the top, you could view the image without knowing that it's part of a comic and spoil yourself.
Pools in the sidebar can look squished.
You don't need to scroll back to the top to advance to the next image in the pool you are currently browsing.
I believe those are all the major ones brought up so far.
I don't like the cumbersome UI of having grayboxes at multiple location in the same image. Pool navigation is not a concern anymore since Albert had introduced key navigation.
I'm in doubt regarding how users would accept having two large gray boxes instead of one. I'll just try it out; screenshots would probably do this work better than words.
It wouldn't matter much for bigger images, though. And for posts like post #630258 all pools but active will stay at bottom, which I see as an improvement.
I'm in doubt regarding how users would accept having two large gray boxes instead of one.
That would be less of a problem if the boxes weren't quite so large. Trying changing the padding of #pool-nav from 1em to 0.3em or 0.4em. It looks much better, in my opinion.
And there could be an option to close one of the boxes for those who dislike it, like there is for the sequential search navigator.
Sal.N said:
Pool navigation is not a concern anymore since Albert had introduced key navigation.
Ugh. Tried to stuff all collections from post #630258 into sidebar as an experiment. Even with small nav buttons, it still looks awful as half of names still go multiline, so I don't even want to consider it.
Ugh. Tried to stuff all collections from post #630258 into sidebar as an experiment. Even with small nav buttons, it still looks awful as half of names still go multiline, so I don't even want to consider it.
The suggestion in the old thread was to shorten longer names with "..." at the end. Do we even need the small nav buttons? As per Dbx's suggestion, we could only show navigation when browsing a collection. This would only apply to collections, though. If you open a page of a comic, you should always want to have navigation enabled, as a single page of a comic is not useful by itself.
And I don't think that post should be in so many pools to begin with. It apppears to be an exception anyway. For some reason, my browser freezes for a few seconds every time I try to load that page.
