|
|
Site upgrade complete; new features active
I did mention in my original post that my account default is set to Nested already. But I usually only want to bother logging in if I have a comment to make.
Site upgrade complete; new features active
I've got a better solution that I'd actually prefer AND I think it would reduce server load in all cases. Let me start with an analogy. You know how in the Finder, if you option-click a triangle in list-view, it will display the contents of every nested folder it contains? You should implement something like that or a simple "view-all" link. That way, everyone sees it in threaded view and anyone can see the nested view with a single click. Provide that link on the comment page itself which displays threaded by default or perhaps after digging into one level of comments. However, instead of making the subject of each comment be the title of the post by default, make it be, e.g. the first 50 characters of the actual comment. Then you could provide the view-all link next to each subject (or something like that). Then people would be less likely to click view all if their interest isn't piqued by the first 50 characters.
Site upgrade complete; new features active
I was going to suggest that, but I figured it would add too much work on top of everything else going on with the site right now. But anyway, I agree this would be awesome! I'd prefer it to be able to see the hints with a nested view of hints, but be able to hide the comment threads that go on forever on a topic I don't care about.
Disclosure triangles on web pages
I have seen web pages that do this. The underlying mechanism works by loading all the text, with some of it hidden, and JavaScript to let you show the hidden stuff. So I agree it could be useful (although I’m quite used to the nested view myself), but it wouldn't reduce server load.
Disclosure triangles on web pages
You're right, it wouldn't reduce server load if you load all the text, but I've implemented a rudimentary version of this before where it does not load all the text, so it is possible, however it reloads the page. The question is, would that increase in load be greater than or less than the extra load created by the unread text loaded for users who default to nested view and the extra load from threaded users who do tons of page loads to view comments? Personally, I think load would be overall reduced, because: |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.11 seconds |
|