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 <[email protected]>: > 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 >
