Re: Set component parameters from page class

2007-07-02 Thread Martin Dietze
On Mon, July 02, 2007, Francois Armand wrote: >@Component(parameters="disabled=prop:isdisabled") >private TextField textField; > >public boolean getIsdisabled() { >return disabled; >} >@SetupRender >void setup() { > if(should de disabled) { >disable

Re: Set component parameters from page class

2007-07-02 Thread Francois Armand
Martin Dietze wrote: Yes, this is how I found it in the documentation. However I'd like to be able to do something like: | @Component(id="myInput") | private TextField _myInput; [...] | _myInput.setDisabled(true); You can use parameter expansion in Java code : 8<---

Re: Set component parameters from page class

2007-07-02 Thread Martin Dietze
On Mon, July 02, 2007, Francois Armand wrote: > I'm not sure I have correctly understood your concern, so excuse me if I > answer to something else ;) > When you have a component with parameter, you have two way to specify it > the actual parameter value : > - in the template, with "paramname=bi

Re: Set component parameters from page class

2007-07-02 Thread Martin Dietze
On Mon, July 02, 2007, Massimo Lusetti wrote: > > I'd like to set some component paramameters ("disabled" for > >inputs) from within my page classes. As far as I've seen so far > >the usual way to do this would be to put a "name=${prop:value}" > >attribute into my template. Can this also be done b

Re: Set component parameters from page class

2007-07-02 Thread Francois Armand
Martin Dietze wrote: Hi, I'd like to set some component paramameters ("disabled" for inputs) from within my page classes. As far as I've seen so far the usual way to do this would be to put a "name=${prop:value}" attribute into my template. Can this also be done by using a simple setter in my J

Re: Set component parameters from page class

2007-07-02 Thread Massimo Lusetti
On 7/2/07, Martin Dietze <[EMAIL PROTECTED]> wrote: Hi, I'd like to set some component paramameters ("disabled" for inputs) from within my page classes. As far as I've seen so far the usual way to do this would be to put a "name=${prop:value}" attribute into my template. Can this also be done