Return-Path: 
 <log4j-dev-return-7292-apmail-logging-log4j-dev-archive=logging.apache.org@logging.apache.org>
Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org
Received: (qmail 70614 invoked from network); 21 May 2004 22:33:08 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 21 May 2004 22:33:08 -0000
Received: (qmail 59219 invoked by uid 500); 21 May 2004 22:32:40 -0000
Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org
Received: (qmail 58729 invoked by uid 500); 21 May 2004 22:32:35 -0000
Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:log4j-dev-unsubscribe@logging.apache.org>
List-Subscribe: <mailto:log4j-dev-subscribe@logging.apache.org>
List-Help: <mailto:log4j-dev-help@logging.apache.org>
List-Post: <mailto:log4j-dev@logging.apache.org>
List-Id: "Log4J Developers List" <log4j-dev.logging.apache.org>
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Delivered-To: mailing list log4j-dev@logging.apache.org
Received: (qmail 58310 invoked by uid 98); 21 May 2004 22:32:30 -0000
Received: from Paul.Smith@lawlex.com.au by hermes.apache.org by uid 82 with
 qmail-scanner-1.20
 (clamuko: 0.70.  Clear:RC:0(202.92.123.11):.
 Processed in 0.106935 secs); 21 May 2004 22:32:30 -0000
X-Qmail-Scanner-Mail-From: Paul.Smith@lawlex.com.au via hermes.apache.org
X-Qmail-Scanner: 1.20 (Clear:RC:0(202.92.123.11):. Processed in 0.106935 secs)
Received: from unknown (HELO ike.local.anstat.com.au) (202.92.123.11)
  by hermes.apache.org with SMTP; 21 May 2004 22:32:30 -0000
Received: by ike.local.anstat.com.au with Internet Mail Service (5.5.2655.55)
	id <LHGX1D9Z>; Sat, 22 May 2004 08:32:00 +1000
Message-ID: <7395B46C07F8D51182AE000629570CC4B2E5C5@ike.local.anstat.com.au>
From: Paul Smith <Paul.Smith@lawlex.com.au>
To: =?iso-8859-1?Q?=27Ceki_G=FClc=FC_=27?= <ceki@qos.ch>,
	'Log4J Developers List ' <log4j-dev@logging.apache.org>
Subject: RE: More chainsaw comments
Date: Sat, 22 May 2004 08:31:58 +1000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
List-Subscribe: <mailto:log4j-dev-subscribe@logging.apache.org>
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: hermes.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

 
> I love this. However, there is one usability issue. Assume you select
> the 
> first logger, by the time you want to select the second logger, the
> events 
> disappear leaving you with only the events of the first logger. Do you
> see 
> what I mean?

Remember that the filters are applied to an "unfiltered" list, so if you
remove the filter, all the hidden events come back.  So you can modify the
filter expression at any time and you won't 'lose' any events, unless they
get dumped as part of the cyclic buffer.

> Come to think of it, the ability to build up the expression is so
> powerful 
> that the Logger panel now looks like a distraction to me.

The logger three panel is not a powerful as the expression filtering, but
it's great for quick 'n dirty logger pruning from the view.  Both the Logger
panel and the expression filter work together, so you can filter by a logger
hierachy and then add a detail refinement in the expression.

Your point about not being able to focus on X distinct logger is
interesting.  I guess we could have 2 modes for the tree, and allow the user
to mark individual loggers that one is interested.  I will have more of a
think about this one.  

Thanks Ceki.

cheers,

Paul Smith

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