On Thu, Apr 08, 2004 at 07:55:44AM -0400, Vadim Gritsenko wrote:
> Tim Larson wrote:
> >We need to be able to specify the hidden state and the
> >selection of {both|output|input|neither} both statically in
>
> +1
>
> >the widget definitions and dynamically via flowscript, Java,
> >binding, and ev
Tim Larson wrote:
We need to be able to specify the hidden state and the
selection of {both|output|input|neither} both statically in
+1
the widget definitions and dynamically via flowscript, Java,
binding, and event handling, but not via the view, of course.
I don't see a necessity to prov
Bruno Dumon wrote:
On Tue, 2004-04-06 at 18:19, Christopher Oliver wrote:
Bruno Dumon wrote:
For the generator-approach, a good starting point would be to commit it
to CVS and add or change an example to show how it works.
I've done this for the V2 flowscript sample.
Coo
On Tue, 2004-04-06 at 18:19, Christopher Oliver wrote:
> Bruno Dumon wrote:
>
> >On Mon, 2004-04-05 at 13:28, Sylvain Wallez wrote:
> >
> >
> >
> >>So, I propose the following changes to Cocoon forms:
> >>- add a state to widgets (enabled/disabled/hidden).
> >>- move to a generator approach.
> >
Bruno Dumon wrote:
On Mon, 2004-04-05 at 13:28, Sylvain Wallez wrote:
So, I propose the following changes to Cocoon forms:
- add a state to widgets (enabled/disabled/hidden).
- move to a generator approach.
WDYT?
For the generator-approach, a good starting point would be to commit it
to C
On Mon, 2004-04-05 at 13:28, Sylvain Wallez wrote:
>
> So, I propose the following changes to Cocoon forms:
> - add a state to widgets (enabled/disabled/hidden).
> - move to a generator approach.
>
> WDYT?
For the generator-approach, a good starting point would be to commit it
to CVS and add or
Sylvain Wallez wrote:
Vadim Gritsenko wrote:
Also, what do you think about something to allow generation of
s? Currently, does not produce any label at all...
Actually, that's not a generator/transformer problem, but something
wrong with . It should produce a tag
containing what it produce
On Mon, Apr 05, 2004 at 01:28:42PM +0200, Sylvain Wallez wrote:
> So, I propose the following changes to Cocoon forms:
> - add a state to widgets (enabled/disabled/hidden).
> - move to a generator approach.
No official comment on the generator approach since I have not
yet tried it, but it looks p
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Now, as I mentioned already [1], I started using the generator
approach
to form templates, using the implementation of "wt:" statements using
JXMacro provided by Chris [2]. And this approach is very power
Sylvain Wallez wrote:
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Now, as I mentioned already [1], I started using the generator approach
to form templates, using the implementation of "wt:" statements using
JXMacro provided by Chris [2]. And this approach is very powerful,
as it
allows comple
Antonio Gallardo wrote:
Upayavira dijo:
Leon Widdershoven wrote:
- move to a generator approach.
Do you mean generator-only approach? I think that would limit the
options of the users quite a bit (and I am one of those). I actually
like the pipeline
approach so that you can build
Upayavira dijo:
> Leon Widdershoven wrote:
>
>>
>>> - move to a generator approach.
>>
>>
>> Do you mean generator-only approach? I think that would limit the
>> options of the users quite a bit (and I am one of those). I actually
>> like the pipeline
>> approach so that you can build your XML tree
Upayavira wrote:
Leon Widdershoven wrote:
- move to a generator approach.
Do you mean generator-only approach? I think that would limit the
options of the users quite a bit (and I am one of those). I actually
like the pipeline
approach so that you can build your XML tree dynamically; if one
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Now, as I mentioned already [1], I started using the generator approach
to form templates, using the implementation of "wt:" statements using
JXMacro provided by Chris [2]. And this approach is very powerful, as it
allows complex conditional form layou
Leon Widdershoven wrote:
- move to a generator approach.
Do you mean generator-only approach? I think that would limit the
options of the users quite a bit (and I am one of those). I actually
like the pipeline
approach so that you can build your XML tree dynamically; if one would
move
to a g
- move to a generator approach.
Do you mean generator-only approach? I think that would limit the options of
the users quite a bit (and I am one of those). I actually like the pipeline
approach so that you can build your XML tree dynamically; if one would move
to a generator only approach other g
Sylvain Wallez wrote:
Now, as I mentioned already [1], I started using the generator approach
to form templates, using the implementation of "wt:" statements using
JXMacro provided by Chris [2]. And this approach is very powerful, as it
allows complex conditional form layout without requiring the
Antonio Gallardo wrote:
Sylvain Wallez dijo:
So, I propose the following changes to Cocoon forms:
- add a state to widgets (enabled/disabled/hidden).
It maybe good. Can reach the same result using another pipeline to
generate the "form definition" file?
Do you mean disabling fields by u
Sylvain Wallez dijo:
> So, I propose the following changes to Cocoon forms:
> - add a state to widgets (enabled/disabled/hidden).
It maybe good. Can reach the same result using another pipeline to
generate the "form definition" file?
> - move to a generator approach.
Can we still use JXTemplateGe
roy huang wrote:
>http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107792005324520&w=2
>In this link,Sylvain suggest 3 states for a widget,I think it's a good idea.
>Today I want to hide an action under some condition ,but I just can't if I don't
>modify the forms-field-styling.xsl.
>I use a tran
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107792005324520&w=2
In this link,Sylvain suggest 3 states for a widget,I think it's a good idea.
Today I want to hide an action under some condition ,but I just can't if I don't
modify the forms-field-styling.xsl.
I use a transformer to generate dif
Jeremy Quinn wrote:
On 25 Feb 2004, at 12:32, Reinhard Poetz wrote:
-Original Message-
From: Antonio Gallardo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 25, 2004 1:28 PM
To: [EMAIL PROTECTED]
Subject: Re: disabling widgets
Jeremy Quinn dijo:
Hi All
I have a booleanfield
Antonio Gallardo wrote:
Reinhard Poetz dijo:
Sorry, I don't like this client-side approach.
We have to find something better because sometimes the 'presentation
state' of a widget can depend on the 'application state'. Flowscript as
controller should have access to both.
Hi Reinhard:
How
snip
> > >>> I have a booleanfield widget, that needs to be disabled
> >> under certain
> >>> conditions.
> >>>
> >>> pseudo-code :
> >>>
> >>> if ( album.scenarios.size() > 0 ) {
> >>> disable ( album.publishable );
> >>> }
I have solved this in a slightly hacky way
woo
ailto:[EMAIL PROTECTED]
> >> Sent: Wednesday, February 25, 2004 1:28 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: disabling widgets
> >>
> >>
> >> Jeremy Quinn dijo:
> >>> Hi All
> >>>
> >>> I have
y, February 25, 2004 1:28 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: disabling widgets
> >>
> >>
> >> Jeremy Quinn dijo:
> >>> Hi All
> >>>
> >>> I have a booleanfield widget, that needs to be disabled
On 25 Feb 2004, at 14:52, Guido Casper wrote:
Jeremy Quinn wrote:
It is with much joy that I find @readonly is ignored by both Mozilla
and Safari (hoo-bloody-ray!! )
Try @disabled instead.
Unfortunately AFAIU (according to the spec at www.w3.org) @disabled
input fields do not get posted to the s
Jeremy Quinn wrote:
It is with much joy that I find @readonly is ignored by both Mozilla and
Safari (hoo-bloody-ray!! )
Try @disabled instead.
Guido
On 25 Feb 2004, at 12:32, Reinhard Poetz wrote:
-Original Message-
From: Antonio Gallardo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 25, 2004 1:28 PM
To: [EMAIL PROTECTED]
Subject: Re: disabling widgets
Jeremy Quinn dijo:
Hi All
I have a booleanfield widget, that needs to be
> -Original Message-
> From: Antonio Gallardo [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 25, 2004 1:28 PM
> To: [EMAIL PROTECTED]
> Subject: Re: disabling widgets
>
>
> Jeremy Quinn dijo:
> > Hi All
> >
> > I have a booleanfield
Jeremy Quinn dijo:
> Hi All
>
> I have a booleanfield widget, that needs to be disabled under certain
> conditions.
>
> pseudo-code :
>
> if ( album.scenarios.size() > 0 ) {
>disable ( album.publishable );
> }
>
> ie. the album.publishable value needs to be in the form,
Reinhard Poetz dijo:
> From: Antonio Gallardo
>> Based on some observation while no-tech oriented users filled
>> HTML forms. It makes clear to me that they don't liked the
>> round-trip to the server. It was confusing to him! It is
>> clear a non-conventional interface. Also it waste time, no
>> m
From: Antonio Gallardo [mailto:[EMAIL PROTECTED]
> Reinhard Poetz dijo:
> > Sorry, I don't like this client-side approach.
> > We have to find something better because sometimes the
> 'presentation
> > state' of a widget can depend on the 'application state'.
> Flowscript
> > as controller s
Jeremy Quinn dijo:
if ( album.scenarios.size() > 0 ) {
disable ( album.publishable );
}
Is there a way of doing this in Cocoon Forms ?
>>>
I thought I don't understand this clear. Did you want to do this just when
the page is rendered?
Then look for , a
Reinhard Poetz dijo:
> Sorry, I don't like this client-side approach.
> We have to find something better because sometimes the 'presentation
> state' of a widget can depend on the 'application state'. Flowscript as
> controller should have access to both.
Hi Reinhard:
How manage a dynamic "show/h
On 25 Feb 2004, at 11:32, Reinhard Poetz wrote:
From: Antonio Gallardo [mailto:[EMAIL PROTECTED]
Jeremy Quinn dijo:
I have a booleanfield widget, that needs to be disabled
under certain
conditions.
pseudo-code :
if ( album.scenarios.size() > 0 ) {
disable ( album.publis
From: Antonio Gallardo [mailto:[EMAIL PROTECTED]
> Jeremy Quinn dijo:
> > I have a booleanfield widget, that needs to be disabled
> under certain
> > conditions.
> >
> > pseudo-code :
> >
> > if ( album.scenarios.size() > 0 ) {
> > disable ( album.publishable );
> > }
> >
Jeremy Quinn dijo:
> I have a booleanfield widget, that needs to be disabled under certain
> conditions.
>
> pseudo-code :
>
> if ( album.scenarios.size() > 0 ) {
>disable ( album.publishable );
> }
>
> ie. the album.publishable value needs to be in the form, but should
Hi All
I have a booleanfield widget, that needs to be disabled under certain
conditions.
pseudo-code :
if ( album.scenarios.size() > 0 ) {
disable ( album.publishable );
}
ie. the album.publishable value needs to be in the form, but should not
be alterable by t
39 matches
Mail list logo
