Scoop -- the swiss army chainsaw of content management
Front Page · Everything · News · Code · Help! · Wishlist · Project · Scoop Sites · Dev Notes · Latest CVS changes · Development Activities
suggestions: time-stamps & auto-refreshing Feature Requests
By alphabit , Section Wishlist []
Posted on Fri Aug 09, 2002 at 12:00:00 PM PST
While participating in the occasional rapid-fire discussion on Kuro5hin.org I noticed it is necessary to "refresh" a story's page fairly often. Unfortunately, since I am often multitasking I sometimes loose track of whether I just refreshed a page or not.

Time-Stamps
I think that listing the date-time of the page's generation right below/above the current system time would be really useful. You could see immediately whether you've recently refreshed the page or not.

Limited Auto-Refreshing
A related idea would be a method of automatic page refreshing. Although allowing unlimited/unconstrained auto-refreshing would lead to wasted server load for many reason, a limited auto-refreshing mechanism could probably be useful. I suggest adding a button to pages that allows the user to request a set number of auto-refreshes (i.e. 5, 10 or 15 refreshes) spaced a set number of minutes apart (i.e. 1, 5, 10, 15, 20, 30 minutes).

Time-Stamps: Implementation Details

Inserting the time stamp of the page's generation should be easy. A resolution of seconds should probably be decent enough. The current time of a client could be updated via a simple client-side javascript. I've seen these on many sites around the net. Together these two time-stamps would be part of a two row table -- one listed above the other to ease comparison.

Limited Auto-Refreshing: Implementation Details

This could be realized by two drop down lists, one for the refresh count and one for the iterval, and a submit style button called "Request Auto-Refreshes." The refreshes could be triggered at the desired intervals simply by the inclusion of the "REFRESH" meta-tag while the limited number of refreshes could be controled via some server-side counting.

Please judge these two ideas separately -- I only explained them together since they seem related to the same minor "inconvenience". I personally time the first idea is more useful that the second.
< Debian Users | Are There Any Sexual Scoop Sites? >

Menu
· create account
· faq
· search
· report bugs
· Scoop Administrators Guide
· Scoop Box Exchange

Login
Make a new account
Username:
Password:

Poll
My opinion is roughly...
· time-stamps are GOOD; auto-refresh is GOOD 0%
· time-stamps are GOOD; auto-refresh is BAD 100%
· time-stamps are BAD; auto-refresh is GOOD 0%
· time-stamps are BAD; auto-refresh is BAD 0%

Votes: 3
Results | Other Polls

Related Links
· Kuro5hin
· More on Feature Requests
· Also by alphabit

Story Views
  19 Scoop users have viewed this story.

Display: Sort:
suggestions: time-stamps & auto-refreshing | 3 comments (3 topical, 0 hidden)
Auto-refresh (none / 0) (#1)
by hulver on Tue Aug 13, 2002 at 01:27:24 AM PST

Bad. Don't like it.

How would you tell what comments are new if the page has refresh 3 times while you weren't looking?



-- HuSi - It's what scoop's for.



timestamps.. (none / 0) (#2)
by phill on Tue Aug 13, 2002 at 01:05:34 PM PST

provided you have scoop running on unix (or a variant) make a new box with the empty_box template. for the content put:
my $content=`/path/to/date`;
return $content;
.

then just put the box anywhere you want it. I like mine at the top of the page, personally.

(check this out on how to format the output of date)

oh, and auto-refresh is bad, especially when you are reading a long comment or post and it reloads on you and puts you back at the top of the screen.

-p



suggestions: time-stamps & auto-refreshing | 3 comments (3 topical, 0 hidden)
Display: Sort:

Hosted by ScoopHost.com Powered by Scoop
All trademarks and copyrights on this page are owned by their respective companies. Comments are owned by the Poster. The Rest © 1999 The Management

create account | faq | search