Write a prototype and email it to this list. Theoretically a committer
with a similar interest will review it, be impressed, and take it off your
hands. He/she _may_ nominate you to be a committer to the tag
library; this usually happens, but there are no guarantees. It's mainly
dependent on the size of your contribution and the quality of the work.
You should also check the current list of tag libraries and make sure
there's no overlap with an existing project.
- Morgan
On Tue, 19 Jun 2001, Sean Rohead wrote:
> Bingo! I'm new to this open source thing and don't know how to go about
> getting a new tag library started. Doesn't a committer have to do that?
>
> Sean
>
> -----Original Message-----
> From: Morgan Delagrange [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 19, 2001 12:56 PM
> To: '[EMAIL PROTECTED]'
> Subject: Re: Another suggestion for DBTags
>
>
> Sounds like a suggestion for another tag library, not for DBTags. :)
>
> On Tue, 19 Jun 2001, Sean Rohead wrote:
>
> > I like the tags for getting data from a result set (getColumn, getDate,
> > etc...), but it doesn't seem like these tags should be doing any
> formatting.
> > Rather, a set of general purpose tags for formatting dates and numbers
> need
> > to be written and these tags can enclose the result of getDate. There are
> > lots of cases where I want to format dates and numbers and putting this
> > functionality in the dbtags means that functionality is *only* available
> > when iterating over result sets -- bad. I'm thinking of something like:
> >
> > <sql:resultSet id="results">
> > <format:date style="SHORT"><sql:getDate position="1"/></format:date>
> > </sql:resultSet>
> >
> > instead of
> >
> > <sql:resultSet id="results">
> > <sql:getDate format="SHORT" position="1"/>
> > </sql:resultSet>
> >
> >
> > Yes, it's more verbose, but far more flexible.
> >
>
