Re: BImage ?
Jacob Kjome <[email protected]> Sat, 09 Dec 2006 09:56:57 -0600
| Newsgroups | gmane.comp.java.enhydra.barracuda.general |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format...
------------=_1165679828-23762-15
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
At 01:10 AM 12/9/2006, you wrote:
>Jacob Kjome a =E9crit :
>> Now, as far as actually developing the=20
component, I don't think it's going to
>> happen unless it is contributed. Are you volunteering to do the work?
>>
>Sure, I am... In fact I already made one, but I still need to test it.
>In fact it is quite simple. Right now, it only has two parameters, that
>is 'alt' and 'url'. Both are strings, so I don't try to see if the image
>file is actually there...
>As soon as it is tested, I'll send it to the list.
>
>
>By the way, I am also back on nestable components... The idea is to take
>BContainer parent/childs structure into account to render nested
>components, just like this :
>
>BInput binput =3D new BInput(BInput.TEXT, "inputId", null);
>BImage calimage =3D new BImage("calendar", "images/cal.png");
>calimage.addChild(new BScript("calscript");
>binput.addChild(calimage);
>BLabel blabel =3D new BLabel("User label : ",binput.getId);
>blabel.addChild(binput);
>
>This is much less flexible and generic than the approach you described,
>from the designer point of view, but would allow for more complex
>components (like BCalField component that could embed this kind of
>logic). In a large app, it could provide more consistency in the UI.
>
>To do this, I think I need a rendering logic that would call
>createDefaultNode recursivly on every child of the main component. In
>fact, it is not far from what is done in BList renderer... I will try it
>further, and will alos probably come back to the list with questions :)
>
>Any comments on that ?
>
It all sounds interesting. The fact that=20
Barracuda's core components are designed to be=20
very flexible and generic shouldn't stop people=20
from developing custom components. What I'm=20
interesting in finding out is whether you need to=20
make changes to Barracuda's core in order to do=20
what you want? I made some changes a while back=20
to add a BCompoundComponent interface, which=20
prevents rendering code from having to check for=20
instanceof of specific component implementations,=20
such as BList, BTable, and BTemplate. It allows=20
other components with similar compound structures=20
to implement the same interface and pass through=20
the rendering code successfully, in the same way=20
as said components. I'm not sure if this applies=20
in your situation, but just wanted to make sure you knew about that.
As far as providing super specific components for=20
public use, I think we might want to separate=20
that from the core but, at the same time, make=20
sure the core can fully support custom=20
components. We might also want to consider doing=20
more with AJAX and plain javascript=20
components. Seems to me one could keep things=20
very generic on the server side components and=20
apply some javascript component over a simple=20
list, and make that list do all kinds of funky UI-related things.
Anyway, let us know how it goes.
Jake
>Franck
>> Jake
>>
>> Quoting Franck Routier <[email protected]>:
>>
>>
>>> Hi all,
>>>
>>> has anyone thought about a BImage component ?
>>>
>>> Something like new BImage(String altAttribute, String url) + height,
>>> width, ...
>>>
>>> Would it make sense, or is it just one of these 'just do it with
>>> dom/BText' things ?
>>>
>>> Franck
>>>
>>>
>>>
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>>
>> --
>>
>> Barracuda mailing list
>>
>> [email protected]
>>
>> http://www.objectweb.org/wws/lists/projects/barracuda
>>
>>
>
>
>
>
>--
>Barracuda mailing list
>[email protected]
>http://www.objectweb.org/wws/lists/projects/barracuda
------------=_1165679828-23762-15
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
------------=_1165679828-23762-15--