column selector / saving columns per query

afranke at ags.uni-sb.de afranke at ags.uni-sb.de
Thu Jan 27 06:54:15 UTC 2005


Quoting robzilla <rob2 at siklos.ca>:

> When you submit the query, it adds the 'columnlist' parameter to the
> buglist.cgi query string.  This specifies which columns should be displayed
> and in which order.

So to adopt the cmdline query tool, I could replace 

  wget -q -O ${outputfile} 
       --header="Cookie: COLUMNLIST=${COLUMNLIST-${defaultcolumnlist}}" 
       "${query}"

with

  wget -q -O ${outputfile}
       "${query}&columnlist=${COLUMNLIST-${defaultcolumnlist}}"

then?  That sounds fine to me.

> Implications:
> Since I got rid of the "Change Columns" page, there's no more support for
> "default columns" (saved in a cookie).  I didn't really see this as a
> problem, since the default columns are now saved with the default query (if
> you create one).

> For #1, I was thinking that we could give users who aren't logged in the
> option to save a default query, but it would be saved in a browser cookie
> instead of in the database.

Why not keep the cookie as the default, and have the columnlist URL parameter
override it, if present?  This way, you are backwards compatible, and avoid the
problem with not-logged-in users (AFAICS).

Cheers,
Andreas


-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/



More information about the developers mailing list