RE: [Tapestry-developer] Why doesn't the Conditional comonent not accept informal parameters ?

["Howard M. Lewis Ship" <hl...@attbi.com>]

Tapestry has constantly evolved to meet end-user's needs and desires.  In
some cases, there's a compelling technical reason why Tapestry works in a
particular way, but in a case like yours, its just a matter of nobody else
getting irritated enough to report and fix the problem.  Remember that
everybody will have a different set of "itches" that need "scratching".  For
example, one recent user was dissapointed that the Insert component didn't
insert " " when the value was null (this can be important when you use
a lot of tables for layout).  That was his itch.

One of the big benefits of Tapestry is that the core components, those
provided with the framework, have no special nature to them.  If you look at
the code, they invoke no private methods, perform no special typecasts.
There's no reason why you can't, at least temporarily, create your own
version of the Conditional component that works exactly how you want it to.

In fact, you can *replace* the existing Conditional component.  Simply
create a component in your application named "Conditional" and Tapestry will
use that component, not the framework component, on all the pages in your
application.  Eventually, a newer version of the framework may have the
updates you want and you can simply delete your Conditional component
without changing your pages at all.

Because Tapestry is open source, you can see the code for Conditional.  I
think if you look at the code for Insert as well, you'll know how to create
a component that does exactly what you need.

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry



> -----Original Message-----
> From: Elankath, Tarun (Cognizant) [mailto:ETarun@blr.cognizant.com] 
> Sent: Monday, February 24, 2003 9:26 AM
> To: Howard M. Lewis Ship
> Subject: RE: [Tapestry-developer] Why doesn't the Conditional 
> comonent not accept informal parameters ?
> 
> 
> I sincerely apologize. I didn't mean to be accusatory or 
> critical at all. I was a bit dissapointed and I am afraid it 
> came out harshly.
> 
> I know I haven't contributed anything nor paid for Tapestry. 
> I am just an intermediate java programmer who needs to 
> acquire a lot of skill and knowledge before I can contribute 
> fruitfully to any open source project. 
> 
> But I can start with something small. I am having a lot of 
> doubts with Tapestry. When I have resolved these, I can 
> contribute with a FAQ. 
> 
> But to resolve the doubts I have, I need to ask questions on 
> the list. For an expert such as you, those questions might 
> seem exceedingly stupid, but they are still relevant and 
> significant to an individual who is grasping the basics.
> 
> In my previous post, I was trying to ask whether there was 
> any particular reason that informal parameters were forbidden 
> for the conditional component. My frustration showed and I 
> admit the post was offensive.
> 
> 
> I apologize once again.
> Tarun
> 
> 
> -----Original Message-----
> From: Howard M. Lewis Ship [mailto:hlship@attbi.com]
> Sent: Monday, February 24, 2003 7:25 PM
> To: 'Elankath, Tarun (Cognizant)'
> Subject: RE: [Tapestry-developer] Why doesn't the Conditional 
> comonent not accept informal parameters ?
> 
> 
> Caution: attitude
> 
> You didn't pay for Tapestry.  You didn't contribute to the 
> project.  Posting feature requests with a negative, 
> accusatory tone are not helpful, they are very likely to get 
> you ignored.
> 
> --
> Howard M. Lewis Ship
> Creator, Tapestry: Java Web Components 
> http://jakarta.apache.org/proposals/tapestry
> 
> 
> 
> > -----Original Message-----
> > From: tapestry-developer-admin@lists.sourceforge.net
> > [mailto:tapestry-developer-admin@lists.sourceforge.net] On 
> > Behalf Of Elankath, Tarun (Cognizant)
> > Sent: Monday, February 24, 2003 7:13 AM
> > To: tapestry-developer@lists.sourceforge.net
> > Subject: [Tapestry-developer] Why doesn't the Conditional 
> > comonent not accept informal parameters ?
> > 
> > 
> > Hi list,
> > 
> > I am rather peeved that the conditional component doesn't
> > accept informal parameters. I have an element with a CLASS 
> > attribute that I wish to display conditionally. 
> > Unfortunately, if I give a jwcid to this element and let it 
> > be a conditional component, then the CLASS attribute is invalid.
> > 
> > IMHO, this is a bug. I don't see any good reason as to why
> > informal parameters are forbidden int the conditional 
> > component. As far as good sense goes, informal parameters 
> > should be allowed in all circumstances for all components, it 
> > should only be disabled in case of conflict.
> > 
> > I know have to put an un-necessary pair of <span
> > jwcid="ifBlah"> tags around the element now.  This only 
> > messes the template, instead of keeping it inviolate. 
> > 
> > 
> > Regards,
> > Tarun
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Tapestry-developer mailing list 
> > Tapestry-developer@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/tapestry-developer
> > 
>