> We should also support a "stand alone" mode, as lots of folks > use Chainsaw > to read pre-existing xml log files.
Mmm, yes, I had forgotten.. *whoops* > Is it possible for each appender to find a "main" window and > attach itself > to it? > Yeah, that's another way of thinking of it actually.. Could we use the name of each Appender to be the Tab/Window name (I assume a class can query the "names" of the locally configured Appenders defined in the Log4j config?) What makes me feel a little un-easy about that concept though is that the ChainSawAppender is going to need to "know" more about the ChainSaw GUI infrastructure. What I was hoping for was that ChainSawAppender class would simply be a known compatable source of information for the ChainSaw GUI. In terms of Separate of Concern, the GUI probably has a right to know where it's source of information is coming from, rather than the Appender having the right to understand where that data is going. Having said that, I've just realised I've probably violated the whole Appender model. I guess an Appender DOES know where the destination is going (file, network)... Mmm, sorry for the thinking out loud here. Perhaps you're right. The ChainSawAppender can be created by log4j core, and during init it registers itself as a TableModel with it's own ChainSawPanel, and also register that panel with the ChainSawPanelFactory. Now the ChainSaw gui code can query the ChainSawPanelFactory for all the known Panels, and render them/hide them, control them as it wishes. How does that sound? > I would be fine with that, especially if some of the tabbed > panel/viewer stuff that has been talked about comes into > existence. Does anyone know the state of that yet? It's not in CVS? I'm very keen on using it myself for my work. > Will I be able to set different > settings/filters > per panel (eventually)? That is kind of a different issue. That's my goal. Have the same source appender with separate querying ability via different tab/windows. cheers, Paul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
