[CFORMS] My idea of improvements

[Nuno Santos <ns...@electroplus.pt>]

After using the CFORMS API for a while i found myself with a list of
improvements that would boost the runtime handling of the forms: 
- state flags that are mutable at runtime ( required, enabled,
read-only, visible )
- the widget.getParent should return a container widget.
- the selection list should be aware of is parent widget.

Re: [CFORMS] My idea of improvements

[Nuno Santos <ns...@electroplus.pt>]

On Wed, 2004-06-16 at 16:41, Sylvain Wallez wrote:
> >- the widget.getParent should return a container widget.
> >  
> >
> ContainerWidget has disappeared and getParent() has moved back to Widget ;-)

Are you saying that now all widgets may have children?

> 
> >- the selection list should be aware of is parent widget.
> >  
> >
> Mmmh... can you elaborate on this need? I do have some forms where a 
> selection list is shared by many widgets.

Do you have your selection list instance shared or only the selection
list builder? 

What i have is a selection list that depends on another one and if the
selection list is aware of is parent widget, than it would be more easy
to implement!

> 
> Sylvain

Re: [CFORMS] My idea of improvements

[Nuno Santos <ns...@electroplus.pt>]

On Wed, 2004-06-16 at 17:41, Vadim Gritsenko wrote:
> Sylvain Wallez wrote:
> 
> > Mmmh... can you elaborate on this need? I do have some forms where a 
> > selection list is shared by many widgets.
> 
> 
> And, please preserve this capability. I have a case where creating 
> selection list for each widget is too costly, memory- and cpu-wise.
> 
> Vadim
> 

Found a possible way:

If the selection list builder is aware of the calling widget, that it
can pass that out to the selection list. That way we can have both
methods implemented either parent aware and parent unaware -the builder
will decide that !

Re: [CFORMS] My idea of improvements

[Vadim Gritsenko <va...@reverycodes.com>]

Sylvain Wallez wrote:

> Mmmh... can you elaborate on this need? I do have some forms where a 
> selection list is shared by many widgets.


And, please preserve this capability. I have a case where creating 
selection list for each widget is too costly, memory- and cpu-wise.

Vadim

Re: [CFORMS] My idea of improvements

[Sylvain Wallez <sy...@apache.org>]

Nuno Santos wrote:

>After using the CFORMS API for a while i found myself with a list of improvements that would boost the runtime handling of the forms: 
>- state flags that are mutable at runtime ( required, enabled, read-only, visible )
>  
>
This has been discussed, and is high on my todo list.

>- the widget.getParent should return a container widget.
>  
>
ContainerWidget has disappeared and getParent() has moved back to Widget ;-)

>- the selection list should be aware of is parent widget.
>  
>
Mmmh... can you elaborate on this need? I do have some forms where a 
selection list is shared by many widgets.

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }