Hello everybody!
My name is Richard Dvorsky. I`m from Slovakia. I have started to use
phpMyAdmin five years ago.
I have been doing some research for user interface cleanup. And I made list
of my user interface improvements.
Of course, is no complete and any suggestions are vary welcome.
Look at list.
-
*Server - Privileges**: * Solution is the same as it is written in points
for *Server - DB – Privilges*. But I add icon to delete user to place
where is “Check All/Uncheck All”. Nearby this icon, will be hidden option to
delete database ,with same name who has user.
-
*Server - Synchronize: *There needs only hide the “Port” and “Socket”,
because they are seldom used.
-
*Server - DB - Structure**: *This phpMyAdmin tool is for common user a
little bit complicated. Probably the best would be to hide “Structure”,
“Search” and “Insert”. Moreover, as “Browse”, “Empty” and “Drop” will
remain. If the user wants other functions, he only clicks to icon. Other
stuff like “Rows”, “Type”, “Collation”, “Size”, ”Overhead” will remain
too.
-
*Server - DB - Search**: *The main goal of this selection is to simplify
searching. There will be one search window like in google. It will be
searching with LIKE %value% command in all tables with columns. If the user
wants to set up search criteria, he only clicks to custom search.
-
*Server - DB - Operations - Copy database to: *Display just only simple
window where user can write database name. Other options will by hidden.
-
*Server - DB - Privileges - Edit Privileges: *Make only simple list of
privileges tools.
-
*Server - DB - Privileges - Edit Privileges - Global Privileges: *In this
section is also best to do list of options too. User chooses only this
options what he needs to change. Items of the list will be: “Data”,
“Structure”, “Administration”, “Resource Limits”.
-
*Server - DB - Privileges - Edit Privileges - Change Password: *There
needs only hide the “Password hashing” and “Generate password”, because
common user doesn`t need it. Other options are OK.
-
*Server - DB - Privileges - Edit Privileges - Change Login informations:
*Make list with “Login informations”, “Create a new user with...”. The
user opens only this, what he really needs to edit.
-
*Server - DB - Table - Browse: *In this section is quite a lot of work.
-
At first would by to simplify “Show” options. There is so many useless
functions, which looks disorganized and common user doesn`t need
to set it
up. Other stuff like “query range”, “horizontal or vertical mod”,
“repeating headers”, “sorting” will be hidden. Only “page
arrows” and “page
list” will be shown.
-
I`d like to hide “Edit” and “Copy” in query displaying, because is not
used commonly by user.
-
*Server - DB - Table - Structure: *Table structure GUI is pretty good. I
would hide only “Add column to table”. Then make “Print view” and
“Propose table structure” more visible.
- *Server - DB - Table – Search: *I would like to make searching more
simpler. It will be searching with LIKE %value% command in all columns in
table. If the user wants to set up search criteria, he only clicks to custom
search.
-
*Server - DB - Table - Insert: *I would hide “Ignore” part, because there
is not needed for common user. And I want to make more simpler part Insert
as new row.
-
*Server - DB - Table - Operations: *The best way is to create a list of
options provided and user chooses what he really wants.
- *Server - DB - Table - Operations - Copy table to: *Display just only
simple window where user can write database name. Other options will by
hidden*. *
Thanks for reading :-)
R.D.
Hi everyone,
My name is Benoit Dumesnil,
I am actually studying computer science at the university of Rouen (France) and I’m very interested by the “User interface cleanup“ idea.
I have begun to use PMA some years ago for my own needs but I’m currently using it for my courses so this would be a huge opportunity to be accepted into GSoC and to be able to help.
So for the interface, taking account of the requests, I tought that we need to create 2 different modes :
A basic mode : The user can only import/export databases ( or tables ) and modify the content of tables.
This means too to simplify the interface and hide some complicated functions for beginners.
For basic user we could also add tooltips to explain elements when the user put the cursor on them.
An admin mode : The user can see everything but he can also hide the parts that he doesn’t want to see and keep an eye only on important data.
The user can set the things he want to keep into the settings menu.
I have also thought that in the main menu the user could modify the size, move or add menus like some kind of widgets.
Of course suggestions are welcome.
Best regards,
Benoit Dumesnil
Hi,
by default, the ShowSQL directive is true, which makes the generated SQL
appear on top for almost every action. This fulfills many needs:
- people teaching SQL
- user who wants to verify what phpMyAdmin did in the backend
However with Inline edit, we no longer see this generated SQL and I'm
wondering if something should be done about this.
--
Marc Delisle
http://infomarc.info
Hello fellow developers,
I am a pre-graduate Student at the Technical University of Vienna /
Austria and I would enjoy to join the GSoC 2011 Program.
PHPMyAdmin has become my tool of the trade for managing my website
databases. I've been using it for over a decade and grew to love
working with it.
I sometimes missed a feature to see how much load the MySQL Server
receives. The phpmyadmin status page unfortunately only shows current
and total values. So my proposal is:
- Instead of using anchor links put all runtime information groups
into jquery-tabs where users can click through.
- Using the recently added pchart libarary, implement a bunch of
charts to give a graphical history of the
- amount of queries
- traffic load
- amount of concurrent connections
- In the process adjust the current chart color to fit with the
currently selected theme (That snake-green over the gray color of
pmahomme looks rather odd ;).
- Improve look & feel of the status page where applicable
Unfortunately making such charts would probably require the user to
install some sort of cronjob and we have to store a history of records
to make the charts. So it either would need to pollute the mysql
database with a table or we store it in a text file.
Despite those 2 configuration annoyances it would be a useful addition
nonetheless, I think. After all, we can just hide everything behind a
small "Enable server load recording"-Link where you can set up the
recording.
I am a great fan of building statistics and speeding up websites using
AJAX so I'd love to hear your Ideas to my proposal or anything that is
related to it. I could need a few more tasks :-)
I have seen that you require GSoC applicants to be developers of
phpmyadmin, so I will go and check if there's anything in the tracker
that I can fix or build within the next days.
P.S.: Your changelog
(http://www.phpmyadmin.net/documentation/changelog.php) linked from
(http://www.phpmyadmin.net/home_page/docs.php) seems to be broken.
Thanks for your time!
Hi All,
Im Dilantha Silva,a final year undergraduate student of the Faculty of
Information Technology, University of Moratuwa, Sri Lanka. Im interested in
partcipiating for Gsoc 2011 under phpmyadmin.I have participated for Gsoc
2010 under sahana software foundation and successfully completed the
project[1]. I have been using phpmyadmin for quite long time and this idea
came to my mind some times back.
Query window act as a editor to create sql queries in phpmyadmin. It provide
some basic functions to make things easy (showing the columns etc.) when
writing a query. But i think we can add some features to enhance it and make
it more user friendly.For example Key words like "SELECT", "FROM",
"WHERE",etc will be used in most of the queries typed in the query window.
So for that we can give auto completes and suggetions. When user type "S"
and press Ctrl + Space (or something similar) we can show all the key words
starting by "S" and allow user to select the particular one. Also when we
are selecting a particular table in a database, once the user type
"db_name." and press Ctrl + Space we can show all the tables in that
particular db. Similarly when selecting a column in a table we can use this
method. We can list down the available columns and allow users to select
among them. specially when there are columns which has longer names this
method will save lot of time and also avoid errors.
These are just some of the improvements that we can do.Im sure there are
plenty of things left. So i would love to hear your comments and suggestions
regarding this project. Thanks.
[1] http://wiki.sahanafoundation.org/doku.php/foundation:gsoc_silva
--
Regards,
Dilantha Silva,
http://twitter.com/dilanthasilva | http://www.linkedin.com/in/dilanthasilva|https://launchpad.net/~dilantha
Hello everyone,
My name is Rouslan and I'm a student from Cork, Ireland. I'm currently
studying at the Cork Institute of Technology for an honours degree in
Software Development. I have been a user of phpmyadmin for about three
years now. So far your tool has been an invaluable for me during the
development of web applications.
So I guess that I'm just dropping by to introduce myself a little and I
would also like to express my interest in coding for your project this
summer as part of the GSOC program. I'm particularly intrigued by the
"Support for procedures" gsoc idea from your wiki page.
I have already downloaded the latest source code from the git repository
and I'm now poking around to see how things work. I have also already
created a fork at repo.or.cz and had a quick go at fixing a bite-sized
bug from your tracker.
I will now get stuck in and get up to speed with git (I've only been
using mercurial so far), explore your code base a bit more and hopefully
attempt to fix one or two other bugs.
Well, I guess I don't have much else to say at the moment. Talk soon.
Take care,
Rouslan
( my ohloh profile: http://www.ohloh.net/accounts/Roccivic )
I have been using phpmyadmin, since I have been using MySQL. I have always
been tweaking and editing it for personalizations and customizations. One
thing I think it is badly lacking is *MVC (Model - View - Controller)
Architecture.*
Better than porting it OOP, it is better to convert into an MVC
Architecture. The reasons why I support MVC Architecture is :
1. Scalabality
2. Code Reuse
3. Integration of various libraries
4. Same application logic can generate various views, i.e., it can be
used to generate UI for mobile or for touch-enabled devices
Also, one optional thing to be considered is, while designing the models, it
is* important to consider the interactions between the various
components*and plan according. The phpmyadmin code is written in a
good fashion, but it
can be better.
Also,* a good abstraction layer for various other DBMS,* and hence can be
extended to other RDBMS.
phpmyadmin, by far, the best database tool I have ever used, I think can
evolve into a better and a robust tool for DBMS.
*Summary : *
Rather than concentrating into converting the codebase into OOP, it should
rather be organized into and *MVC architecture.*
There should be a* considerable amount of planning before designing the
system*, considering the interactions amongst various models.
*A database abstraction layer* can be maintained, in order to extend its
capabilities to other DBMS.
Hi all,
My name is Aris Feryanto (male, final year student @ Institut Teknologi
Bandung, Indonesia, major Computer Science). I would like to participate
in GSoC as a student. I am interested in the "user interface cleanup"
project idea.
In the ideas page there are two feature requests [2][3]. I have looked
at these requests and they are about "disabling some tabs for particular
users".
I think we can implement this feature by adding a tab "Users" under
"Setting" where the administrator can configure an user "role". The user
account used here is linked to mysql user database.
Role can be admin, basic, or something else defined by the
administrator. For each role, the administrator can configure which tabs
are shown to the user (maybe we can also add other configuration that
specific for an user).
This is my suggestion for the project. I do expect comments and
suggestions from the phpmyadmin developers.
I am currently trying to familiarize myself with phpmyadmin code from
current git. Now, I am working on fixing a bug "User prefs and Iconic
settings" (ID 3216140).
Regards,
Aris Feryanto
Institut Teknologi Bandung
My name is Fábio, I'm a student of Computer Science at Federal University of
Paraíba, Brazil, and an enthusiastic of GSoC. As I've working with
phpMyAdmin in the last two years, I'd love to contribute and to improve this
excellent tool. I'm interested to implement some object oriented
improvements on some existing module/functionality, like import or export a
database, CRUD operations, etc.
I'm studying the phpMyAdmin code base (and documentation), looking for some
bit of code which needs to be refactored or could be encapsulated into a
class. Maintaining a OOP code is easier and we can make it much more
re-usable and self-independent, mainly when the code is re-utilized, like
various phpMyAdmin functions, so any improvements are welcome, of course,
with a good test covering and an excellent analysis of the consequences into
the code.
Although I've never had posted/committed any bug solution, I'd like to be
closer to the project and this opportunity came right on time, since I
worked the last two year entirely with php/mysql (I finished a social
network for tourists which is about to be launched soon) and it gave me an
excellent experience (since I worked with a lot of design patterns,
discovering and correcting pitfalls and traps in PHP language, and good part
of the development driven by tests). So, I hope I can mix my experience with
an opportunity to increase a tool which I constantly use, beside the chance
to be in touch with the leaders and the team of this development. I know is
necessary a 40 hours per week, along the 12 weeks, so I'm wondering, maybe I
can use the free time between the deadline to rank the students and the real
coding beginning, in order to gain some time to give the project some tests
(it's obvious we'll need some unit tests to keep the system saved), even
start the coding (since I'll still having some classes during the first
month, unfortunately), and discuss the idea so we can enhance the
improvement :)
Is there anything else I can do beside exploring the code? How can I discuss
the focus of the implementation? I just can't wait to work with it and
finally make my real contribution. Thank you all in advance.
Best Regards,
Fábio Cruz B. de Albuquerque