User talk:A930913/wave

Addshore's thoughts
Things I would like to see:  ·addshore·  talk to me!
 * 1) The wikipedia page text seems rather large when using the tool, could this be reduced by default rather than having to zoom out in my browser?
 * 2) Strip some of the useless menus and navigation out of the wikipedia pages? (Potentially use the api to call the diff, this would dramatically decrease the amount of content the user would need to load each time)
 * 3) What is the point of the 'Innocent/Next' button if it is always disabled? :D
 * 4) A back button (there are cases when I don't see anything wrong with a diff, click to view the next one and as I do I spot something that actually should have been reverted in the previous one, being able to go back to the previous diff viewed would solve this! :D).
 * 5) Some sort of color highlighting for classification of edits in the queue (although this may not be possible ? I dont know how the backend of this works :))
 * 6) Some sort of pre loading of diffs would be awesome (but again not sure if it is easy with the backend)
 * It's the default, I think #2 is a better idea.
 * That is the idea; at the moment the wikipedia part is very simple, as I don't know too much of the wikipedia javascript. I'm looking for someone who knows the ins and outs who can help/advise.
 * It's not, the ClueBot feed uses it.
 * Yup; first I need to stack the history
 * The only classification used so far is tagging edits with the warn level of the editor. It's more that I haven't implemented much rather than it not being possible. The idea is that custom feeds can be fairly easily written and imported — fetching, colouring and ranking.
 * Would be ideal, though I don't know how soon I'll be able to implement it. Also see #2.
 * 930913(Congratulate) 23:20, 8 June 2013 (UTC)

Firefox?
Also monobook. Plz. :) Legoktm (talk) 23:21, 8 June 2013 (UTC)
 * Firefox is broken and they won't fix it, because they consider it a security risk.
 * I'm making WAVE with vector, and am not personally testing monobook, so that's why I'm saying confirmed with vector. Unless monobook is different in a few key areas, it should work fine. 930913(Congratulate) 00:48, 9 June 2013 (UTC)
 * I was using monobook when I tested it and it seemed to be okay, except for the large text as mentioned above.  ·addshore·  talk to me! 09:31, 9 June 2013 (UTC)