Newest Nodes gets big- really big, really fast. There have been numerous suggestions on organizing Newest Nodes, for example, the checkbox addition which I wouldn't mind. But we all know vroom is busy killing innocent squirrel mommies, so I've come up with less programmer intensive solution.

THE NEWEST NODES FREEZE FEATURE

Don't make me repeat myself. In this parallel universe, I see a button next to the "clear flags" button which says "FREEZE FEATURE- special thanks to AgentM, an all around cool guy" or whatever part of that text fits. This button, when pushed appropriately down (not up) would "freeze" the current date in the Newest Nodes so that clicking Newest Nodes again would not update the time. Essentially, it would provide "show me nodes only between the last time I wanted to update and the time I last pushed the freeze button" so that the user is not overloaded and frustrated with the amount of new data loading each time. Obviously, this would also lead to some cacheing improvements, hence possibly minor performance improvements. This feature would allow one to divide up one's time between a multitude of nodes. For example, I might get up and say, "I've got 50 nodes to read, I'd better freeze." or "I'll read these nodes tomorrow- and to make sure I can see them just like this on my other computer, I'll freeze."

I know what you're saying- "Sheesh, you stupid butthead, just click BACK!" I assure you, I do that. But you web developers also know that site navigation shouldn't be left to the back button (ESPECIALLY not the jscript routine that is analogous). Also, proxies and browsers that interpret no cache literally may point and laugh at you. Additionally, you can't save your unread Newest Nodes overnight AND read them on a different computer without the hassle of saving HTML to some drive.

Of course, once clicked, the button must reveal the option to "unfreeze" or "update" the Newest Nodes since I'm sure no one wants to miss out on another quality Tutorial. I BEG to get some more tasty and delicious Newest Nodes functionality. The NodeReaper eagerly awaits your suggestions below. 8-) Thanks.

Edited by Petruchio: added smiley face

AgentM Systems nor Nasca Enterprises nor Bone::Easy nor Macperl is responsible for the comments made by AgentM. Remember, you can build any logical system with NOR.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.