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:
than simply nesting a
table inside a table.
I look forward to more information on this. I'm a bit new to this, so
perhaps there is a better solution that I haven't found yet.
Thanks
Mike
--
View this message in context:
http://www.nabble.com/embedded-table-tp15059361p15340775.html
Sent from
this message in context:
http://www.nabble.com/embedded-table-tp15059361p15343801.html
Sent from the My Faces - Dev mailing list archive at Nabble.com.
Hi!
Sounds good - can you send your example again utilizing the
detailStamp approach if that fits?
So, not it is getting stressy again. I have a bad need for it now.
So, using the detailStamp approach it might look like:
t:datable var=group1 value=#{bean.data}
...
t:column colspan=10
Sounds good!
regards,
Martin
On 2/6/08, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
Sounds good - can you send your example again utilizing the
detailStamp approach if that fits?
So, not it is getting stressy again. I have a bad need for it now.
So, using the detailStamp approach it
Sounds good - can you send your example again utilizing the detailStamp
approach if that fits?
regards,
Martin
On Jan 24, 2008 2:54 PM, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
Shouldn't this work somewhat
similar to how the detailStamp in t:dataTable works now?
Yep, why not,
Hi Mario,
thanks - but that part I understood. I was just wondering about the
header part of your first example. I think I understood it now - you
have a header per row for the details in this row, and also allow each
main-row to have a header now?
regards,
Martin
On 1/24/08, Mario Ivankovits
Hi Martin,
I think I understood it now - you
have a header per row for the details in this row, and also allow each
main-row to have a header now?
I am not sure if this describes it exactly - it is not about having headers.
Or lets say, one header for three nested tables.
Have a look at
I don't get through to this server, sorry :(
regards,
Martin
On 1/24/08, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi Martin,
I think I understood it now - you
have a header per row for the details in this row, and also allow each
main-row to have a header now?
I am not sure if this
Martin Marinschek schrieb:
I don't get through to this server, sorry :(
Sorry, try this one: http://www.ops.co.at/~opsj/table.html
Ciao,
Mario
Hi Mario,
ok, now I completely understand the use-case - I still don't
understand the source-code, though. Shouldn't this work somewhat
similar to how the detailStamp in t:dataTable works now?
regards,
Martin
On 1/24/08, Mario Ivankovits [EMAIL PROTECTED] wrote:
Martin Marinschek schrieb:
I
Hi!
Shouldn't this work somewhat
similar to how the detailStamp in t:dataTable works now?
Yep, why not, should work that way too. The real magic will be the
embedded=true attribute to the datatable, and a different way how to
define the column header for the master table.
Ciao,
Mario
Hi!
One thing in JSF which constantly worries me is, that it is not easily
possible to create a more complicated table layout with
group/group/detail style.
What I mean is somthing like this:
Name Column1 Column2
Data1HeaderInformation1
Sub1HeaderInformation1
Name1 10 20
13 matches
Mail list logo