This is just the kind of interface I had in mind when I wrote
PerlMonks::NewestNodes, and the kind of interface I had been
waiting for for a longe time. Thanks, Shendal! Shendal++
I've been using it today for surfing PM, and it's very useful.
A few suggestions I have (more like "requests for features"):
- * Mark "read nodes" (the ones you double-click on) with
a different color (a dim gray, maybe?) so that they can be
distinguished from nodes you haven't read.
- * If you do the above, have an option for having the whole
subtree marked as read when you double-click on its top node
(since, when you view a node, you can also read all of its
replies on the same page).
- Make it not "re-collapse" the whole tree when you hit
refresh, only add the new nodes. I don't know how hard this is,
since I'm not familiar with the Tk::Tree widget.
- * Coupled with the above, mark "new nodes" (the ones that
appeared in the last "refresh" with a different color.
- When you reduce the window's width, the rightmost buttons
start to disappear. I think it'd be better if all the buttons
shrank proportionally, or if the status line shrank instead.
- The "reviews" category of nodes refers to reviews in
general (modules, books, etc.), so it may be more appropriately
called "Reviews" instead of "Book Reviews".
- Make it so that it's possible to collapse/expand a whole
subtree in one click. For example, have it so that if you click
on the +/- indicator with the middle button, the operation
applies to all the subtrees of the current node.
- Have an option for automatically refreshing periodically.
The items I marked with "*" are the ones for which I believe
I can add support in PerlMonks::NewestNodes (for example, being
able to identify the "new nodes" from a flag in the node, similarly
for "read nodes"). I'll
be adding those things shortly.
--ZZamboni
-
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.
|
