On Sat, Jul 30, 2011 at 9:13 PM, Marc Delisle marc@infomarc.info wrote:
Le 2011-07-30 14:05, Tyron Madlener a écrit :
As mentioned in the Instructions dialog you will need to first setup logging then select a time span in any of the charts. This will open a dialog that let's you load the logs.
I admit I had not read all the "Using the monitor" explanation, but I have a suggestion. The second paragraph starting with "When you get to see..." should have a bold title like "Displaying queries for a time span". This would have got my attention better.
Ok, I've changed the whole paragraph to: "To display queries from the logs, select the relevant time span on any chart by holding down the left mouse button and panning over the chart. Once confirmed, this will load a table of grouped queries, there you may click on any occuring SELECT statements to further analyze them."
This is shorter and should be more clear, I hope :)
Well, I liked the idea of "sudden spike of activity".
It's a good example but probably doesn't quite represent what a database administrator should be doing (as in staring at the screen looking for activity spikes all day long ;-), meaning it could also be under permanent heavy load.
Do you plan to add a bold title for this paragraph?
That would look not harmonic to me. That paragraph should be read as part of the 'Using the Monitor'-"chapter", but putting a bold line above there would make it look like it's not part of 'Using the Monitor'. Then I would need to make the other bold lines in a bigger font, which might not look the same nice. Does that make sense somehow? :)
Might be worth considering to open the same dialog through a link at the top right to the instructions link.
Or I could add a notice below the charts advising the users to select a time span.
Could be useful but users should have read the instructions :)
If we can lead the user to use the tool correctly in a subtle way, it's definitely better I think. Only question is whether a notice box below the charts is subtle enough ;-) I'll leave it as it is for now and we just observe how many users don't find it.
Another suggestion: near the "Disable" links for the logs, add links to disable and empty the logs in one click, unless you find this too dangerous.
Yea I was also thinking of adding a link to empty the table. Combining that with a log disable is a good idea too.
Thanks for having a look at my work.
-- Marc Delisle http://infomarc.info
Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel