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

[Scott W. <swa...@my...>]

On Mon, 5 Nov 2001 pef...@fe... wrote:
>
> 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.


In this case, it sounds like your original idea will probably be best.  I
can't think of another elegant way to do this.  But what if you called
attribute 1 "[Foo] Attrib1" and attribute 4 "[Bar] Attrib4" would
attribute 3 be "[Foo,Bar] Attrib3" ?   It seems like this might get out of
hand if there were 5-10 or so classes.