On Fri, Jul 11, 2008 at 2:13 PM, Jim Hunter <[EMAIL PROTECTED]> wrote:
> But are you able to change the column models properties? I would need to
> have it associate with a new set of columns for the new use. I thought that
> was not possible. I never know from one instance of a table to the next what
> column information it will need.
Looking at the code, it seems that you'd not be able to change the *number*
of columns, but could change the attributes of existing columns (e.g. their
width). If your user interface doesn't make the column visibility menu
available to your users, I suppose you could create a column model with
whatever maximum number of columns you might ever need and then make the
unused columns invisible as you prepare to use an instance of the table
pulled from the pool.
Derrell
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
