Re: [pilot-db-list] record display/layout hints

[<pef...@fe...>]

On Mon, 5 Nov 2001, Scott Wallace wrote:

> 	The advantage of this approach is that it doesn't require
> thinking about how the data will be displayed when you decide what should
> be in each record.

This is a cool idea, too, but is not exactly what I'm talking about (at
least I don't think so).  In your example you represented rows of a
table with four fields (name, number, size, quality), whereas I don't
necessarily have the same attributes for "Foo" as I have for "Bar".  To
change my example form, I might have:

Foo
  Attrib1 ___
  Attrib2 ___
  Attrib3 ___

Bar
  Attrib3 __
  Attrib4 __

It's ok not to display them as a table; I'm just trying to avoid having
to call them "Bar Attrib3" in the UI.

> 	There is an experimental plugin interface in db, that I have been
> looking at a bit lately.  It seems like it supports plugins for new list
> views.  I think this would be a great plugin capability, I would
> definately use it.

I haven't looked too heavily into this, but if it's possible to use it
and not disturb the main code, all the better.

-Peff