Mario Ivankovits wrote:
>
> Hi!
>> It so happens, I have been looking for this sort of a solution.
>>
> :-) Yea, I wonder why no one else have had a need for this too. It is a
> common use-case in our application.
>
>> In my case, I have a table with three columns, with three headings.
>>
> <snip />
>
> Do you mean something like this:
> A table with, say 10 columns. First column is a description and then 3x3
> columns with some values.
> As header you'd like to have:
> 1) 4 columns where the first column is a spacer for the description
> columns and then 3 columns where each spans 3 detail columns to describe
> the group of the spanned columns
> 2) another header with 10 column to describe exactly each column of the
> column
>
> I am working on a solution for this too as I need exactly this kind of
> thing too.
>
> Header 2 should be possible with the current solution, just use f:facet
> name=header on either the master table or detail table depending on if
> you'd like to have the header repeated each time.
> Header 1 requires some additional thoughts, but I think I'll introduce
> someting like a facet name="headerStamp" where you'll be able to define
> a header which a complete different set of columns.
> You just have to ensure that the number of columns (including all the
> callspan) match with all used tables.
>
> Ciao,
> Mario
>
>
>
Actually, i think i may have made it more confusing with my description, so
I'll simplify it.
You've got a three column table on an invoice. The header describes each
column:
LineItem Description UnitCost
Then below that you have, to make it simple, an Image that spans all three
columns.
Then below the image you have 5 transactions relating to the Image above it.
Then you get another image, followed by 3 transactions.
etc. etc. Each of these "groupings" are logical, but the data is described
by the heading for the overall table.
I believe this can be solved simply by nesting tables, but it would be
better to have the logical line items have the logical table headers applied
to the columns. Otherwise, the only other way I can think of solving this
is to use a rendered attribute on each "row". So depending upon the
contents of that row either render the image (or panel group, etc.) or a
usual data item.
The problem is, the data source doesn't lend as well to that structure. But
it's the only other option I can think of.
--
View this message in context:
http://www.nabble.com/embedded-table-tp15059361p15343801.html
Sent from the My Faces - Dev mailing list archive at Nabble.com.
