W dniu 23 marca 2010 01:22 użytkownik Marc Delisle marc@infomarc.info napisał:
There are surely other settings that can benefit from this. Some are in config.default.php, some are maybe only on the interface, I'm not sure.
Yes, this will require some information gathering on this group, and maybe some questions about this on phpMyAdmin website. It can be researched while implementing functionality current config options.
The last time we discussed about this feature, we were wondering if there should be a page regrouping user preferences, or if they should be settable individually on the related page (for example while browsing, choosing the number of rows you usually want there), or both?
I believe that everything should be on special preferences page so we do not clutter the interface and keep interface behavior consistent.
There was also the question of the place where they should be stored during your work session in phpMyAdmin (avoid loading them on each click!)
$_SESSION is the best place. Settings would be loaded once and kept in an easily available place. Cookies are out of the question as it would require too much data to be sent on each request.
We need to keep these features also in the "normal" config mechanisms ( /setup, config.default.php, config.inc.php) because the pmadb is optional and has to remain optional.
My idea is to put all user-changeable options to config.default.php, then it can be implemented as simply overwriting current config with user values. Allowed keys would be stored in $cfg array, making the list easy to modify if needed. That would also allow setup script to show which config values can be changed by end users.