Re: BImage ?

This is a multi-part message in MIME format...

------------=_1165850666-11279-96
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Jacob Kjome a =E9crit :

> What I'm interesting in finding out is whether you need to make=20
> changes to Barracuda's core in order to do what you want?=20
I don't know yet, but I am under the impression that I will need any=20
nested component to implement createDefaultNode in its renderer, to be=20
able to append this nodes to the parent component...

Right now, the abstract DOMComponentRenderer will throw an=20
UnsupportedFormatException, and each component has to override it to=20
implement the feature.
I think I would need a more lenient implementation, maybe returning a=20
<span> if vc.getTemplateNode() is null.

Or it could be a little bit more smart, and each component could return=20
a default node if and only if vc.getTemplateNode() is null or is not a=20
compatible node (so BText for example would not return any default node=20
except if null, but BImage would always return one except if=20
vc.getTemplateNode() is already an IMG. Or the component could return a=20
Set of compatible nodes (maybe even based on ClientType or FormatType...)

Well, I don't know if this speaks to you...

I am going to experiment and come with real code maybe.

> I made some changes a while back to add a BCompoundComponent=20
> interface, which prevents rendering code from having to check for=20
> instanceof of specific component implementations, such as BList,=20
> BTable, and BTemplate.  It allows other components with similar=20
> compound structures to implement the same interface and pass through=20
> the rendering code successfully, in the same way as said components.=20=
=20
> I'm not sure if this applies in your situation, but just wanted to=20
> make sure you knew about that.
Yes, I noticed this interface, but I have not yet found how it is used=20
in the code... I am looking at this.

>
> As far as providing super specific components for public use, I think=20
> we might want to separate that from the core but, at the same time,=20
> make sure the core can fully support custom components.
I agree on that.
>   We might also want to consider doing more with AJAX and plain=20
> javascript components.  Seems to me one could keep things very generic=20
> on the server side components and apply some javascript component over=20
> a simple list, and make that list do all kinds of funky UI-related=20
> things.
Yes. I also would like to see how/if the event model would interact with=20
async requests... This is on my todo list as well.
>
> Anyway, let us know how it goes.
Sure, I will ;-)

Franck


------------=_1165850666-11279-96
Content-Type: text/plain; name="message-footer.txt"
Content-Disposition: inline; filename="message-footer.txt"
Content-Transfer-Encoding: 8bit



--

Barracuda mailing list

[email protected]

http://www.objectweb.org/wws/lists/projects/barracuda


------------=_1165850666-11279-96--