Hi,
i would like to introduce saving server, db and table in cookie too, but only checked in index.php
so a user will always return to the last opened server/db/table
// with true phpMyAdmin will save last opened server/db/table in a // cookie and restore it when phpMyAdmin re-opens $cfg['RememberLastPosition'] = true;
Hi
On Wed, 02 Aug 2006 09:16:45 +0200 Sebastian Mendel lists@sebastianmendel.de wrote:
i would like to introduce saving server, db and table in cookie too, but only checked in index.php
so a user will always return to the last opened server/db/table
Good idea.
// with true phpMyAdmin will save last opened server/db/table in a // cookie and restore it when phpMyAdmin re-opens $cfg['RememberLastPosition'] = true;
I think this would be better if configured per user, but we don't have framework for that...
Sebastian Mendel a écrit :
Hi,
i would like to introduce saving server, db and table in cookie too, but only checked in index.php
so a user will always return to the last opened server/db/table
OK.
// with true phpMyAdmin will save last opened server/db/table in a // cookie and restore it when phpMyAdmin re-opens $cfg['RememberLastPosition'] = true;
I would avoid adding another config parameter. I don't see why someone would not be happy to see his last server/db/table. Fear of having more cookies?
Marc
On Wed, 02 Aug 2006 07:40:42 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
I would avoid adding another config parameter. I don't see why someone would not be happy to see his last server/db/table. Fear of having more cookies?
I would not be happy, because I work on different database most time :-)
Michal Čihař a écrit :
On Wed, 02 Aug 2006 07:40:42 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
I would avoid adding another config parameter. I don't see why someone would not be happy to see his last server/db/table. Fear of having more cookies?
I would not be happy, because I work on different database most time :-)
When you return to the same db, you would be happy. When you have to switch, you have to choose it anyway from the left panel. So ?
Marc
On Wed, 02 Aug 2006 07:47:04 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
When you return to the same db, you would be happy. When you have to switch, you have to choose it anyway from the left panel. So ?
Loading table listing with many tables can take long time...
Simply I prefer being always brought to welcome page :-).
Michal Čihař a écrit :
On Wed, 02 Aug 2006 07:47:04 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
When you return to the same db, you would be happy. When you have to switch, you have to choose it anyway from the left panel. So ?
Loading table listing with many tables can take long time...
Simply I prefer being always brought to welcome page :-).
Ok I see your point. On a multi-user installation of PMA, how a $cfg['RememberLastPosition'] (be it true of false) will please everyone?
Marc
Marc Delisle schrieb:
Michal Čihař a écrit :
On Wed, 02 Aug 2006 07:47:04 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
When you return to the same db, you would be happy. When you have to switch, you have to choose it anyway from the left panel. So ?
Loading table listing with many tables can take long time...
Simply I prefer being always brought to welcome page :-).
Ok I see your point. On a multi-user installation of PMA, how a $cfg['RememberLastPosition'] (be it true of false) will please everyone?
with set to false, phpMyAdmin can present a link on the main.php that will 'warp' them to the last opened object
Sebastian Mendel a écrit :
Marc Delisle schrieb:
Michal Čihař a écrit :
On Wed, 02 Aug 2006 07:47:04 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
When you return to the same db, you would be happy. When you have to switch, you have to choose it anyway from the left panel. So ?
Loading table listing with many tables can take long time...
Simply I prefer being always brought to welcome page :-).
Ok I see your point. On a multi-user installation of PMA, how a $cfg['RememberLastPosition'] (be it true of false) will please everyone?
with set to false, phpMyAdmin can present a link on the main.php that will 'warp' them to the last opened object
Not a bad idea! So PMA would always remember these in a cookie; Michal has a problem with what PMA does with what is remembered :)
The setting could be named ShowLastPosition, true would warp automatically and false would provide a warp link.
Marc
Marc Delisle schrieb:
Sebastian Mendel a écrit :
Marc Delisle schrieb:
Michal Čihař a écrit :
On Wed, 02 Aug 2006 07:47:04 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
When you return to the same db, you would be happy. When you have to switch, you have to choose it anyway from the left panel. So ?
Loading table listing with many tables can take long time...
Simply I prefer being always brought to welcome page :-).
Ok I see your point. On a multi-user installation of PMA, how a $cfg['RememberLastPosition'] (be it true of false) will please everyone?
with set to false, phpMyAdmin can present a link on the main.php that will 'warp' them to the last opened object
Not a bad idea! So PMA would always remember these in a cookie; Michal has a problem with what PMA does with what is remembered :)
The setting could be named ShowLastPosition, true would warp automatically and false would provide a warp link.
ShowLastPosition = false
Should automatically switch to last position? This is confusing, isn't it?
Sebastian Mendel a écrit :
Marc Delisle schrieb:
Sebastian Mendel a écrit :
Marc Delisle schrieb:
Michal Čihař a écrit :
On Wed, 02 Aug 2006 07:47:04 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
When you return to the same db, you would be happy. When you have to switch, you have to choose it anyway from the left panel. So ?
Loading table listing with many tables can take long time...
Simply I prefer being always brought to welcome page :-).
Ok I see your point. On a multi-user installation of PMA, how a $cfg['RememberLastPosition'] (be it true of false) will please everyone?
with set to false, phpMyAdmin can present a link on the main.php that will 'warp' them to the last opened object
Not a bad idea! So PMA would always remember these in a cookie; Michal has a problem with what PMA does with what is remembered :)
The setting could be named ShowLastPosition, true would warp automatically and false would provide a warp link.
ShowLastPosition = false
Should automatically switch to last position? This is confusing, isn't it?
ShowLastPosition = true automatically switches to last position ShowLastPosition = false provides a link to go to last position
Marc Delisle a écrit :
Sebastian Mendel a écrit :
Marc Delisle schrieb:
Sebastian Mendel a écrit :
Marc Delisle schrieb:
Michal Čihař a écrit :
On Wed, 02 Aug 2006 07:47:04 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
> When you return to the same db, you would be happy. When you have to > switch, you have to choose it anyway from the left panel. So ? Loading table listing with many tables can take long time...
Simply I prefer being always brought to welcome page :-).
Ok I see your point. On a multi-user installation of PMA, how a $cfg['RememberLastPosition'] (be it true of false) will please everyone?
with set to false, phpMyAdmin can present a link on the main.php that will 'warp' them to the last opened object
Not a bad idea! So PMA would always remember these in a cookie; Michal has a problem with what PMA does with what is remembered :)
The setting could be named ShowLastPosition, true would warp automatically and false would provide a warp link.
ShowLastPosition = false
Should automatically switch to last position? This is confusing, isn't it?
ShowLastPosition = true automatically switches to last position ShowLastPosition = false provides a link to go to last position
Or call it "AutoLastPosition".
Marc Delisle schrieb:
Sebastian Mendel a écrit :
Marc Delisle schrieb:
Sebastian Mendel a écrit :
Marc Delisle schrieb:
Michal Čihař a écrit :
On Wed, 02 Aug 2006 07:47:04 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
> When you return to the same db, you would be happy. When you have to > switch, you have to choose it anyway from the left panel. So ? Loading table listing with many tables can take long time...
Simply I prefer being always brought to welcome page :-).
Ok I see your point. On a multi-user installation of PMA, how a $cfg['RememberLastPosition'] (be it true of false) will please everyone?
with set to false, phpMyAdmin can present a link on the main.php that will 'warp' them to the last opened object
Not a bad idea! So PMA would always remember these in a cookie; Michal has a problem with what PMA does with what is remembered :)
The setting could be named ShowLastPosition, true would warp automatically and false would provide a warp link.
ShowLastPosition = false
Should automatically switch to last position? This is confusing, isn't it?
ShowLastPosition = true automatically switches to last position ShowLastPosition = false provides a link to go to last position
oh
but 'Show' does not imply that the user will automatically switched to last position
possibilities are: Remember..., Switch..., Open..., StartWith...
Sebastian Mendel a écrit :
Marc Delisle schrieb:
Sebastian Mendel a écrit :
Marc Delisle schrieb:
Sebastian Mendel a écrit :
Marc Delisle schrieb:
Michal Čihař a écrit : > On Wed, 02 Aug 2006 07:47:04 -0400 > Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote: > >> When you return to the same db, you would be happy. When you have to >> switch, you have to choose it anyway from the left panel. So ? > Loading table listing with many tables can take long time... > > Simply I prefer being always brought to welcome page :-). Ok I see your point. On a multi-user installation of PMA, how a $cfg['RememberLastPosition'] (be it true of false) will please everyone?
with set to false, phpMyAdmin can present a link on the main.php that will 'warp' them to the last opened object
Not a bad idea! So PMA would always remember these in a cookie; Michal has a problem with what PMA does with what is remembered :)
The setting could be named ShowLastPosition, true would warp automatically and false would provide a warp link.
ShowLastPosition = false
Should automatically switch to last position? This is confusing, isn't it?
ShowLastPosition = true automatically switches to last position ShowLastPosition = false provides a link to go to last position
oh
but 'Show' does not imply that the user will automatically switched to last position
possibilities are: Remember..., Switch..., Open..., StartWith...
AutoLastPosition does imply the automatic idea. But if the team prefers Remember, no problem. It's just that "remember" for me means "store in a cookie", not what you do with what is remembered.
Marc
On Wed, 02 Aug 2006 09:12:08 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
Not a bad idea! So PMA would always remember these in a cookie; Michal has a problem with what PMA does with what is remembered :)
The setting could be named ShowLastPosition, true would warp automatically and false would provide a warp link.
ShowLastPosition = false means that phpMyAdmin remembers position? It's confustion.
I think RememberLastPosition is better (and when it's false, link will be shown).
Michal Čihař a écrit :
On Wed, 02 Aug 2006 09:12:08 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
Not a bad idea! So PMA would always remember these in a cookie; Michal has a problem with what PMA does with what is remembered :)
The setting could be named ShowLastPosition, true would warp automatically and false would provide a warp link.
ShowLastPosition = false means that phpMyAdmin remembers position? It's confustion.
I said that true goes automatically and false provides a link.
I think RememberLastPosition is better (and when it's false, link will be shown).
On Wed, 02 Aug 2006 08:08:03 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
Ok I see your point. On a multi-user installation of PMA, how a $cfg['RememberLastPosition'] (be it true of false) will please everyone?
No way :-). We should finally move to per user configuration...
hi,
Marc Delisle wrote:
I would avoid adding another config parameter. I don't see why someone would not be happy to see his last server/db/table. Fear of having more cookies?
like letting the user choose lang,theme, and now even fontsize :) why not a litte checkbox "remember table" or "always save position" on main.php ?
windkiel a écrit :
hi,
Marc Delisle wrote:
I would avoid adding another config parameter. I don't see why someone would not be happy to see his last server/db/table. Fear of having more cookies?
like letting the user choose lang,theme, and now even fontsize :) why not a litte checkbox "remember table" or "always save position" on main.php ?
In the interest of interface simplicity.
Marc
windkiel schrieb:
hi,
Marc Delisle wrote:
I would avoid adding another config parameter. I don't see why someone would not be happy to see his last server/db/table. Fear of having more cookies?
like letting the user choose lang,theme, and now even fontsize :) why not a litte checkbox "remember table" or "always save position" on main.php ?
you could easily add every single config option ... what a mess ... ;-)
Sebastian Mendel wrote:
windkiel schrieb:
hi,
Marc Delisle wrote:
I would avoid adding another config parameter. I don't see why someone would not be happy to see his last server/db/table. Fear of having more cookies?
like letting the user choose lang,theme, and now even fontsize :) why not a litte checkbox "remember table" or "always save position" on main.php ?
you could easily add every single config option ... what a mess ... ;-)
-- Sebastian Mendel
good idea , but only everything what is useful for the user and is not server dependent. maybe on a "separate userconfig" page.
just my 2cent.
windkiel a écrit :
Sebastian Mendel wrote:
windkiel schrieb:
hi,
Marc Delisle wrote:
I would avoid adding another config parameter. I don't see why someone would not be happy to see his last server/db/table. Fear of having more cookies?
like letting the user choose lang,theme, and now even fontsize :) why not a litte checkbox "remember table" or "always save position" on main.php ?
you could easily add every single config option ... what a mess ... ;-)
-- Sebastian Mendel
good idea , but only everything what is useful for the user and is not server dependent. maybe on a "separate userconfig" page.
just my 2cent.
This is a new feature we have been discussing for many years: user preferences in pmadb. A separate page as you say would be important.
Marc
Marc Delisle wrote:
good idea , but only everything what is useful for the user and is not server dependent. maybe on a "separate userconfig" page.
This is a new feature we have been discussing for many years: user preferences in pmadb.
sorry for having read only half of the archive :)
an option is "cookies" as they are mandatory now.
--
Juergen
windkiel a écrit :
Marc Delisle wrote:
good idea , but only everything what is useful for the user and is not server dependent. maybe on a "separate userconfig" page.
This is a new feature we have been discussing for many years: user preferences in pmadb.
sorry for having read only half of the archive :)
an option is "cookies" as they are mandatory now.
--
Juergen
You are right, but I still think that we should not add too many cookies.
Besides, using pmadb would enable possible sysadmin interventions in terms of correcting user preferences in case of problems, implementing site-specific default for them, etc.
marc
an option is "cookies" as they are mandatory now.
You are right, but I still think that we should not add too many cookies.
i think of only one pma_cookie with "bitcoded options" as most parameters are boolean.
Besides, using pmadb would enable possible sysadmin interventions in terms of correcting user preferences in case of problems, implementing site-specific default for them, etc.
ok (if the isp has not too many users. BTW is there any info available, which isp serves how many users via pma ?)
Juergen Wind a écrit :
an option is "cookies" as they are mandatory now.
You are right, but I still think that we should not add too many cookies.
i think of only one pma_cookie with "bitcoded options" as most parameters are boolean.
Besides, using pmadb would enable possible sysadmin interventions in terms of correcting user preferences in case of problems, implementing site-specific default for them, etc.
ok (if the isp has not too many users. BTW is there any info available, which isp serves how many users via pma ?)
I can tell you at my school that there are 440 MySQL student accounts all using a single PMA installation.
PMA project has a bug entry for an installation having thousands of databases, probably just not one user :)
Marc
On Wed, 2 Aug 2006 07:40:05 -0700 (PDT) Juergen Wind jwind@ngi.de wrote:
i think of only one pma_cookie with "bitcoded options" as most parameters are boolean.
Am I the only one who uses too much computers to use cookie based settings?
Michal Čihař a écrit :
On Wed, 2 Aug 2006 07:40:05 -0700 (PDT) Juergen Wind jwind@ngi.de wrote:
i think of only one pma_cookie with "bitcoded options" as most parameters are boolean.
Am I the only one who uses too much computers to use cookie based settings?
Yes :) my FF profile (+ cookies) follows me on the network; OK it does not follow me at home, you win :)
Marc
Michal Čihař wrote:
On Wed, 2 Aug 2006 07:40:05 -0700 (PDT) Juergen Wind jwind@ngi.de wrote:
i think of only one pma_cookie with "bitcoded options" as most parameters are boolean.
Am I the only one who uses too much computers to use cookie based settings?
ok, that is a striking argument.
-
Juergen Wind -
Jürgen Wind
-
Marc Delisle -
Michal Čihař -
Sebastian Mendel -
windkiel