The poor guy may very well not be up to that though. If we really
want tapestry to be useful to inexperienced or "new" developers, then asking
them to just "tweak" the components themselves isn't the way to go. Sure, a
good programmer (or just an intermediate one with good knowledge of
tapestry), can do this, but a good programmer with sufficient time can do
damn near anything (except solve the traveling salesman problem).
That's the thing that always makes me a little uncomfortable about
open source communities. As the community matures and gets more and more
experienced with its own product, it tends to get less welcoming and more
dismissive of newcomers and their concerns e.g. that's not a bug, it's a
feature, duh! I mean seriously, try asking *any* question on the Hibernate
forums and watch the snarking sneers begin. Great product, lousy, insular,
and arrogant community.
I don't think that's specifically what Geoff was trying to do here,
but it's a fear that always lurks in the back of my mind in cases like this.
I'm as guilty of this as anyone, I'm sure, but I still think its something
we should try to look out for.
Ultimately, we can't assume that anyone who uses tapestry is:
A) An experienced java programmer.
B) Familiar with the classic design patterns.
C) Comfortable running ant.
D) Comfortable modifying somebody else's code.
E) Either already aware of, or capable of easily discerning, the
overall code structure of the Tapestry code base.
If we insist on the above as a minimum to be a member of the "club"
then we've just pained tapestry into a corner where it's never going to get
the kind of widespread following we all (I assume) hope it gets.
I guess what I'm saying is give the guy a break.
--- Pat
> -----Original Message-----
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Nick Westgate
> Sent: Friday, July 22, 2005 9:33 PM
> To: [email protected]
> Subject: Re: Is there a bug for dual Select components?Bug still exits!
>
> Patrick Casey <patcasey <at> adelphia.net> writes:
>
> >
> >
> > Probably because it's frustrating to find a bug (or at least think
> > you've found a bug) and have folks neither confirm, nor deny the bug,
> but
> > instead question why the hell you're doing things a particular way :).
>
> No excuse. Probably 99% of posts like this are not bugs.
> Geoff's question was entirely reasonable, since the example code
> provided did not indicate multiple selections.
>
> Anyway "tapestrycn", you can work around the bug by downloading the source
> for Tapestry, copying the Select component into your project, and making
> your own customised Select component.
>
> Patch the java source as follows:
> protected void cleanupAfterRender(IRequestCycle cycle)
> {
> _rendering = false;
> _selections = null;
>
> cycle.removeAttribute(ATTRIBUTE_NAME);
> }
>
> Cheers,
> Nick.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
