RE: new person type questions

[Scott Deboy]

Title: Message

I'd say LF5 and Chainsaw V2 have a good amount in common.  Chainsaw was designed with a different metaphor in mind and designed from the start to be more flexible with regard to filtering...here are some of the differences:   SUPPORT FOR MULTIPLE SOURCE 'APPLICATIONS' Chainsaw was designed around a tabbed pane metaphor.  The idea is that logging event sources can be defined as unique 'applications', which have their events routed to their own tab on the tabbed pane.  These tabs can be docked in the tabbedpane or undocked for side-by-side viewing of events.    CONFIGURABLE EVENT DISPLAY You can enable a multi-line tooltip that shows the event data.  The detail pane and multi-line tooltip fields are configurable.   There is 'scroll to bottom' support which can be enabled/disabled.   Column order, size and filters and detail pane fields/tooltip fields are loaded and saved automatically - on a per-tab basis.   Sorting support (thanks Claude Duguay!)   CONFIGURABLE BUFFER SIZE Support for cyclic buffer (thanks Ceki and Paul Smith) with a configurable buffer size or non-cyclic buffer for handling events in the tables.   FILTERING Color filters and display filters can be defined for almost any column and applied individually (apply a display filter for one column and color filter from another column if you'd like).   A custom filtering mechanism which supports regexps and can be applied to the currently filtered rows or all rows (that's the reason for the 'override' checkbox next to the QuickFilter).   EVENT SOURCE-AGNOSTIC Support for reception of JDK1.4 logging events via the standard socket/xml support provided in util.logging.   I developed a number of appenders and receivers to support my -source agnostic- goals: multicast, udp, database and socket-based appenders and receivers that accept XML formatted data (either via XMLLayout and log4j.dtd or JDK1.4's logger.dtd).  I've contacted the log4perl, log4net and a couple of log4c++ port folks and they're at different stages of adding support in their port for XML-generated events that conform to the DTD so they can use the UI (as well as other appenders if you want to configure them with a receiver that can accept the events).   FEEDBACK? The UI is at a point where the bugs aren't obvious, and I would love more serious feedback on functionality/usability/performance, etc.  Documentation is thin and the serialized representation of filters and settings may change before the official release, but it is pretty stable now and if anyone is interested, please pull the sandbox and try it out for yourself.  I've implemented as many features as I felt were necessary - if others are interested in a feature I didn't add (or if you can find a bug), I'd love to hear about it.   Finally, a big thanks to Paul Smith for all his work helping refactor/add functionality and improve the usability of the new UI..   So, anyone interested in trying the new Chainsaw version, please do!  I'd appreciate the feedback..     Hope this helps, Scott                 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 3:44 PM To: [EMAIL PROTECTED] Subject: new person type questions Hi,   I'm beginning to utilize log4j in a couple of projects at work and I'm looking at contributing to the project as well. I have a couple of quick questions.   1) You have two graphic interfaces that are in the build. Chainsaw and lf5, chainsaw seems to be getting the most commits but lf5 seems already ahead in features? Is lf5 being phased out in log4j for chainsaw or the reverse?   2) I noticed on the "Plan" webpage that there is a note about re-implementing the DailyRollingFileAppender. That actually intersects a couple of areas that I have been working on recently and I wanted to know if there has been a design laid out for the new implementation.   thanks     Jason Bailey