| [reply] [Watch: Dir/Any] [d/l] |
TT elements are being stripped in an attempt to remove the existing ++ and -- text, but TT elements are also used for code tags.
It's just a question of fixing the XPath query. "//tt" needs to be replaced. I think "//div[@class='vote']//tt" will do the trick.
| [reply] [Watch: Dir/Any] [d/l] [select] |
Yes, I had started noting that peculiar behaviour. I have updated the script with your new XPath query. Thanks.
| [reply] [Watch: Dir/Any] |
Couple of things:
- I use http://perlmonks.org/, not http://www.perlmonks.* ;-)
- The ++ and -- links are not really user friendly. I'd opt for the radio buttons with a button next to them
- Your script breaks the voting booth
- Why do I have to refresh the page to see the ratings? Isn't the point to _not_ to refresh?
--
b10m
All code is usually tested, but rarely trusted.
| [reply] [Watch: Dir/Any] |
- You can add http://perlmonks.org/* to your "Included pages" when you "Manage User Scripts..." in GreaseMonkey.
- Subjective. I feel they are more user friendly as they are single-click.
- I'll take a look at the voting booth. It must use a similar form to post-voting. Update: Looks like this is a JavaScript bug when calling document.evaluate on an XPath - appears to be picking nodes with similar XPaths! Best workaround is to disable the VB node.
- You do save refreshes especially in the long run. You no longer need to refresh the page (by pressing the "vote" button) before moving to another node.
I must admit I was not expecting to please everyone ;-)
| [reply] [Watch: Dir/Any] |
- This was more a pointer, you may want to include that in your next release
- Ok, so we disagree
- Nice workaround ;-)
The last point requires some more text, so I'll comment on that here.
IMHO, your GM script (no matter funny and handy) will not help much. You still request a lot of pages and AFAIK, the content is still being returned to the client (we just ignore it at this point). Since we already receive the whole page back, why not strip out the relevant information to update the new "reputation"?
Also, why not update the "votes left" in the XP Nodelet at the same time? (I don't believe you do that now). That way, in the end, we end up with slightly more page requests, but at least it's fun ;-)
Right now, I'm actually putting more stress on the PM server, for usually I vote for a few nodes, then hit the Vote button and all is handled in a single page request. I see the amount of votes I have left, and I see the node's reputation. Now I launch a request for every single vote, and I have to launch another one, to see the result!
"I must admit I was not expecting to please everyone ;-)"
You've posted code to a critical (and often cynical) audience. Expect feedback ;-)
--
b10m
All code is usually tested, but rarely trusted.
| [reply] [Watch: Dir/Any] |