On 06-12-10 16:08, SourceForge.net wrote:
https://sourceforge.net/tracker/?func=detail&atid=377408&aid=3119882...
I'd like to hear some opinions on how 'loud' a warning for a 'slow' feature should be.
Herman van Rink a écrit :
On 06-12-10 16:08, SourceForge.net wrote:
https://sourceforge.net/tracker/?func=detail&atid=377408&aid=3119882...
I'd like to hear some opinions on how 'loud' a warning for a 'slow' feature should be.
Maybe we need a class for loud warnings and one to whisper a warning. The whisper one would not be in red.
Hi
Dne Mon, 06 Dec 2010 16:12:21 +0100 Herman van Rink rink@initfour.nl napsal(a):
On 06-12-10 16:08, SourceForge.net wrote:
https://sourceforge.net/tracker/?func=detail&atid=377408&aid=3119882...
I'd like to hear some opinions on how 'loud' a warning for a 'slow' feature should be.
I don't see that this feature would be slow (or at least I don't notice anything), however it could be definitely faster if the image was not inline base64 encoded.
For the warning, I'd prefer <div class="notice"> with link inside it. And it should disappear when stats are shown (I don't see need to pollute page with way to hide it after it is loaded).
Michal Čihař a écrit :
Hi
Dne Mon, 06 Dec 2010 16:12:21 +0100 Herman van Rink rink@initfour.nl napsal(a):
On 06-12-10 16:08, SourceForge.net wrote:
https://sourceforge.net/tracker/?func=detail&atid=377408&aid=3119882...
I'd like to hear some opinions on how 'loud' a warning for a 'slow' feature should be.
I don't see that this feature would be slow (or at least I don't notice anything), however it could be definitely faster if the image was not inline base64 encoded.
For the warning, I'd prefer <div class="notice"> with link inside it. And it should disappear when stats are shown (I don't see need to pollute page with way to hide it after it is loaded).
Probably the same principle would apply on the databases page.
2010/12/6 Marc Delisle marc@infomarc.info:
Michal Čihař a écrit :
Hi
Dne Mon, 06 Dec 2010 16:12:21 +0100 Herman van Rink rink@initfour.nl napsal(a):
On 06-12-10 16:08, SourceForge.net wrote:
https://sourceforge.net/tracker/?func=detail&atid=377408&aid=3119882...
I'd like to hear some opinions on how 'loud' a warning for a 'slow' feature should be.
I don't see that this feature would be slow (or at least I don't notice anything), however it could be definitely faster if the image was not inline base64 encoded.
On my little server (not a very fast CPU) this page loaded slow. ;)
For the warning, I'd prefer <div class="notice"> with link inside it. And it should disappear when stats are shown (I don't see need to pollute page with way to hide it after it is loaded).
Which 'link inside it' do you mean? The actual link to display the graph? I agree with not showing the warning/disable link after clicking, I just put it there because it was done that way on the database page.
Probably the same principle would apply on the databases page.
Agreed.
Maybe a config option can be created that disables 'heavy' features (with a link to enable them), or enables them.
Greets,
Dieter
Dieter Adriaenssens a écrit :
2010/12/6 Marc Delisle marc@infomarc.info:
Michal Čihař a écrit :
Hi
Dne Mon, 06 Dec 2010 16:12:21 +0100 Herman van Rink rink@initfour.nl napsal(a):
On 06-12-10 16:08, SourceForge.net wrote:
https://sourceforge.net/tracker/?func=detail&atid=377408&aid=3119882...
I'd like to hear some opinions on how 'loud' a warning for a 'slow' feature should be.
I don't see that this feature would be slow (or at least I don't notice anything), however it could be definitely faster if the image was not inline base64 encoded.
On my little server (not a very fast CPU) this page loaded slow. ;)
For the warning, I'd prefer <div class="notice"> with link inside it. And it should disappear when stats are shown (I don't see need to pollute page with way to hide it after it is loaded).
Which 'link inside it' do you mean? The actual link to display the graph? I agree with not showing the warning/disable link after clicking, I just put it there because it was done that way on the database page.
Probably the same principle would apply on the databases page.
Agreed.
Maybe a config option can be created that disables 'heavy' features (with a link to enable them), or enables them.
We try to avoid adding config options if possible. I think it's enough that it be disabled by default, with a link like you did.
Hi all,
I made some snapshots of possible views. What do you think?
Kind regards,
Dieter
Dieter Adriaenssens a écrit :
Hi all,
I made some snapshots of possible views. What do you think?
I believe that the link is not really part of the note so I would go with the third one.
On 06-12-10 21:25, Marc Delisle wrote:
Dieter Adriaenssens a écrit :
Hi all,
I made some snapshots of possible views. What do you think?
I believe that the link is not really part of the note so I would go with the third one.
Although the inline variant does appeal, Marc is probably right about choosing the seperate_link_and_notice.png option.
But lets remove the 'Hide query chart' link and the 'Disable Statistics' from the databases page.
Hi all,
2010/12/7 Herman van Rink rink@initfour.nl:
On 06-12-10 21:25, Marc Delisle wrote:
Dieter Adriaenssens a écrit :
Hi all,
I made some snapshots of possible views. What do you think?
I believe that the link is not really part of the note so I would go with the third one.
Although the inline variant does appeal, Marc is probably right about choosing the seperate_link_and_notice.png option.
But lets remove the 'Hide query chart' link and the 'Disable Statistics' from the databases page.
Done and pushed to repository.
I was just going to regenerate the po files, but Marc had already pushed them. ;)
Greets,
Dieter
-- Met vriendelijke groet / Regards,
Herman van Rink Initfour websolutions
What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
On 06-12-10 16:30, Michal Čihař wrote:
I don't see that this feature would be slow (or at least I don't notice anything), however it could be definitely faster if the image was not inline base64 encoded.
The inline encoding was added to avoid having two separate http requests that need the same info from the database. And for query statistics it seemed undesirable to store the intermediate results in the session.
When I go on2 sharkysworld.net./wp-admin I get this message: Fatal error: Unsupported operand types in /home/sharky88/public_html/wp-content/themes/clear-line/options/value_sets.php on line 4 Now i just started this site, I downloaded something off another site & tried 2 publish tht. I no the problem the download had a link. That can't be published. If u can help me get back 2 where I was before tht I 'll make a donation 2 you. 10x a lot, dvardo59
On Mon, Dec 6, 2010 at 11:45 PM, Herman van Rink rink@initfour.nl wrote:
On 06-12-10 16:30, Michal Čihař wrote:
I don't see that this feature would be slow (or at least I don't notice anything), however it could be definitely faster if the image was not inline base64 encoded.
The inline encoding was added to avoid having two separate http requests that need the same info from the database. And for query statistics it seemed undesirable to store the intermediate results in the session.
-- Met vriendelijke groet / Regards,
Herman van Rink Initfour websolutions
What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Daniel Bishop a écrit :
When I go on2 sharkysworld.net./wp-admin I get this message: Fatal error: Unsupported operand types in /home/sharky88/public_html/wp-content/themes/clear-line/options/value_sets.php
Hi, this list is for phpMyAdmin developers; please contact a Wordpress help forum or your host provider.
10x 4 t info, host provider got me going. Explain the terms. What is XML? Explain XML 1 time at least in the beginning. You gotta tell people what your exactly what you'll do 4 them. Get them more involved Ok, I got this website back 2 where i can use it again. I uninstalled wordpress, & reinstalled it & tht took care of tht fatal error. Ok, Im gonna get this monkey off my back. I'm starting the yawning, watery eyes, & not runny nose yet. cu l8r g8r, dan
On Tue, Dec 7, 2010 at 8:28 AM, Marc Delisle marc@infomarc.info wrote:
Daniel Bishop a écrit :
When I go on2 sharkysworld.net./wp-admin I get this message: Fatal error: Unsupported operand types in
/home/sharky88/public_html/wp-content/themes/clear-line/options/value_sets.php
Hi, this list is for phpMyAdmin developers; please contact a Wordpress help forum or your host provider.
-- Marc Delisle http://infomarc.info
What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Hi
Dne Tue, 07 Dec 2010 08:45:09 +0100 Herman van Rink rink@initfour.nl napsal(a):
On 06-12-10 16:30, Michal Čihař wrote:
I don't see that this feature would be slow (or at least I don't notice anything), however it could be definitely faster if the image was not inline base64 encoded.
The inline encoding was added to avoid having two separate http requests that need the same info from the database. And for query statistics it seemed undesirable to store the intermediate results in the session.
Well, but using base64 you almost double amount of data which need to be transferred plus you put workload on the browser to parse much bigger HTML. What is IMHO biggest cause of the slowdown, not the chart itself.
I'd rather prefer having image external and pass numbers to it as parameters (to avoid saving data in the session).