You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by "BAZLEY, Sebastian" <Se...@london.sema.slb.com> on 2003/12/17 12:24:35 UTC

Save/load menu item suggestions

I've found (some of) the discussion about Save/Load menu items, which had
already been recorded in Bugzilla:

http://issues.apache.org/bugzilla/show_bug.cgi?id=23780

To summarise, the suggestion was to have the following functionality:

1) Clear the existing test plan, after prompting to save it

This is the current New behaviour.
It would be better to rename this as "Close", as it does not create a New
plan.

2) Read a file into the existing tree

This is the current Open behaviour, but it would be better to name it
"Merge".

3) Clear plan (prompt to save) and read new test plan.

This is new functionality, which could be called "Open".
However, Open currently does something different, so it might be better to
use a different name.

New could be resurrected later if multiple test plans were to be supported.

OK?

Sebastian

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


Re: Save/load menu item suggestions

Posted by Sebastian Bazley <Se...@london.sema.slb.com>.
These have been implemented:

New has been replaced by Close. This means that ^N no longer works; I replaced it with ^L. This can be changed.

Open (which was implemented in Load.java) now calls close before loading the file.

A new Merge menu option has been added (this is the old Load code).

Hope they're OK ...

S.

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


Re: Save/load menu item suggestions

Posted by peter lin <jm...@yahoo.com>.
 I would also vote to keep Open as the current behavior. Close makes sense to me, so + on that.
 
peter


Jordi Salvat i Alabart <js...@atg.com> wrote:
I would still leave "Open" for prompt-clear-read -- since that's what is 
costumary in most other programs. Existing users will only be (slightly 
and gratefully) surprised the first time. If/when we implement multiple 
test plan editing we will just need to remove the prompt-clear phase.

I would not bother to keep a "Merge" -- although it doesn't harm much 
with that name. It's functionality would not be obvious, even worse if 
we supported opening multiple test plans. Plus it's already handled at 
the pop-up/edit menu level.

Backward compatibility is nice to keep, but should not become a 
roadblock when the old stuff is so poor. And you must admit that the GUI 
is probably the poorest area of JMeter -- which is not too surprising 
since JMeter users (and hence JMeter developers) are mostly server-side 
people.

-- 
Salut,

Jordi.


En/na BAZLEY, Sebastian ha escrit:
> I've found (some of) the discussion about Save/Load menu items, which had
> already been recorded in Bugzilla:
> 
> http://issues.apache.org/bugzilla/show_bug.cgi?id=23780
> 
> To summarise, the suggestion was to have the following functionality:
> 
> 1) Clear the existing test plan, after prompting to save it
> 
> This is the current New behaviour.
> It would be better to rename this as "Close", as it does not create a New
> plan.
> 
> 2) Read a file into the existing tree
> 
> This is the current Open behaviour, but it would be better to name it
> "Merge".
> 
> 3) Clear plan (prompt to save) and read new test plan.
> 
> This is new functionality, which could be called "Open".
> However, Open currently does something different, so it might be better to
> use a different name.
> 
> New could be resurrected later if multiple test plans were to be supported.
> 
> OK?
> 
> Sebastian
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
> 
> 


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


---------------------------------
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing

Re: Save/load menu item suggestions

Posted by Jordi Salvat i Alabart <js...@atg.com>.
I would still leave "Open" for prompt-clear-read -- since that's what is 
costumary in most other programs. Existing users will only be (slightly 
and gratefully) surprised the first time. If/when we implement multiple 
test plan editing we will just need to remove the prompt-clear phase.

I would not bother to keep a "Merge" -- although it doesn't harm much 
with that name. It's functionality would not be obvious, even worse if 
we supported opening multiple test plans. Plus it's already handled at 
the pop-up/edit menu level.

Backward compatibility is nice to keep, but should not become a 
roadblock when the old stuff is so poor. And you must admit that the GUI 
is probably the poorest area of JMeter -- which is not too surprising 
since JMeter users (and hence JMeter developers) are mostly server-side 
people.

-- 
Salut,

Jordi.


En/na BAZLEY, Sebastian ha escrit:
> I've found (some of) the discussion about Save/Load menu items, which had
> already been recorded in Bugzilla:
> 
> http://issues.apache.org/bugzilla/show_bug.cgi?id=23780
> 
> To summarise, the suggestion was to have the following functionality:
> 
> 1) Clear the existing test plan, after prompting to save it
> 
> This is the current New behaviour.
> It would be better to rename this as "Close", as it does not create a New
> plan.
> 
> 2) Read a file into the existing tree
> 
> This is the current Open behaviour, but it would be better to name it
> "Merge".
> 
> 3) Clear plan (prompt to save) and read new test plan.
> 
> This is new functionality, which could be called "Open".
> However, Open currently does something different, so it might be better to
> use a different name.
> 
> New could be resurrected later if multiple test plans were to be supported.
> 
> OK?
> 
> Sebastian
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
> 
> 


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