HTTP Request simplify UI
Hello, What do you think of using a JTabbedPane to simplify the UI. There would be a Basic Pane for usual parameters and an advanced one for those which are rarely used. I created https://bz.apache.org/bugzilla/show_bug.cgi?id=59129 with screenshots. -- Regards. Philippe
Re: HTTP Request simplify UI
Hi, I strongly support this idea. IMO, there are lot more fields that should go to Advanced: * Implementation * Redirect / Follow / Keep-alive flags * proxy server * timeout fields Andrey Pokhilko On 03/06/2016 12:39 AM, Philippe Mouawad wrote: > Hello, > What do you think of using a JTabbedPane to simplify the UI. > > There would be a Basic Pane for usual parameters and an advanced one for > those which are rarely used. > > > I created https://bz.apache.org/bugzilla/show_bug.cgi?id=59129 with > screenshots. >
Re: HTTP Request simplify UI
Hi, On Sunday, March 6, 2016, Andrey Pokhilko wrote: > Hi, > > I strongly support this idea. > > IMO, there are lot more fields that should go to Advanced: > > * Implementation > * Redirect / Follow / Keep-alive flags > * proxy server > * timeout fields > > I agree, but this needs more work. My proposal is a first step that can be done rapidly before 3.0. Moving the other fields requires moving those out of UrlConfigGui but maybe It can be done faster that what I think. > > Andrey Pokhilko > > On 03/06/2016 12:39 AM, Philippe Mouawad wrote: > > Hello, > > What do you think of using a JTabbedPane to simplify the UI. > > > > There would be a Basic Pane for usual parameters and an advanced one for > > those which are rarely used. > > > > > > I created https://bz.apache.org/bugzilla/show_bug.cgi?id=59129 with > > screenshots. > > > > -- Cordialement. Philippe Mouawad.
Re: HTTP Request simplify UI
In my head, Advanced include the Basic fields with more option than the basic. Perhaps, use another word for Advanced tab if it's contains only more options like your screenshot (like "Optional fields" or "More params"). In the 'advanced' tab, you have more space, it is not necessary to align horizontally Source address section and Optional Tasks. They can be align vertically only imho. On 06/03/2016 08:07, Philippe Mouawad wrote: Hi, On Sunday, March 6, 2016, Andrey Pokhilko wrote: Hi, I strongly support this idea. IMO, there are lot more fields that should go to Advanced: * Implementation * Redirect / Follow / Keep-alive flags * proxy server * timeout fields I agree, but this needs more work. My proposal is a first step that can be done rapidly before 3.0. Moving the other fields requires moving those out of UrlConfigGui but maybe It can be done faster that what I think. Andrey Pokhilko On 03/06/2016 12:39 AM, Philippe Mouawad wrote: Hello, What do you think of using a JTabbedPane to simplify the UI. There would be a Basic Pane for usual parameters and an advanced one for those which are rarely used. I created https://bz.apache.org/bugzilla/show_bug.cgi?id=59129 with screenshots.
Re: HTTP Request simplify UI
Hi, I strongly support this idea too And I can help to migrate some elements if it's easy Antonio 2016-03-06 9:24 GMT+01:00 Milamber : > > In my head, Advanced include the Basic fields with more option than the > basic. > > Perhaps, use another word for Advanced tab if it's contains only more > options like your screenshot (like "Optional fields" or "More params"). > > In the 'advanced' tab, you have more space, it is not necessary to align > horizontally Source address section and Optional Tasks. They can be align > vertically only imho. > > > > > On 06/03/2016 08:07, Philippe Mouawad wrote: > >> Hi, >> >> On Sunday, March 6, 2016, Andrey Pokhilko wrote: >> >> Hi, >>> >>> I strongly support this idea. >>> >>> IMO, there are lot more fields that should go to Advanced: >>> >>>* Implementation >>>* Redirect / Follow / Keep-alive flags >>>* proxy server >>>* timeout fields >>> >>> I agree, but this needs more work. >>> >> My proposal is a first step that can be done rapidly before 3.0. >> Moving the other fields requires moving those out of UrlConfigGui but >> maybe >> It can be done faster that what I think. >> >> Andrey Pokhilko >>> >>> On 03/06/2016 12:39 AM, Philippe Mouawad wrote: >>> Hello, What do you think of using a JTabbedPane to simplify the UI. There would be a Basic Pane for usual parameters and an advanced one for those which are rarely used. I created https://bz.apache.org/bugzilla/show_bug.cgi?id=59129 with screenshots. >>> >
Re: HTTP Request simplify UI
On Sun, Mar 6, 2016 at 9:24 AM, Milamber wrote: > > In my head, Advanced include the Basic fields with more option than the > basic. > No always, Firefox has advanced tab which only has advanced parameters. > > Perhaps, use another word for Advanced tab if it's contains only more > options like your screenshot (like "Optional fields" or "More params"). > > In the 'advanced' tab, you have more space, I agree, if I can proceed with this change, I will complete it by changing the advanced tab layout. But if there is opposition then I won't spend more time on it. > it is not necessary to align horizontally Source address section and > Optional Tasks. They can be align vertically only imho. Yes > > > > > On 06/03/2016 08:07, Philippe Mouawad wrote: > >> Hi, >> >> On Sunday, March 6, 2016, Andrey Pokhilko wrote: >> >> Hi, >>> >>> I strongly support this idea. >>> >>> IMO, there are lot more fields that should go to Advanced: >>> >>>* Implementation >>>* Redirect / Follow / Keep-alive flags >>>* proxy server >>>* timeout fields >>> >>> I agree, but this needs more work. >>> >> My proposal is a first step that can be done rapidly before 3.0. >> Moving the other fields requires moving those out of UrlConfigGui but >> maybe >> It can be done faster that what I think. >> >> Andrey Pokhilko >>> >>> On 03/06/2016 12:39 AM, Philippe Mouawad wrote: >>> Hello, What do you think of using a JTabbedPane to simplify the UI. There would be a Basic Pane for usual parameters and an advanced one for those which are rarely used. I created https://bz.apache.org/bugzilla/show_bug.cgi?id=59129 with screenshots. >>> > -- Cordialement. Philippe Mouawad.
Re: HTTP Request simplify UI
Philippe, what is the purpose of "Add/Del" buttons in basic panel of HTTP Sampler GUI? Is it really some "basic" stuff? Vladimir
Re: HTTP Request simplify UI
Hi Vladimir , this is not related to my change. It is part of : - https://bz.apache.org/bugzilla/show_bug.cgi?id=59083 Regards Philippe On Mon, Mar 7, 2016 at 11:44 AM, Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > Philippe, what is the purpose of "Add/Del" buttons in basic panel of > HTTP Sampler GUI? > > Is it really some "basic" stuff? > Vladimir > -- Cordialement. Philippe Mouawad.
Re: HTTP Request simplify UI
I wonder if that can be split to "advanced" tab somehow. I bet typical users do not invent HTTP methods often. Is that Add/Del specific to a particular sampler? Does it make sense to make it global, so it does not clutter UI of each HTTP sampler? Vladimir
Re: HTTP Request simplify UI
Hi, Yes . I even think that in fact there should be in a new "Config" component that holds cross samplers configuration, (or maybe but this can be harder to manage (see below), it should be in HTTPRequest Defaults advanced tab) Doing so would allow us to check that Deletion of 1 method is fine, it would check in All HTTP Samplers that the method is not used and inform user / refuse the deletion. I think it is more a Cross configuration setting. Regards On Mon, Mar 7, 2016 at 12:35 PM, Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > I wonder if that can be split to "advanced" tab somehow. > I bet typical users do not invent HTTP methods often. > > Is that Add/Del specific to a particular sampler? > Does it make sense to make it global, so it does not clutter UI of > each HTTP sampler? > > Vladimir > -- Cordialement. Philippe Mouawad.
