Paul, > If I understand it all correctly, once the LF5Appender class has been > instantiated from being an appender in a local log4j > environment, a separate > Swing GUI is auto-instantiated and shown to display the > incoming log events. > That's pretty cool.
Yeah, the LF5 stuff is pretty cool in that respect. It was part of the thinking behind creating the receiver design. > In a single Receiver model, which is what the initial > revision of ChainSaw > would be I think, we could follow the LF5 approach almost > identically. It's > probably worth the refactoring to go towards this model initially. We should also support a "stand alone" mode, as lots of folks use Chainsaw to read pre-existing xml log files. > Thinking further ahead though, what are the possibilities of > defining more > than one ChainSawAppender. I can see windows popping up > everywhere.. ;) > > Let's see if I can draw an ASCII diagram of Nirvana here: > > > REMOTE_SERVER1 \ /--> ChainSawAppender1 > REMOTE_SERVER2 --> LOCAL_LOG4J_VM ---> ChainSawAppender2 > REMOTE_SERVER3 / \--> ChainSawAppender3 > > In the above, each Remote server is broadcasting the log > events to the Local > log4j event bus (or in the new Reciever model, there are 3 Receivers > configured to connect to each Server). The local bus then > configures a > series of ChainSawAppenders according to it's own > Category/Level filter in > the log4j.xml. I like it. The log4j event bus (TM). :-) > However at this point, is there any _need_ to spawn a GUI > window for each > Appender? Rather than the model receiving events and > spawning a window, > perhaps another way to look at it is that a ChainSawLogPanel > "attaches" > itself to one of the known ChainSawAppenders for display. > That way the user > can hide/close windows, while the ChainSawAppender (which is > itself the > TableModel) is still able to receive events in the background. Is it possible for each appender to find a "main" window and attach itself to it? I would be fine with that, especially if some of the tabbed panel/viewer stuff that has been talked about comes into existence. Then I could drag one of the panels off the main window to live in its own window if I wanted. I guess I don't see a reason why there should be multiple instances of the "core" chainsaw portion per logger repository. Sure, it could be shared I suppose. Will I be able to set different settings/filters per panel (eventually)? That is kind of a different issue. Seems like you are on the right track here. -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
