Hi,
Previously, I have emailed some of my suggestions on User Interface Cleanup project. But after doing some research, I found that compared to User Interface Cleanup project, Browse-mode Improvement project will provide me to achieve the satisfied result and bring me higher chance of success. I have submitted a proposal on this project and also have added some ideas besides feature requests listed on the phpMyAdmin Ideas Page. The following is my suggestions for this project. Any comment and suggestion are welcome.
Synopsis:
This project is intended to improve the convenience of users when using phpMyAdmin, particularly when browsing tables. This can be achieved by adding the following features to phpMyAdmin: •Browse recently used tables •Remember the last way user sorted tables •Flexible table’s column width •Reorder table’s column using mouse during browsing •Show only selected columns •Integration of navigation bar •Edit only selected field •Grid view in the table edit page
Project Details:
•Browse recently used tables
Interface As discussed in the feature tracker , we can show recent tables that have been viewed by user as a drop-down list in the navigation frame. To keep things simple, the preferences will only show a checkbox “Display recent [#] tables” with the [#] default to 10 and can be set by user.
Storage Recently used tables can be stored in phpmyadmin database if it has been configured or in session variable if it is not.
•Remember the last way user sorted tables
Sorted column of each table can be stored (if the table is ever sorted) in phpmyadmin database or in session variable. When user browse a table, this value is read and added to sorting criteria of the SQL select query. This value must be synchronized with current database, i.e. when user drop a field, table, or database, the corresponding sorting value must be deleted.
Up to three points below are inspired by: http://www.flexigrid.info/ by Paulo P. Mariñas
•Flexible table’s column width & reorder table’s column using mouse during browsing
We can add functionality to adjust width and reorder table’s column by using jQuery. Again, table’s column order can be saved in phpmyadmin database or in session variable. An option “Remember tables’ columns order” can be added to the preference page.
•Show only selected columns
Currently, users have to run a SQL SELECT query or create a VIEW to display only certain columns from a table. This is sometimes cumbersome. We can improve this by adding a drop-down list in table’s header, giving checklist options to show only certain columns. This can be done by using jQuery.
•Integration of navigation bar
Current interface of navigation bar (prev, next) and “Show # row(s) starting …” can be integrated with the query-result table. So it will look like a part of the table and make user more convenient to use the navigation.
•Edit only selected field
One way to achieve this: modify current edit page to show only selected field. When user runs a select query, select some rows, and then click edit, some variables will be passed to edit page, so it hides fields that are not shown in the query result. Alternatively, an option to show/unhide all fields can be added.
•Grid view in the table edit page
Sometimes, users want to be able to edit only certain selected rows, but with a browse-like view. (Think of actions: browse -> select some rows -> With selected: edit)
I am thinking of improving the edit page, so user can have an option to edit table in a grid view instead of current edit view. The grid view will be simple, 2D grid, like in browse table. Each cell will be resizable text field, where user can change the value directly by typing in it.
I think this will be a complement of inline edit, since we can edit TEXT type value (which cannot be edited in inline edit).
Aris Feryanto a écrit :
• Grid view in the table edit page
Sometimes, users want to be able to edit only certain selected rows, but with a browse-like view. (Think of actions: browse -> select some rows -> With selected: edit)
I am thinking of improving the edit page, so user can have an option to edit table in a grid view instead of current edit view. The grid view will be simple, 2D grid, like in browse table. Each cell will be resizable text field, where user can change the value directly by typing in it.
I think this will be a complement of inline edit, since we can edit TEXT type value (which cannot be edited in inline edit).
I'm not sure that we should keep the 3.4 version "inline edit" in this case. Do you still see a value for this feature if "grid editing" is implemented?
Hi
Dne Mon, 28 Mar 2011 20:10:55 -0700 (PDT) Aris Feryanto aris_feryanto@yahoo.com napsal(a):
•Edit only selected field
One way to achieve this: modify current edit page to show only selected field. When user runs a select query, select some rows, and then click edit, some variables will be passed to edit page, so it hides fields that are not shown in the query result. Alternatively, an option to show/unhide all fields can be added.
•Grid view in the table edit page
Sometimes, users want to be able to edit only certain selected rows, but with a browse-like view. (Think of actions: browse -> select some rows -> With selected: edit)
I am thinking of improving the edit page, so user can have an option to edit table in a grid view instead of current edit view. The grid view will be simple, 2D grid, like in browse table. Each cell will be resizable text field, where user can change the value directly by typing in it.
I think this will be a complement of inline edit, since we can edit TEXT type value (which cannot be edited in inline edit).
Maybe these two could be somehow mixed together? Seeing bugs we had with inline edit, I'm afraid of adding yet another way for editing data, what would mean three versions of code doing basically same thing.
I think rather than adding yet another editing mode, it would be more useful to somehow consolidate what we have right now into shape that it is usable in more situations. This should probably start with defining how the data should be editable and which options it should provide (eg. using MySQL functions and so on).
Hi,
-----Original Message----- From: Marc Delisle [mailto:marc@infomarc.info] Sent: 29 Maret 2011 18:38 To: phpmyadmin-devel@lists.sourceforge.net Subject: Re: [Phpmyadmin-devel] GSoC 2011: Browse-mode Improvements ++
I'm not sure that we should keep the 3.4 version "inline edit" in this case. Do you still see a value for this feature if "grid editing" is implemented?
Actually, I was thinking of giving users some choices of ways to edit data. And they can choose the way that most suitable for them. Maybe there are some users that prefer to use inline edit. Moreover, phpMyAdmin developers and contributors surely have put some time and effort on implementing inline edit feature, so I wasn't planning to replace it. How do you think?
-- Marc Delisle http://infomarc.info
-----Original Message----- From: Michal Čihař [mailto:michal@cihar.com] Sent: 29 Maret 2011 20:18 To: phpmyadmin-devel@lists.sourceforge.net Subject: Re: [Phpmyadmin-devel] GSoC 2011: Browse-mode Improvements ++
Hi
Dne Mon, 28 Mar 2011 20:10:55 -0700 (PDT) Aris Feryanto aris_feryanto@yahoo.com napsal(a):
•Edit only selected field
One way to achieve this: modify current edit page to show only selected
field.
When user runs a select query, select some rows, and then click edit, some variables will be passed to edit page, so it hides fields that are not shown in the query result. Alternatively, an option to show/unhide all fields can be added.
•Grid view in the table edit page
Sometimes, users want to be able to edit only certain selected rows, but with a browse-like view. (Think of actions: browse -> select some rows -> With selected: edit)
I am thinking of improving the edit page, so user can have an option to edit table in a grid view instead of current edit view. The grid view will be simple, 2D grid, like in browse table. Each cell will be resizable text field, where user can change the value directly by typing in it.
I think this will be a complement of inline edit, since we can edit TEXT type value (which cannot be edited in inline edit).
Maybe these two could be somehow mixed together? Seeing bugs we had with inline edit, I'm afraid of adding yet another way for editing data, what would mean three versions of code doing basically same thing.
I think rather than adding yet another editing mode, it would be more useful to somehow consolidate what we have right now into shape that it is usable in more situations. This should probably start with defining how the data should be editable and which options it should provide (eg. using MySQL functions and so on).
Same as above, I thought that the grid editing will be just an option for users. And about current basic edit mode, I think we should keep it for compatibility when javascript is not available or disabled (as I am thinking of implementing the grid editing using javascript).
I have take a look at current phpMyAdmin edit page and also a tool "Toad for MySQL Freeware". Basically, user can enter data by typing the value directly, or choose from a MySQL function.
For the grid editing, we can implement a drop-down for every cell in the grid, just like in "Toad for MySQL Freeware" [1]. In the drop-down, depends to the data type for selected cell, user will be given option whether to type-in data directly, use MySQL function, use datetime picker, etc.
To differ MySQL function from usual data, we can use spreadsheet-like syntax, i.e. MySQL function appears with "=" sign in front of the expression.
That is my suggestions. How do you think?
-- Michal Čihař | http://cihar.com | http://blog.cihar.com
----- Aris Feryanto
Hi,
Sorry, I forgot the link in previous email.
-----Original Message----- From: Marc Delisle [mailto:marc@infomarc.info] Sent: 29 Maret 2011 18:38 To: phpmyadmin-devel@lists.sourceforge.net Subject: Re: [Phpmyadmin-devel] GSoC 2011: Browse-mode Improvements ++
I'm not sure that we should keep the 3.4 version "inline edit" in this case.
Do
you still see a value for this feature if "grid editing" is implemented?
Actually, I was thinking of giving users some choices of ways to edit data. And they can choose the way that most suitable for them. Maybe there are some users that prefer to use inline edit. Moreover, phpMyAdmin developers and contributors surely have put some time and effort on implementing inline edit feature, so I wasn't planning to replace it. How do you think?
-- Marc Delisle http://infomarc.info
-----Original Message----- From: Michal Čihař [mailto:michal@cihar.com] Sent: 29 Maret 2011 20:18 To: phpmyadmin-devel@lists.sourceforge.net Subject: Re: [Phpmyadmin-devel] GSoC 2011: Browse-mode Improvements ++
Hi
Dne Mon, 28 Mar 2011 20:10:55 -0700 (PDT) Aris Feryanto aris_feryanto@yahoo.com napsal(a):
•Edit only selected field
One way to achieve this: modify current edit page to show only selected
field.
When user runs a select query, select some rows, and then click edit, some variables will be passed to edit page, so it hides fields that are not shown in the query result. Alternatively, an option to show/unhide all fields can be added.
•Grid view in the table edit page
Sometimes, users want to be able to edit only certain selected rows, but with a browse-like view. (Think of actions: browse -> select some rows -> With selected: edit)
I am thinking of improving the edit page, so user can have an option to edit table in a grid view instead of current edit view. The grid view will be simple, 2D grid, like in browse table. Each cell will be resizable text field, where user can change the value directly by typing in
it.
I think this will be a complement of inline edit, since we can edit TEXT type value (which cannot be edited in inline edit).
Maybe these two could be somehow mixed together? Seeing bugs we had with inline edit, I'm afraid of adding yet another way for editing data, what would mean three versions of code doing basically same thing.
I think rather than adding yet another editing mode, it would be more useful to somehow consolidate what we have right now into shape that it is usable in more situations. This should probably start with defining how the data should be editable and which options it should provide (eg. using MySQL functions and so on).
Same as above, I thought that the grid editing will be just an option for users. And about current basic edit mode, I think we should keep it for compatibility when javascript is not available or disabled (as I am thinking of implementing the grid editing using javascript).
I have take a look at current phpMyAdmin edit page and also a tool "Toad for MySQL Freeware". Basically, user can enter data by typing the value directly, or choose from a MySQL function.
For the grid editing, we can implement a drop-down for every cell in the grid, just like in "Toad for MySQL Freeware" [1]. In the drop-down, depends to the data type for selected cell, user will be given option whether to type-in data directly, use MySQL function, use datetime picker, etc.
To differ MySQL function from usual data, we can use spreadsheet-like syntax, i.e. MySQL function appears with "=" sign in front of the expression.
That is my suggestions. How do you think?
[1] http://s.itb.ac.id/home/aris_feryanto@students.itb.ac.id/Briefcase/GSoC/capt...
-- Michal Čihař | http://cihar.com | http://blog.cihar.com
----- Aris Feryanto
Hi all,
About the grid editing mode, should we keep this as an option for user? I have submitted a proposal on GSoC website and hoping for some comments.
-- Aris Feryanto
________________________________ From: Aris Feryanto aris_feryanto@yahoo.com To: phpmyadmin-devel@lists.sourceforge.net Sent: Rab, 30 Maret, 2011 00:30:40 Subject: Re: [Phpmyadmin-devel] GSoC 2011: Browse-mode Improvements ++
Hi,
Sorry, I forgot the link in previous email.
-----Original Message----- From: Marc Delisle [mailto:marc@infomarc.info] Sent: 29 Maret 2011 18:38 To: phpmyadmin-devel@lists.sourceforge.net Subject: Re: [Phpmyadmin-devel] GSoC 2011: Browse-mode Improvements ++
I'm not sure that we should keep the 3.4 version "inline edit" in this case.
Do
you still see a value for this feature if "grid editing" is implemented?
Actually, I was thinking of giving users some choices of ways to edit data. And they can choose the way that most suitable for them. Maybe there are some users that prefer to use inline edit. Moreover, phpMyAdmin developers and contributors surely have put some time and effort on implementing inline edit feature, so I wasn't planning to replace it. How do you think?
-- Marc Delisle http://infomarc.info
-----Original Message----- From: Michal Čihař [mailto:michal@cihar.com] Sent: 29 Maret 2011 20:18 To: phpmyadmin-devel@lists.sourceforge.net Subject: Re: [Phpmyadmin-devel] GSoC 2011: Browse-mode Improvements ++
Hi
Dne Mon, 28 Mar 2011 20:10:55 -0700 (PDT) Aris Feryanto aris_feryanto@yahoo.com napsal(a):
•Edit only selected field
One way to achieve this: modify current edit page to show only selected
field.
When user runs a select query, select some rows, and then click edit, some variables will be passed to edit page, so it hides fields that are not shown in the query result. Alternatively, an option to show/unhide all fields can be added.
•Grid view in the table edit page
Sometimes, users want to be able to edit only certain selected rows, but with a browse-like view. (Think of actions: browse -> select some rows -> With selected: edit)
I am thinking of improving the edit page, so user can have an option to edit table in a grid view instead of current edit view. The grid view will be simple, 2D grid, like in browse table. Each cell will be resizable text field, where user can change the value directly by typing in
it.
I think this will be a complement of inline edit, since we can edit TEXT type value (which cannot be edited in inline edit).
Maybe these two could be somehow mixed together? Seeing bugs we had with inline edit, I'm afraid of adding yet another way for editing data, what would mean three versions of code doing basically same thing.
I think rather than adding yet another editing mode, it would be more useful to somehow consolidate what we have right now into shape that it is usable in more situations. This should probably start with defining how the data should be editable and which options it should provide (eg. using MySQL functions and so on).
Same as above, I thought that the grid editing will be just an option for users. And about current basic edit mode, I think we should keep it for compatibility when javascript is not available or disabled (as I am thinking of implementing the grid editing using javascript).
I have take a look at current phpMyAdmin edit page and also a tool "Toad for MySQL Freeware". Basically, user can enter data by typing the value directly, or choose from a MySQL function.
For the grid editing, we can implement a drop-down for every cell in the grid, just like in "Toad for MySQL Freeware" [1]. In the drop-down, depends to the data type for selected cell, user will be given option whether to type-in data directly, use MySQL function, use datetime picker, etc.
To differ MySQL function from usual data, we can use spreadsheet-like syntax, i.e. MySQL function appears with "=" sign in front of the expression.
That is my suggestions. How do you think?
[1] http://s.itb.ac.id/home/aris_feryanto@students.itb.ac.id/Briefcase/GSoC/capt...
-- Michal Čihař | http://cihar.com | http://blog.cihar.com
----- Aris Feryanto
-
Aris Feryanto -
Marc Delisle -
Michal Čihař