[Bug 64287] WhileController: Improve UX

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=64287

Philippe Mouawad <p....@ubik-ingenierie.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |FixedInTrunk
             Status|NEW                         |RESOLVED
                 CC|                            |p.mouawad@ubik-ingenierie.c
                   |                            |om
         Resolution|---                         |FIXED

--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
This is an automated email from the ASF dual-hosted git repository.

pmouawad pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/jmeter.git

commit 510c92fe736b29325625e8d3bb0698676e0ffffb
Author: pmouawad <p....@ubik-ingenierie.com>
AuthorDate: Sun Mar 29 22:11:17 2020 +0200

    Bug 64287 - WhileController: Improve UX
---
 .../jmeter/control/gui/WhileControllerGui.java     | 27 +++++++---------------
 xdocs/changes.xml                                  |  1 +
 2 files changed, 9 insertions(+), 19 deletions(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Re: [Bug 64287] WhileController: Improve UX

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

Philippe,

Thanks for doing the cleanup. I deliberately refrained from touching
individual components :)


However, can you please clarify what is the value of those one-time
Bugzilla issues?
They do appear in the email notifications, so they produce some noise.
Later the end-users would crawl over the fixed bugs listed in the
changelog, and they will not know if the bug is a true one or if it is an
empty one.
So these "empty Bugzilla entries" distract both developers and the
end-users :-/
I guess we should commit small UX changes without creating Bugzilla tickets.

On the other hand, it would be great to have screenshots (e.g. in the
changelog) for the changes.
That would be more valuable for the end-users, so they would learn how it
works.

PS. Some of the components you edit have significant padding around the
panel.
For instance, While Controller has significant padding for "Conditition
(function or variable)" field.
I guess we should stick to the following:
1) If a component contains just a set of fields, then padding should be
minimal (e.g. like in Debug Sampler where the component panel has no
padding around)
2) If there are titled panels, then the padding should be there. For
instance, Thread Group has two titled panels, so the contents of the panels
is padded.

Vladimir