Ted,
I submitted a patch a month ago, following a go-ahead from Craig to a
bugzilla I raised and it got zero response. Now maybe it wasn't any good and
probably I should have put more explanation, but a response saying something
would have been great.
That was the reason I put the comment about a committer being assigned - I'd
rather know there was someone with "power" interested rather than waste
effort again.
I also submitted code for if/else and switch/case tags - if you've got the
time, I would appreciate your opinion on those as well.
1) PATCH: [Bug 1683] - Change Struts tags to be more granular in their
design:
This patch affected the following tags and involved re-factoring code out of
the doStartTag() method so that Struts tags could be more easily sub-classed
and individual bits of functionality overriden - a good example of where
this could be used is, generating names which include the index value when
embedded in an IterateTag.
BaseFieldTag.java, BaseFieldTag.java, ButtonTag.java, CancelTag.java,
CheckboxTag.java, ImageTag.java, ImgTag.java, MultiboxTag.java,
RadioTag.java, ResetTag.java, SelectTag.java, SubmitTag.java,
TextareaTag.java
http://www.mail-archive.com/struts-dev%40jakarta.apache.org/msg01450.html
I believe quite a few of these tags have been changed since I submitted this
so unless CVS is clever I gues its now can't be applied and was a waste of
time.
2) IF / ELSE and SWITCH/CASE Tags:
These tags are basically just new "wrappers" for existing Struts
functionality - the key classes extend the existing Struts CompareTagBase. I
have a new version since I submitted them which includes the ability to
specify condtions on the case tag - rather than just having to be "equal" -
if its of interest I can send it.
http://www.mail-archive.com/struts-dev@jakarta.apache.org/msg01372.html
Niall
> -----Original Message-----
> From: Ted Husted [mailto:[EMAIL PROTECTED]]
> Sent: 21 June 2001 11:13
> To: [EMAIL PROTECTED]
> Subject: Re: Struts 1.0 Released - Looking forward to 1.1!!!!!!!
>
>
> Just a note:
>
> Committers make the final decision about whether something is added to
> the official distribution, but we do not control the contribution or
> development process. Everyone is invited and encouraged to discuss how
> they would implement features here on the dev list, and then go off and
> implement them -- usually for use in your own project. When you bring
> the code back to list, then we can make the decision about whether it's
> a good fit with the Struts core.
>
> But, hey, don't wait on us guys -- do what *you* need to do, and then
> show us the code when you're ready.
>
> -- Ted Husted, Husted dot Com, Fairport NY USA.
> -- Custom Software ~ Technical Services.
> -- Tel 716 737-3463.
> -- http://www.husted.com/about/struts/
>
> Niall Pemberton wrote:
> > These areas are currently unassigned on the ToDo list and
> presumably need a
> > committer to take control. If someone is assigned I am more
> than willing to
> > contribute to these (and other) areas.
>
