> -----Original Message-----
> From: Karr, David [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 01, 2002 4:17 PM
> To: 'Struts Developers List'
> Subject: RE: Struts-EL: Finished with copyright header and javadoc
>
>
> > -----Original Message-----
> > From: Martin Cooper [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, October 01, 2002 4:05 PM
> > To: 'Struts Developers List'
> > Subject: RE: Struts-EL: Finished with copyright header and javadoc
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, September 30, 2002 10:56 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Struts-EL: Finished with copyright header and javadoc
> > >
> > > In several tag classes in the HTML library, I have some
> > > attribute evaluations
> > > commented out, as I've discovered that these are attributes
> > > which the HTML 4.01
> > > spec defines, but which are not covered in the current Struts
> > > tag, either
> > > because their TLD doesn't specify them, or the Struts tag
> > > doesn't properly emit
> > > them. I've noticed some of these have had bugs reported
> > > against them (some by
> > > me), but probably not all. One thing I want to do in the
> > > very near future is
> > > make sure all of these are logged (and maybe even fix them :) ).
> >
> > Is there an easy way to find these comments? A Bugzilla
> report listing
> > what's missing would be very helpful. I've wanted to get this
> > cleaned up,
> > but haven't had the time to go through and check all the
> tags myself.
>
> If you want a head start, you can grep for "//.*evalAttr" in
> ".java" files
> in the "contrib/struts-el" tree.
>
> I was planning on rechecking each one that I found (checking
> the spec, the
> tld, and the tag code), just to make sure, before I submitted
> bug reports
> (for each tag), but it doesn't matter who does that. If you
> have time now,
> have at it. Otherwise, that was going to be on my evening
> work task list,
> after I write and submit the announcement tonight, assuming
> I'm granted time
> by my social director :) .
Actually, I don't have a lot of time at the moment (even if I don't have a
social director :) so feel free to have at it. If you want to "divide and
conquer" at some point, we can do that too.
>
> > > Is there some point where it would be worthwhile for me
> to write an
> > > "[ANNOUNCEMENT]" note in struts-user about Struts-EL, or
> > > should that wait until
> > > we get to a Struts release (1.1-b3, or 1.1)?
> >
> > Feel free to make an announcement whenever you are
> > comfortable doing so. It
> > would be a good idea to mention the earliest nightly build in
> > which people
> > should expect the tags to be available.
>
> I submitted my last changes (so far) yesterday evening. I
> assume then, that
> indicating the nightly build of 9/30 would be correct?
The nightly builds happen at ~3am, so if you were working on it last night,
you'd want to mention the 20021001 build. (Nice number!) Unless you were
working on it *really* late, that is!
--
Martin Cooper
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
