|
| Author | Thread |
|
|
01/15/2006 12:44:54 PM · #1 |
[quote]
Threads will be shown in descending order for the remainder of this session. To permenantly display posts in this order, adjust your preferences.
[/quote]
I do not understand this design decision, unless it was simply made "because it is easier". It definitely seems less intuitive to me.
I set the way I want threads to appear by default in the preferences. When I'm checking on a longer thread that I've read before, I might want to look at the thread in reverse to see recent additions, so I click ``reverse''. I don't want this to change the way any other thread looks thoug, I want those to use what I have currently set as the default. I want only the threads I select to be exceptions. I'd be satisfied if it even only showed this thread, this one time, in reverse (just passing an extra argument along that overrides the default) and therefore it wouldn't affect anything else [hopefully].
Does this make sense to anyone else? |
|
|
|
01/15/2006 12:47:58 PM · #2 |
yes, I have often thought that the "reverse" should be a "thread option" rather than a global way of viewing all your threads. We all know that there are often VERY long threads that we want to be involved in that using "reverse" helps greatly, but the majority of threads are more comfortably viewed the opposite way.
drake |
|
|
|
01/15/2006 01:23:21 PM · #3 |
| You can click on the "Reverse" link again to restore the original setting. Rather than implement complex coding which would have to track your option thread-by-thread (extra database load slows site performance), the admins have provided you a way to toggle this preference from any thread, rather than having to find your way to your Preferences page. |
|
|
|
01/15/2006 01:38:13 PM · #4 |
Originally posted by GeneralE:
You can click on the "Reverse" link again to restore the original setting. Rather than implement complex coding which would have to track your option thread-by-thread (extra database load slows site performance), the admins have provided you a way to toggle this preference from any thread, rather than having to find your way to your Preferences page. |
I don't think it would need to be complex, and I offered a simple method that would fit (at least my) preferences.
The annoyance is that I set threads to auto-refresh. In general, most tabs in my browser are auto-refreshing at some given interval. This causes threads to have an indeterminite reversal mode, and is an annoyance, albeit just an annoyance. This is why the 'double-click' method does not exactly work for me, but I'm obviously living with it. |
|
|
|
01/15/2006 02:09:20 PM · #5 |
Originally posted by m:
Originally posted by GeneralE:
You can click on the "Reverse" link again to restore the original setting. Rather than implement complex coding which would have to track your option thread-by-thread (extra database load slows site performance), the admins have provided you a way to toggle this preference from any thread, rather than having to find your way to your Preferences page. |
I don't think it would need to be complex, and I offered a simple method that would fit (at least my) preferences.
The annoyance is that I set threads to auto-refresh. In general, most tabs in my browser are auto-refreshing at some given interval. This causes threads to have an indeterminite reversal mode, and is an annoyance, albeit just an annoyance. This is why the 'double-click' method does not exactly work for me, but I'm obviously living with it. |
What you are describing, while simple to describe in words, is somehat complex to code. the confusion comes in making the setting stick as you flip pages, reply to posts, etc. It would also have to stick if you were viewing multiple threads (or the same thread) in multiple windows at the same time. I can't think of a way to make what you're describing work reliably, without undesired becavior, without adding database overhead.
~Terry
|
|
|
|
01/15/2006 06:34:16 PM · #6 |
Originally posted by ClubJuggle:
What you are describing, while simple to describe in words, is somehat complex to code. the confusion comes in making the setting stick as you flip pages, reply to posts, etc. It would also have to stick if you were viewing multiple threads (or the same thread) in multiple windows at the same time. I can't think of a way to make what you're describing work reliably, without undesired becavior, without adding database overhead. |
Obviously I don't know what the current codebase is, as I do not think it's available publically, but it seems like instead of adding order=DESC you can change that to xorder=DESC (so as not to touch current code) and then check $_GET['xorder'] on the page display after checking whatever is currently checked, and then in whatever code constructs the URLs for other pages and prev/next (which already checks other variables) it would just append xorder if it isset. If you opened a new window/tab from these links, the value would be part of the request and it'd be all fine and dandy. The point of my request was for it *not* to affect multiple threads.
If it's more complicated than this, however, I'll just take your word for it unless the code is available somewhere. |
|
|
|
Current Server Time: 08/30/2025 05:18:51 PM  |
Home -
Challenges -
Community -
League -
Photos -
Cameras -
Lenses -
Learn -
Help -
Terms of Use -
Privacy -
Top ^
DPChallenge, and website content and design, Copyright © 2001-2025 Challenging Technologies, LLC.
All digital photo copyrights belong to the photographers and may not be used without permission.
Current Server Time: 08/30/2025 05:18:51 PM EDT.
|
