Hi all
I quite like the AJAX improvements (though there are lot of problems with that, see bug tracker), however what I really don't like are disappearing messages. Once something is done, the message just flashes on the top and it is impossible to read it (it's too quick) and what I find even worse, it is impossible to copy something from that.
For example when I'm inserting new row, I would like to copy new row ID, what is possible with non-AJAX version, but with AJAX, the message just flashes and is gone forever.
Michal Čihař a écrit :
Hi all
I quite like the AJAX improvements (though there are lot of problems with that, see bug tracker), however what I really don't like are disappearing messages. Once something is done, the message just flashes on the top and it is impossible to read it (it's too quick) and what I find even worse, it is impossible to copy something from that.
For example when I'm inserting new row, I would like to copy new row ID, what is possible with non-AJAX version, but with AJAX, the message just flashes and is gone forever.
So you would prefer a message that stays there and that you can close manually?
On Wed, Sep 1, 2010 at 7:47 PM, Marc Delisle marc@infomarc.info wrote:
Michal Čihař a écrit :
Hi all
I quite like the AJAX improvements (though there are lot of problems with that, see bug tracker), however what I really don't like are disappearing messages. Once something is done, the message just flashes on the top and it is impossible to read it (it's too quick) and what I find even worse, it is impossible to copy something from that.
For example when I'm inserting new row, I would like to copy new row ID, what is possible with non-AJAX version, but with AJAX, the message just flashes and is gone forever.
So you would prefer a message that stays there and that you can close manually?
Yes, It would be preferred.
-- Marc Delisle http://infomarc.info
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Hi
Dne Wed, 01 Sep 2010 10:47:23 -0400 Marc Delisle marc@infomarc.info napsal(a):
So you would prefer a message that stays there and that you can close manually?
I'd prefer same message as is in non-AJAX version. The SQL box is added/updated anyway, so why should not be message as well?
Hi,
On 01/09/2010, Michal Čihař michal@cihar.com wrote:
Hi
Dne Wed, 01 Sep 2010 10:47:23 -0400 Marc Delisle marc@infomarc.info napsal(a):
So you would prefer a message that stays there and that you can close manually?
I like this idea too.
I'd prefer same message as is in non-AJAX version. The SQL box is added/updated anyway, so why should not be message as well?
Some of the messages are trivial ones, like 'Loading', 'Processing Request'. Hence, I wanted to hide the message after a certain amount of time.
But, this use case was something that I did not think too much about. I can move the messages from the notification div on the top to a div above the SQL box, instead of showing it on the top as it is now. I've been trying to figure out what has been causing the messages to disappear since yesterday, but could not understand why jQuery's clearQueue() was failing. Should I go ahead and make this change?
Hi
Dne Thu, 2 Sep 2010 01:40:30 +0530 Ninad Pundalik ninadsp16289@gmail.com napsal(a):
Some of the messages are trivial ones, like 'Loading', 'Processing Request'. Hence, I wanted to hide the message after a certain amount of time.
Yes, it is reasonable for such temporary messages, but not for results of some operation.
But, this use case was something that I did not think too much about. I can move the messages from the notification div on the top to a div above the SQL box, instead of showing it on the top as it is now. I've been trying to figure out what has been causing the messages to disappear since yesterday, but could not understand why jQuery's clearQueue() was failing. Should I go ahead and make this change?
Yes.
Hi,
I committed the change in commit 857310a on my branch. Please check it out on the demo server and suggest some improvements for the CSS for the notifications. I have removed the loading gif that was part of the CSS for that division, as it does not make sense to show it for all the messages.
Hi
Dne Thu, 2 Sep 2010 23:03:13 +0530 Ninad Pundalik ninadsp16289@gmail.com napsal(a):
I committed the change in commit 857310a on my branch. Please check it out on the demo server and suggest some improvements for the CSS for the notifications. I have removed the loading gif that was part of the CSS for that division, as it does not make sense to show it for all the messages.
It looks broken for me, I tried just one thing - adding new user.
On current master, the dialog disappears after submitting and message flashes for some time.
On your branch, the dialog is still there and empty message box is show under it.