PROTECTED]
Sent: Tuesday, April 12, 2005 10:35 PM
To: MyFaces Development
Subject: Re: Proposed improvement to x:dataTable
Neal,
Please report back here about what you learn and how you make out. We
are in the process of investigating this too.
sean
On Apr 12, 2005 4:31 PM, Neal
]
Sent: Tuesday, April 12, 2005 3:29 AM
To: MyFaces Development
Subject: RE: Proposed improvement to x:dataTable
Hi Sean,
Take a look at the new component x:columns and the example crosstable.
I think it is exactly what you need to create a datatable with variable columns.
I've allready posted
Hi Neal,
-Original Message-
From: Neal Haggard [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 12, 2005 3:20 PM
To: MyFaces Development
Subject: RE: Proposed improvement to x:dataTable
Mathias,
While your x:columns is very nice, it does not answer
Sean's request to have
: Tuesday, April 12, 2005 3:20 PM
To: MyFaces Development
Subject: RE: Proposed improvement to x:dataTable
Mathias,
While your x:columns is very nice, it does not answer
Sean's request to have something where the columns can be
independently formatted. All of your columns
Development
Subject: RE: Proposed improvement to x:dataTable
Hi Neal,
-Original Message-
From: Neal Haggard [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 12, 2005 3:20 PM
To: MyFaces Development
Subject: RE: Proposed improvement to x:dataTable
Mathias,
While your x:columns is very
with that and see how it works for us. Thanks for the idea.
Neal
-Original Message-
From: Broekelmann, Mathias [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 12, 2005 9:55 AM
To: MyFaces Development
Subject: RE: Proposed improvement to x:dataTable
Hi Neal,
-Original Message
What is wrong with doing a component-binding and setting this stuff up in your bean?
We've had a few cases where the datatable's columns cannot be defined inside the JSP and this has worked just fine for us.
On Apr 11, 2005 1:06 PM, Sean Schofield [EMAIL PROTECTED] wrote:
We're trying to use
How would this work exactly? Would the backing bean add column
children to the data table as needed? I suppose that could work but
it seems like a roundabout way of doing it. Plus what if I want to
render the data differently in the columns depending on their type
(similar to tree2?) That
Yes, we basically just did it programmatically inside our bean. I agree with you that rendering rules should be separate from the application logic, but that doesn't mean it HAS to reside in the JSP.
Could you maybe give a JSP example?
On Apr 11, 2005 1:28 PM, Sean Schofield [EMAIL PROTECTED]
But I thought that you were proposing changing the component (and I'm guessing the Tag as well), and I'm just wondering if you could provide an example of your changes in a JSP form.
On Apr 11, 2005 1:48 PM, Sean Schofield [EMAIL PROTECTED] wrote:
I didn't say that that this functionality *had* to
We are trying to do something like this in Shale. The proposed plugin is
called Clay. The basic idea is to allow defining a subtree of components using
something other than the JSP tags.
We currently have three subtree composition options:
1) Define in XML only
2) Define at runtime with a
I'll try and get an example to you shortly. BTW I thought of an
additional drawback to the approach you suggested. Suppose you have
fifteen columns that you need to render but you need to render them
the same for each column.
This is the opposite of my earlier example where you need to
Gary,
I've seen this proposal on the struts-dev list. I haven't really had
time to delve into it yet but in this case it seems to be solving the
wrong tree. While it might be appropriate to programatically add
components to the tree in some cases, it does not make sense in this
case.
I have
13 matches
Mail list logo
