Re: Update CocoonForms flowscript API (was Re: [CocoonForms] Code freeze)

2004-03-07 Thread Vadim Gritsenko 
Christopher Oliver wrote:

Those jx macros have never been checked in. I can check in something 
after Reinhard is done if you want.


I think it would be beneficial for all. Just yesterday I had a need to 
do labels for one control created out of value of another control... 
It's not possible with transformer, but should be possible with macros.

Vadim


To fix the problem you mention, a helper Java class has to be written 
that buffers the widget's end-element event and allows the macro to 
stream the wi:styling element before it. This class can be called from 
the macro.

Chris

Vadim Gritsenko wrote:

Christopher Oliver wrote:

Can we also get rid of the original Woody flowscript API as part of 
this process (and replace it with the v2 version)? The original was 
clearly not ready for prime time.




This new API, does it allow creation of JXTemplate macros with proper 
wi:styling handling (old set of macros were printing wi:styling 
outside of wi:field element)?

Vadim

Re: Update CocoonForms flowscript API (was Re: [CocoonForms] Code freeze)

2004-03-06 Thread Stefano Mazzocchi 
Christopher Oliver wrote:

Can we also get rid of the original Woody flowscript API as part of this 
process (and replace it with the v2 version)? The original was clearly 
not ready for prime time.
+1

--
Stefano.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: Update CocoonForms flowscript API (was Re: [CocoonForms] Code freeze)

2004-03-06 Thread Vadim Gritsenko 
Christopher Oliver wrote:

Can we also get rid of the original Woody flowscript API as part of 
this process (and replace it with the v2 version)? The original was 
clearly not ready for prime time.


This new API, does it allow creation of JXTemplate macros with proper 
wi:styling handling (old set of macros were printing wi:styling outside 
of wi:field element)?

Vadim

Re: Update CocoonForms flowscript API (was Re: [CocoonForms] Code freeze)

2004-03-06 Thread Christopher Oliver 
Those jx macros have never been checked in. I can check in something 
after Reinhard is done if you want. To fix the problem you mention, a 
helper Java class has to be written that buffers the widget's 
end-element event and allows the macro to stream the wi:styling element 
before it. This class can be called from the macro.

Chris

Vadim Gritsenko wrote:

Christopher Oliver wrote:

Can we also get rid of the original Woody flowscript API as part of 
this process (and replace it with the v2 version)? The original was 
clearly not ready for prime time.


This new API, does it allow creation of JXTemplate macros with proper 
wi:styling handling (old set of macros were printing wi:styling 
outside of wi:field element)?

Vadim