[Phpmyadmin-devel] GSoG 2011: Reg Zoom-search idea

[Ammar Yasir]

On Mon, Apr 11, 2011 at 10:19 PM, Marc Delisle <marc at infomarc.info> wrote:

> Ammar Yasir a écrit :
> >
> >
> > On Sun, Mar 20, 2011 at 3:05 AM, Ammar Yasir <ammaryasir.88 at gmail.com
> > <mailto:ammaryasir.88 at gmail.com>> wrote:
> >
> >
> >
> >     On Sun, Mar 20, 2011 at 2:00 AM, Marc Delisle <marc at infomarc.info
> >     <mailto:marc at infomarc.info>> wrote:
> >
> >         Le 2011-03-19 15:13, Ammar Yasir a écrit :
> >          > Sir,
> >          >
> >          > I looked at the table search page. One problem I find is that
> >         a form such as
> >          > table search page consists of all the columns. I think in
> >         general a user is
> >          > interested in at most 2-3 criteria for searching at once. If
> >         number of
> >          > columns are more(in a table eg. users table in mysql
> >         database), the search
> >          > table form will contain lot of irrelevant fields(to his
> >         query). Can the page
> >          > be something like it asks the user to select the column
> >         first, then its
> >          > detail and then again a column if he wants to build the query
> >         further?
> >
> >         (Please do not top-post, conversations are difficult to follow).
> >
> >         I was referring to the Table Search page because we'll have to
> avoid
> >         duplicating the same functionality on many pages.
> >
> >         You are right, the table Search page displays all the columns in
> >         "query
> >         by example" but in its Options hidden panel you can choose the
> >         columns
> >         that will be displayed. I think that this behavior could be
> >         improved by
> >         adding a way to quickly hide or show which columns are to receive
> a
> >         search criterion.
> >
> >     I think that we can reduce some fields by combining elements from
> >     the table search page and those from the options hidden pane. The
> >     table search form provides appropriate operations for each column
> >     and in options panel we can select columns but it just provides a
> >     textbox to enter the body of the WHERE clause.
> >
> >     As in this case we are only interested in selecting one of the
> >     columns, initially we can just have a list of columns and then when
> >     a user clicks on one of the columns, the appropriate operations
> >     available for that column appear. This reduces some of the fields on
> >     the screen.
> >
> >         Try to avoid a behavior that would be too sequential.
> >
> >
> >     and this will not be very sequential also. For example see:
> >     Initially -> http://web.iiit.ac.in/~yasir/IMG1.jpg
> >     <http://web.iiit.ac.in/%7Eyasir/IMG1.jpg> , Selecting File_priv
> >     ->http://web.iiit.ac.in/~yasir/IMG2.jpg
> >     <http://web.iiit.ac.in/%7Eyasir/IMG2.jpg>
> >
> > Hi,
> > Regarding the table search page, should I try doing the changes ( see
> > images above) i.e. changing from a query-by-example to displaying fields
> > on user click (on a column). Maybe they could turn out useful if we
> test??
>
> Yes but this table is a special case with a lot of ENUMs. I don't see in
> your screenshot where a user would give an example value, let's say for
> "host".
>
> I suggest you use the "sakila" example database which contains more
> real-world tables.
>
> Hi,

I just submitted a patch for this. Its just a basic idea of what I though
would help in that interface. It might not look good on applying, so if you
may please give comments to improve.


> --
> Marc Delisle
> http://infomarc.info
>
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> Phpmyadmin-devel mailing list
> Phpmyadmin-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phpmyadmin.net/pipermail/developers/attachments/20110415/a518171d/attachment.html>