Hi all
I again came to question whether we should disable tabs or not when table is empty. As it won't be updated when user uses external program [1] to fill the table, I'm still more inclined to remove disabling.
What do you thing about this issue?
[1]:https://sourceforge.net/tracker/index.php?func=detail&aid=1294369&gr...
Michal Čihař a écrit :
Hi all
I again came to question whether we should disable tabs or not when table is empty. As it won't be updated when user uses external program [1] to fill the table, I'm still more inclined to remove disabling.
What do you thing about this issue?
In general, I like this feature. I think that in most situations it's correct to disable those.
What about a new Refresh link near the tabs that would regenerate them?
Marc
On Tue, 17 Oct 2006 08:39:26 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
In general, I like this feature. I think that in most situations it's correct to disable those.
What this feature brings?
+ You directly see whether table is empty? - You have to reload when insert data using another way. - We need to care about refreshing it on some queries. (eg. bug #1441833)
What about a new Refresh link near the tabs that would regenerate them?
I don't like cluttering interface with refresh button...
Hi,
and when we use an event on mouseover on the disabled tabs? Perhabs with an little ajax request? Sample: onmouseover =3D "checkTable('tablename');";
If table not empty, enable it else do nothing ;) With ajax we don't really ned a refresh button.
Michael =20
--- Original Message --- Mail from: Michal C(ihar( Date: 17.10.2006 14:46
On Tue, 17 Oct 2006 08:39:26 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
=20
In general, I like this feature. I think that in most situations it's =
correct to disable those. =20
What this feature brings?
- You directly see whether table is empty?
- You have to reload when insert data using another way.
- We need to care about refreshing it on some queries. (eg. bug
#1441833)
=20
What about a new Refresh link near the tabs that would regenerate them=
?
=20
I don't like cluttering interface with refresh button...
--------------050607060900080304050603 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content=3D"text/html;charset=3DISO-8859-1" http-equiv=3D"Content-= Type"> </head> <body bgcolor=3D"#ffffff" text=3D"#000000"> Hi,<br> <br> and when we use an event on mouseover on the disabled tabs?<br> Perhabs with an little ajax request?<br> Sample: onmouseover =3D "checkTable('tablename');";<br> <br> If table not empty, enable it else do nothing ;)<br> With ajax we don't really ned a refresh button.<br> <br> Michael <br> <br> --- Original Message ---<br> Mail from: Michal Čihař<br> Date: 17.10.2006 14:46 <blockquote cite=3D"mid20061017144620.413bc1cf@mic.sysgo.cz" type=3D"cite= "> <pre wrap=3D"">On Tue, 17 Oct 2006 08:39:26 -0400 Marc Delisle <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:Marc.Delis= le@cegepsherbrooke.qc.ca"><Marc.Delisle@cegepsherbrooke.qc.ca></a> = wrote:
</pre> <blockquote type=3D"cite"> <pre wrap=3D"">In general, I like this feature. I think that in most = situations it's=20 correct to disable those. </pre> </blockquote> <pre wrap=3D""><!----> What this feature brings?
+ You directly see whether table is empty? - You have to reload when insert data using another way. - We need to care about refreshing it on some queries. (eg. bug #1441833)
</pre> <blockquote type=3D"cite"> <pre wrap=3D"">What about a new Refresh link near the tabs that would= regenerate them? </pre> </blockquote> <pre wrap=3D""><!----> I don't like cluttering interface with refresh button...</pre> </blockquote> </body> </html>
--------------050607060900080304050603--
Michael Keck a écrit :
Hi,
and when we use an event on mouseover on the disabled tabs? Perhabs with an little ajax request? Sample: onmouseover =3D "checkTable('tablename');";
If table not empty, enable it else do nothing ;) With ajax we don't really ned a refresh button.
Michael =20
I don't know much about AJAX, would this be complex? and compatible with all browsers?
marc
With ajax we don't really ned a refresh button.
I don't know much about AJAX, would this be complex? and compatible with all browsers?
marc
All modern (newer browsers) may be able to handle AJAX and it's mainly used function XMLHttpRequest.
I don't know since wich version, but since browser generation 6, like IE 6, NS 6, FF 1.5 ... yes! I'm working with AJAX, and I know with listed browser above, there's no problem.
Sometimes it would be complex. But for our needs to check if a table empty not. It would only return like 'empty' or 'not empty' and set the browse-tab state and empty-tab state.
The changes we need: the browse-tab and empty-tab need unique ids.
Regards Michael
Michal Čihař a écrit :
On Tue, 17 Oct 2006 08:39:26 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
In general, I like this feature. I think that in most situations it's correct to disable those.
What this feature brings?
- You directly see whether table is empty?
- You have to reload when insert data using another way.
- We need to care about refreshing it on some queries. (eg. bug
#1441833)
What about a new Refresh link near the tabs that would regenerate them?
I don't like cluttering interface with refresh button...
We could also set a different color on the tab, but not disable it. On mouseover, display a message that states that PMA thinks that this table is empty, or something like that.
Marc
On Tue, 17 Oct 2006 10:54:15 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
We could also set a different color on the tab, but not disable it. On mouseover, display a message that states that PMA thinks that this table is empty, or something like that.
I thought about similar solution - make the tab work, only make it look disabled.
On Tue, 17 Oct 2006 17:03:36 +0200 Michal Čihař michal@cihar.com wrote:
On Tue, 17 Oct 2006 10:54:15 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
We could also set a different color on the tab, but not disable it. On mouseover, display a message that states that PMA thinks that this table is empty, or something like that.
I thought about similar solution - make the tab work, only make it look disabled.
Any comments about this?
Michal Čihař a écrit :
On Tue, 17 Oct 2006 17:03:36 +0200 Michal Čihař michal@cihar.com wrote:
On Tue, 17 Oct 2006 10:54:15 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
We could also set a different color on the tab, but not disable it. On mouseover, display a message that states that PMA thinks that this table is empty, or something like that.
I thought about similar solution - make the tab work, only make it look disabled.
Any comments about this?
If the tab is greyed, there is a big X on mouseover. What do we do with this X ?
I think that, if the tab is operational, it should not be greyed. Maybe instead of being greyed and the big X, there should be a message on mouseover stating that "this table is probably empty, unless an external source changed it".
There is also the reverse case: when PMA built the tabs, table was not empty but now it is!
Marc
On Fri, 20 Oct 2006 08:40:35 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
If the tab is greyed, there is a big X on mouseover. What do we do with this X ?
I think that, if the tab is operational, it should not be greyed. Maybe instead of being greyed and the big X, there should be a message on mouseover stating that "this table is probably empty, unless an external source changed it".
Well the tab is always operation, you only don't get any results.
There is also the reverse case: when PMA built the tabs, table was not empty but now it is!
And does something really wrong happen in this case?
Michal Čihař a écrit :
On Fri, 20 Oct 2006 08:40:35 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
If the tab is greyed, there is a big X on mouseover. What do we do with this X ?
I think that, if the tab is operational, it should not be greyed. Maybe instead of being greyed and the big X, there should be a message on mouseover stating that "this table is probably empty, unless an external source changed it".
Well the tab is always operation, you only don't get any results.
I'm pretty sure that we got bug reports about this: "I click Browse and I don't get results", this is why it got greyed!
There is also the reverse case: when PMA built the tabs, table was not empty but now it is!
And does something really wrong happen in this case?
No :)
-
Marc Delisle -
Michael Keck -
Michal Čihař