Submenus for JMeter elements

[Vincent HERILIER <vh...@gmail.com>]

Hi,

First, thanks to all of you for your work on JMeter.

Maybe I'm re-opening a discussion thread about the need of submenus to
handle JMeter elements but when several plugins are developed around
JMeter, it is difficult to manage, organise, find the related
config/sampler/... elements into the native ones.
Introducing submenus will increase the user friendly aspect of JMeter.

Like in the Bugzilla#39937(
https://bz.apache.org/bugzilla/show_bug.cgi?id=59937) , I was wondering
about the use of a similar method like getMenuCategories() to introduce a
sub level into the menu tree.

IMHO, it is a real need (not only for myself).
But, accordingly to you, how could it be considered ?

Thanks and regards

Vincent

Re: Submenus for JMeter elements

[sebb <se...@gmail.com>]

On 31 August 2016 at 10:09, Vladimir Sitnikov
<si...@gmail.com> wrote:
> Andrey>That's why I used "label prefix" approach to visually
> group plugins of "jp@gc"
> Andrey>It serves the purpose of grouping without
> introducing new menu levels.
>
> jp@gc makes it hard to read.
+1
> Nothing personal, but I'm always reading jp@gc as something like *(╯°□°）╯︵
> ┻━┻*
>
> The idea of enabling plugin to specify which particular submenu it wants to
> enhance is well-established in IDE world: IDEA, Eclipse, MPS, etc, etc.
>
> If compare "one menu of 100 items" and "3-4 deep menu", I would prefer "3-4
> deep menus" provided they are searchable and properly organized.

That depends on what the menu contains.
For example, a menu to select a country code is probably better
organised as a single level.

> Vladimir

Re: Submenus for JMeter elements

[Vincent HERILIER <vh...@gmail.com>]

Andrey> I was using a same kind of way but it works only for conscious
users in my case - that's why I'm looking for a more user friendly approach
Andrey, Vladimir> at least only one sub level may be enough

Vincent

2016-08-31 11:09 GMT+02:00 Vladimir Sitnikov <si...@gmail.com>:

> Andrey>That's why I used "label prefix" approach to visually
> group plugins of "jp@gc"
> Andrey>It serves the purpose of grouping without
> introducing new menu levels.
>
> jp@gc makes it hard to read.
> Nothing personal, but I'm always reading jp@gc as something like *(╯°□°）╯︵
> ┻━┻*
>
> The idea of enabling plugin to specify which particular submenu it wants to
> enhance is well-established in IDE world: IDEA, Eclipse, MPS, etc, etc.
>
> If compare "one menu of 100 items" and "3-4 deep menu", I would prefer "3-4
> deep menus" provided they are searchable and properly organized.
>
> Vladimir
>

Re: Submenus for JMeter elements

[Vladimir Sitnikov <si...@gmail.com>]

Andrey>That's why I used "label prefix" approach to visually
group plugins of "jp@gc"
Andrey>It serves the purpose of grouping without
introducing new menu levels.

jp@gc makes it hard to read.
Nothing personal, but I'm always reading jp@gc as something like *(╯°□°）╯︵
┻━┻*

The idea of enabling plugin to specify which particular submenu it wants to
enhance is well-established in IDE world: IDEA, Eclipse, MPS, etc, etc.

If compare "one menu of 100 items" and "3-4 deep menu", I would prefer "3-4
deep menus" provided they are searchable and properly organized.

Vladimir

Re: Submenus for JMeter elements

[Andrey Pokhilko <ap...@ya.ru>]

Hi,

My opinion, the deep nested popup menus is bad UX. It's tedious to find
elements in them. That's why I used "label prefix" approach to visually
group plugins of "jp@gc". It serves the purpose of grouping without
introducing new menu levels.

Andrey Pokhilko

On 08/31/2016 11:42 AM, Vincent HERILIER wrote:
> Hi,
>
> First, thanks to all of you for your work on JMeter.
>
> Maybe I'm re-opening a discussion thread about the need of submenus to
> handle JMeter elements but when several plugins are developed around
> JMeter, it is difficult to manage, organise, find the related
> config/sampler/... elements into the native ones.
> Introducing submenus will increase the user friendly aspect of JMeter.
>
> Like in the Bugzilla#39937(
> https://bz.apache.org/bugzilla/show_bug.cgi?id=59937) , I was wondering
> about the use of a similar method like getMenuCategories() to introduce a
> sub level into the menu tree.
>
> IMHO, it is a real need (not only for myself).
> But, accordingly to you, how could it be considered ?
>
> Thanks and regards
>
> Vincent
>

Re: Submenus for JMeter elements

[Vincent HERILIER <vh...@gmail.com>]

Accordingly to my own usecases, I didn't consider finding elements by this
way, but why not...
My purpose is more about grouping elements around protocol related sets or
plugin related.

Considering a getSubMenuCategories() method like the getMenuCategories()
does for config/samplers/..., it could a way to introduce one or more names
to group elements under their kind category. if it not set (empty for
example) related element may stay at the top kind category.
for BeanInfo made elements, the shortDescription could be hijacked to set
the submenu categories.

Vincent


2016-08-31 10:53 GMT+02:00 Vladimir Sitnikov <si...@gmail.com>:

> Vincent>find the related
> Vincent>config/sampler/... elements into the native ones.
>
> Just in case: do you mean "quick search" makes sense?
> For instance: allow whatever grouping that makes sense, however enable
> quick search of the elements when user opens menu and starts typing.
>
> I think a plugin should expose "desired submenu name" and JMeter should
> just group that accordingly.
> I don't think JMeter can figure out proper submenu names on its own.
>
> Vladimir
>

Re: Submenus for JMeter elements

[Vladimir Sitnikov <si...@gmail.com>]

Vincent>find the related
Vincent>config/sampler/... elements into the native ones.

Just in case: do you mean "quick search" makes sense?
For instance: allow whatever grouping that makes sense, however enable
quick search of the elements when user opens menu and starts typing.

I think a plugin should expose "desired submenu name" and JMeter should
just group that accordingly.
I don't think JMeter can figure out proper submenu names on its own.

Vladimir