Hi!
My name is Thomas de Lima. I'm a computer engineering student from Brazil. I want to discuss more the idea of redesigning PMA, because I want to be sure I understood it correctly.
Design is not only about changing color or shapes in the user interface, but also about changing how the user interacts with the application, towards improving usability. So, the "User interface cleanup" project needs to be codeveloped with the AJAX team. Is that right?
I read an email from our indian colleague Anirvana Mishra, excited about ajaxifying PMA. But then Michal answered that he should pick one specific area to improve, cause there's too much functionality in PMA. Well, as a database manager, the PMA should be lightweight and "usable". For example, it takes a great deal of HTML download and clicks to find and edit someone's data in a huge personnel table. AJAX could solve both problems by opening a quickedit option on a browse table's row, which could be quickly found by an AJAX filter on top. So I think one of the "User interface cleanup" project goals should be study of which features need to be ajaxified or changed, or whatever, not about picking, before a deeper study, an area to improve.
For this purpose I wish to apply as an GSoCer to improve the PMA user interface, cause I frequently use it to manage my databases remotely. Of course PMA's usability now is excellent, as everything is intuitively put in place, but it feels soooo Web1.0, so static.
Thanks,
thomas.
Hi
Dne Tue, 23 Mar 2010 19:42:25 -0300 Thomas de Lima tfl3000@gmail.com napsal(a):
My name is Thomas de Lima. I'm a computer engineering student from Brazil. I want to discuss more the idea of redesigning PMA, because I want to be sure I understood it correctly.
Design is not only about changing color or shapes in the user interface, but also about changing how the user interacts with the application, towards improving usability. So, the "User interface cleanup" project needs to be codeveloped with the AJAX team. Is that right?
I read an email from our indian colleague Anirvana Mishra, excited about ajaxifying PMA. But then Michal answered that he should pick one specific area to improve, cause there's too much functionality in PMA.
Yes, you can not convert everything to AJAX during summer, so you need to choose some area.
Well, as a database manager, the PMA should be lightweight and "usable". For example, it takes a great deal of HTML download and clicks to find and edit someone's data in a huge personnel table. AJAX could solve both problems by opening a quickedit option on a browse table's row, which could be quickly found by an AJAX filter on top. So I think one of the "User interface cleanup" project goals should be study of which features need to be ajaxified or changed, or whatever, not about picking, before a deeper study, an area to improve.
Please note that this is summer of *code*, so we can not accept studies, but only coding projects for GSoC. Generally it would be helpful, but is out of scope for GSoC (as well as other things we currently can not do ourselves because of time limits).
For this purpose I wish to apply as an GSoCer to improve the PMA user interface, cause I frequently use it to manage my databases remotely. Of course PMA's usability now is excellent, as everything is intuitively put in place, but it feels soooo Web1.0, so static.
Well I would not tell that usability is excellent...
Thank your for the reply Michal.
You made yourself clear about *code* projects.
I can say I'm not an advanced PMA user, but everything I wanted to do in my database, I was able to find links easily, except user privileges vs. databases. I believe that's the basic concept of good usability. But you're right, excellent is not the best adjective for it.
thomas.
On Wed, Mar 24, 2010 at 7:06 PM, Michal Čihař michal@cihar.com wrote:
Hi
Dne Tue, 23 Mar 2010 19:42:25 -0300 Thomas de Lima tfl3000@gmail.com napsal(a):
My name is Thomas de Lima. I'm a computer engineering student from Brazil. I want to discuss more
the
idea of redesigning PMA, because I want to be sure I understood it correctly.
Design is not only about changing color or shapes in the user interface,
but
also about changing how the user interacts with the application, towards improving usability. So, the "User interface cleanup" project needs to be codeveloped with the AJAX team. Is that right?
I read an email from our indian colleague Anirvana Mishra, excited about ajaxifying PMA. But then Michal answered that he should pick one specific area to improve, cause there's too much functionality in PMA.
Yes, you can not convert everything to AJAX during summer, so you need to choose some area.
Well, as a database manager, the PMA should be lightweight and "usable". For
example,
it takes a great deal of HTML download and clicks to find and edit
someone's
data in a huge personnel table. AJAX could solve both problems by opening
a
quickedit option on a browse table's row, which could be quickly found by
an
AJAX filter on top. So I think one of the "User interface cleanup"
project
goals should be study of which features need to be ajaxified or changed,
or
whatever, not about picking, before a deeper study, an area to improve.
Please note that this is summer of *code*, so we can not accept studies, but only coding projects for GSoC. Generally it would be helpful, but is out of scope for GSoC (as well as other things we currently can not do ourselves because of time limits).
For this purpose I wish to apply as an GSoCer to improve the PMA user interface, cause I frequently use it to manage my databases remotely. Of course PMA's usability now is excellent, as everything is intuitively put
in
place, but it feels soooo Web1.0, so static.
Well I would not tell that usability is excellent...
-- Michal Čihař | http://cihar.com | http://blog.cihar.com
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
-
Michal Čihař -
Thomas de Lima