Re: Re: Re: little extension of BLink
Jacob Kjome <[email protected]>
| Newsgroups | gmane.comp.java.enhydra.barracuda.general |
|---|---|
| Message-ID | <[email protected]> |
At 09:17 AM 10/30/2003 +0100, you wrote: >Jacob Kjome <[email protected]> wrote: > > > The point of my comment was about the specified values > > you want to add as constants. Please point out where those are > > defined by the spec. I don't think they are. >Yes they are, see: >http://www.w3.org/TR/html401/types.html#type-frame-target I stand corrected. Thanks for pointing that out. > > I think I opened up a can of worms. See Christian's response. BLink > > is there for components you want to set a BAction on, but also want > > to set the text on. A solution already exists, however. You can > > bind two separate components to the same view. >... hmmm solution ... more a hack I think ;-) >(not very smart to use two heavy weight components for one small task) Well, yes and no. Other than tags like BTable, Barracuda components aren't specialized. They adapt to different elements. If you remove the concept of BLink, which I've already pointed out as being incongruent with some of the tags is meant for, then you are left with no specific way to deal with tags that need both linking capabilities and textual capabilities. Remember that many tags that have linking capabilities don't require (or even allow) visual text. We could solve this be making a BComponent for every tag in HTML (or any other markup we support). However, I'd say that is overkill as well and leaves us with a glut of BComponents. What if you change the element from <p> to <h1>? In Barracuda, that means you continue returning a BText component and it doesn't matter. In another component-based framework, that might mean forcing server-side code to change from PComponent to H1Component. That is certainly not desireable or flexible. We're all ears on any ideas on how to improve Barracuda components. Let us know your ideas. >To go back to my starting wish, I just find it useful to have the new >constants in BLink because I think they are useful. Not more. Looks like Christian is +1 for this (previous email). I'm +0. If you are +1, then I guess they can be added. I'll let Christian add it. I just think that these names are well enough known that it isn't so necessary to add the constants, but I don't care enough to block their addition. Jake