logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Womack <mwom...@bevocal.com>
Subject RE: Where can I help?
Date Mon, 10 Feb 2003 01:09:07 GMT
I'm not a big gui/swing person, so I don't think I can lend much code or
advice on that front, but I would like to help with the adding remote
sources via a gui.  At least as defining these via a gui plugin mechanism.
I have not had a chance to look at it very hard, but it sounds like the
commons-discovery code has a way to search for "plugins" in the classpath.
We could use that to look for the "gui plugins" and add them to the chainsaw
gui dynamically.  That way, when developers create new Receivers, they can
also develop a chainsaw plugin and chainsaw can use them without
modification.

-Mark

> -----Original Message-----
> From: Oliver Burn [mailto:oliver@puppycrawl.com]
> Sent: Sunday, February 09, 2003 4:58 PM
> To: Log4J Developers List
> Subject: RE: Where can I help?
> 
> 
> May be once or twice. :-)
> 
> I'd like to see preferences stored to support:
> 
> - Store the GUI settings. I.e. window size, column widths
> 
> - Make the columns to display selectable. So
>   for example, to choose whether to display the NDC column.
> 
> Oliver
> 
> > -----Original Message-----
> > From: Mark Womack [mailto:mwomack@bevocal.com]
> > Sent: Monday, 10 February 2003 11:44
> > To: 'Log4J Developers List'
> > Subject: RE: Where can I help?
> >
> >
> > My Chainsaw wish list:
> >
> > - ability to sort messages by various columns (sort by time with
> > most recent
> > at bottom instead of top, sort by level, logger, etc)
> > - ability to filter by MDC key/values, filter by multiple 
> category/level
> > names, maybe just let me define my own filter chain?
> > - ability to configure/add new remote sources via gui (support
> > input via new
> > v1.3 Receivers).
> >
> > I think I have mentioned these before...:-)
> >
> > -Mark
> >
> > > -----Original Message-----
> > > From: Oliver Burn [mailto:oliver@puppycrawl.com]
> > > Sent: Sunday, February 09, 2003 4:11 PM
> > > To: Log4J Developers List
> > > Subject: RE: Where can I help?
> > >
> > >
> > > Hi Raymond,
> > >
> > > I am the original author of Chainsaw. I have lots of ideas on
> > > how to improve Chainsaw, but due to time constraints I have
> > > basically taken on the role of maintainer. I will fix any
> > > reported bugs, and endeavour to incorporate patches. I also
> > > have dialogue with some people who would like to modify
> > > Chainsaw. So I would be happy to coordinate with you to improve
> > > Chainsaw.
> > >
> > > WRT Chainsaw not being compatible with output from earlier
> > > XMLLayout format. This is intentional, in so far that when
> > > the format changed, I updated Chainsaw to work with the new
> > > format. From memory I am not sure if it was possible to
> > > be backwardly compatible - that could have been due to
> > > using a validating XML parser. If it is easy and reliable
> > > to support both formats, then this is a good fix.
> > >
> > > Please feel free to e-mail directly.
> > >
> > > Regards,
> > > Oliver
> > >
> > > > -----Original Message-----
> > > > From: Raymond DeCampo [mailto:rdecampo@twcny.rr.com]
> > > > Sent: Monday, 10 February 2003 11:07
> > > > To: Log4J Developers List
> > > > Subject: Re: Where can I help?
> > > >
> > > >
> > > > Thanks for the suggestions.  I think I'll give some 
> effort towards
> > > > improving Chainsaw.
> > > >
> > > > Toward that end, when I was trying to get Chainsaw 
> going today, I
> > > > noticed that it is not compatible with output from 
> earlier XMLLayout
> > > > output that use "category" instead of "logger".  Was this
> > > intentional or
> > > > should I submit my fix?
> > > >
> > > > Is anybody else actively working on Chainsaw?  If so we should
> > > > coordinate our efforts.
> > > >
> > > > Thanks,
> > > > Ray
> > > >
> > > > mwomack@apache.org wrote:
> > > > > All of Scott's suggestions are good.  Ray, what are your
> > > > interests in the
> > > > > log4j code?  What area would you like to look
> > > at/contribute to?  We can
> > > > > certainly suggest an area to look at, but if you have a
> > > > specific area of
> > > > > interest, then it will be more interesting, certainly.  Your
> > > > interest and
> > > > > effort are most welcome.
> > > > >
> > > > > For anyone out there interested in contributing code, I
> > > > started a wiki page
> > > > > with some  guidelines/requirements:
> > > > >
> > > > >
> > > > 
> http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/Co
> > > > ntributingC
> > > > > ode
> > > > >
> > > > > I'd be very interested in documenting the steps one must go
> > > > through to get
> > > > > the current log4j cvs code compiling on one's machine.  Would
> > > > someone be
> > > > > interested in documenting the process in that page as well?
> > > > >
> > > > > -Mark
> > > > >
> > > > >
> > > > >>-----Original Message-----
> > > > >>From: Scott Schram [mailto:scott@schram.net]
> > > > >>Sent: Saturday, February 08, 2003 6:02 PM
> > > > >>To: Log4J Developers List
> > > > >>Subject: Re: Where can I help?
> > > > >>
> > > > >>
> > > > >>Until the log4j gurus have a chance to respond, may I suggest:
> > > > >>
> > > > >>Take a look at the Wiki and see if information there 
> is complete,
> > > > >>or could
> > > > >>use improving.
> > > > >>
> > > > >>http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages
> > > > >>
> > > > >>And the "todo" pages there for ideas:
> > > > >>
> > > >
> > 
> >>http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/ToDo
> > > >>
> > > >>Make sure you can get the source code via CVS, and compile it.
> > > >>
> > > >>Here are some possible areas to work on:
> > > >>
> > > >>http://jakarta.apache.org/log4j/docs/plan.html
> > > >>
> > > >>A couple catch my eye: add automated tests.  Improve Chainsaw.
> > > >>
> > > >>Scott
> > > >>
> > > >>At 12:25 PM 2/8/2003, you wrote:
> > > >>
> > > >>>All,
> > > >>>
> > > >>>I haven't been involved with open source before but I've
> > > wanted to for a
> > > >>>while.  I figured I would take the plunge with log4j.
> > > >>>
> > > >>>Where can I be of help?  Should I just grab some bugs from
> > > Bugzilla and
> > > >>>go?  Does anyone have any in particular they'd like to see
> > tackled but
> > > >>>don't have the time themselves?
> > > >>>
> > > >>>Thanks,
> > > >>>Ray
> > > >>>
> > > >>>
> > >
> > 
> >>>-----------------------------------------------------------
> ----------
> > > >>>To unsubscribe, e-mail: 
> log4j-dev-unsubscribe@jakarta.apache.org
> > > >>>For additional commands, e-mail: 
> log4j-dev-help@jakarta.apache.org
> > > >>
> > > >>
> > > 
> >>------------------------------------------------------------
> ---------
> > > >>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> > > >>For additional commands, e-mail: 
> log4j-dev-help@jakarta.apache.org
> > > >>
> > > >
> > > >
> > > >
> > > > 
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: 
> log4j-dev-help@jakarta.apache.org
> > > >
> > > >
> > >
> > >
> > >
> > > 
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
> > >
> >
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org


Mime
View raw message