Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: neutral (asf.osuosl.org: 167.206.4.198 is neither permitted nor
 denied by domain of hgilde@gmail.com)
Date: Sun, 06 Nov 2005 11:49:03 -0500
From: Hans Gilde <hgilde@gmail.com>
Subject: RE: [jelly] refillComponent tag ? (was Re: swing example)
In-reply-to: <8864a202f8766b775f9a433e144f85bc@activemath.org>
To: 'Jakarta Commons Users List' <commons-user@jakarta.apache.org>
Message-id: <0IPJ005EALDMMYI0@mta3.srv.hcvlny.cv.net>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Thread-index: AcXhQG833wqV5EpaQO+EzukFdGXixgBWrQ0g

Should be fine. It would implement ContainerTag and would just clear the
container, then run its body. The body components would add themselves =
and
then it may need of call pack if it's visible. There are a couple of =
tricky
bits, like ensuring that it's addChild method has all the features of
ComponentTag's addChild.

It could extend ComponentTag, but one would have to look carefully at =
what
must be overridden.

One question is: this new tag is essentially acting like the original =
panel
in terms of allowing children to add components to it. Would it go one =
step
further and allow you to change the bean fields of that panel using
attributes in the tag?

For instance, would this work:

<sw:frame>
	<sw:panel name=3D"myPanel" var=3D"myList"/>
</sw:frame>

.....
<!--refillComponent is now proxying for the panel tag above-->
<sw:refillComponent name=3D"yourPanel" ref=3D"myList">
	<sw:label>the panel now has the bean property
name=3DyourPanel</sw:label>
</sw:refillComponent>

-----Original Message-----
From: Paul Libbrecht [mailto:paul@activemath.org]=20
Sent: Friday, November 04, 2005 8:05 AM
To: Jakarta Commons Users List
Subject: [jelly] refillComponent tag ? (was Re: swing example)

Can other Jelly-Swing users comment on such a tag. It really looks to=20
be able to solve quite many issues I've met thus far.

thanks

paul


Le 3 nov. 05, =E0 21:35, D=E1rio Lu=EDs Coneglian Oliveros a =E9crit :
[...]
> Regarding your reloadable strategy, I think it would be great to have=20
> something like that. We can discuss it later if you wish.
> [...]
>> Just thinking out loud, I seem to encounter that the following might=20
>> be
>> enough:
>>
>> <sw:frame>
>>   blabla
>>    <sw:panel var=3D"myList"/>
>>   </sw:frame>
>>
>> and somewhere else (e.g. as a child of action:
>>
>> <sw:refillComponent name=3D"panel">
>>    <sw:label>casdasa</sw:label>
>>    ....
>> </sw:refillComponent>
>>
>> That is, we would introduce a "target" element that would allow an
>> component to be cleared than repopulated by its content...
>> This seems suddenly pretty easy to implement compared to the
>> "reloadable" kind of things I expected. Would it fit your task ?


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org