Return-Path: X-Original-To: apmail-jmeter-dev-archive@minotaur.apache.org Delivered-To: apmail-jmeter-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B09D19DD8 for ; Mon, 23 Jan 2012 19:57:24 +0000 (UTC) Received: (qmail 16117 invoked by uid 500); 23 Jan 2012 19:57:24 -0000 Delivered-To: apmail-jmeter-dev-archive@jmeter.apache.org Received: (qmail 16077 invoked by uid 500); 23 Jan 2012 19:57:24 -0000 Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jmeter.apache.org Delivered-To: mailing list dev@jmeter.apache.org Received: (qmail 16069 invoked by uid 99); 23 Jan 2012 19:57:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jan 2012 19:57:23 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of philippe.mouawad@gmail.com designates 209.85.210.171 as permitted sender) Received: from [209.85.210.171] (HELO mail-iy0-f171.google.com) (209.85.210.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jan 2012 19:57:17 +0000 Received: by iaeh11 with SMTP id h11so3847055iae.2 for ; Mon, 23 Jan 2012 11:56:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=vJlhaqtpMI4iXkD18xqzuD9g7vN1wkiuTzHA0yqQDcs=; b=G+80up08P2KOVNgsgVrlP3iEmGmUoSiw7LPmpsSkCpkgkwfi1pCK+GN5ujis3ppc+r p8NJHjjXhaYQ7kDnjbOYU7oeV1y6gZg1VZ6gwljaSFzmNs3Ehn9Rudph6MSbs8gms2Mq LV+JKSleyPXYNkyt0rK5Mw0VDMh7+iH84yAMc= MIME-Version: 1.0 Received: by 10.50.89.197 with SMTP id bq5mr11365092igb.24.1327348617057; Mon, 23 Jan 2012 11:56:57 -0800 (PST) Received: by 10.231.19.135 with HTTP; Mon, 23 Jan 2012 11:56:56 -0800 (PST) In-Reply-To: References: Date: Mon, 23 Jan 2012 20:56:56 +0100 Message-ID: Subject: Re: New Logger Panel From: Philippe Mouawad To: dev@jmeter.apache.org Content-Type: multipart/alternative; boundary=e89a8f3ba75fd014fa04b7376e06 --e89a8f3ba75fd014fa04b7376e06 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Jan 23, 2012 at 8:14 PM, sebb wrote: > On 23 January 2012 17:52, Philippe Mouawad > wrote: > > On Mon, Jan 23, 2012 at 5:18 PM, sebb wrote: > > > >> On 23 January 2012 15:34, Philippe Mouawad > >> wrote: > >> > Hello, > >> > My answers below. > >> > > >> > On Mon, Jan 23, 2012 at 3:51 PM, sebb wrote: > >> > > >> >> The Logger panel is useful, but I really don't like the way it is > >> >> added to every single GUI pane. Is that really intentional? > >> >> > >> > > >> > Can you explain what you mean ?. > >> > Today LoggerPanel is initialized at creation of MainFrame and not > every > >> > time you open a Test Plan. > >> > >> Start JMeter (Gui mode) > >> > >> Select Test Plan, then Workbench. > >> No logger panel showing in either. > >> > >> Check Options/Logviewer > >> > >> Now both Workbench and Test Plan have the logger panel. > >> Same applies to any other Gui screens. > >> > >> Yes it's intentional, because when I test a plan I want the console > view > > to be always here. It's like the console in Eclipse. > > It is in MainFrame. > > I still not see what you would like to have. > > I think it looks wrong for every GUI to have a console panel at the bottom. > Some GUIs are already very full, and adding the console view means the > rest of the Gui will need to be scrolled. > > I don't have the same opinion, when you write a script, you usually have a TreeView result and you click on failed sampler then look at response and then look in the logs if there is an error. As it is shown in Milamber screenshot. Regarding the place taken, you always have the option to click on divider at left to minimize window. Finally, LoggerPanel is independant of GUIs in term of implementation . > Either have a single panel, for example on the Workbench Gui - or even > a new Gui - or have a floating panel that can be visible independently > of the existing Guis. > > I must still say I don't see what you would like, maybe a screenshot on the Bugzilla will help me understand. >> > >> >> Also at present, disabling the option does not appear to release the > >> >> memory, because the same contents are redisplayed when re-enabled. > >> >> > >> >> Ok with this, I'll fix it this evening. > >> > > >> > It might make more sense to add it to the workbench GUI. > >> >> This could then provide options to clear/refresh/reload/change size > etc. > >> >> > >> > These are already handled in current implementation ? > >> > >> No, they are not, at least not at run-time. > >> > > > > I am not sure to see what you are want, but if you are talking about menu > > options to clear, refresh , change size, well I imagined the same > behaviour > > as Eclipse console, with some icons to clear. > > > > > >> > >> > > >> > > >> > -- > >> > Cordialement. > >> > Philippe Mouawad. > >> > > > > > > > > -- > > Cordialement. > > Philippe Mouawad. > -- Cordialement. Philippe Mouawad. --e89a8f3ba75fd014fa04b7376e06--