On 22/03/07, Alf Høgemark <[EMAIL PROTECTED]> wrote:
Hi
I'm hoping to enhance the HTTP Request sampler, by adding functionality to
support multipart/form-data http post request with only parameters, if the user
selects to do that. And also add support for uploading several files in one HTTP
request. There are also other bugzilla entries which might very well require
more
options in the HTTP Request gui.
Agreed.
I feel that in order to be able to add more options for the user for HTTP
Request, the GUI needs to be restructured. I think it should be easy and simple
for normal users, who I guess only are doing "HTTP GET" requests. But it must
also have room for options for more advanced users, i.e. doing HTTP Post with
many files.
Agreed.
I suggest to have the upper part of the GUI as it is now, but to change the
lower part to use a tabbed pane layout. I suggest tabs such as "options",
"parameters", "file upload".
Do you think it makes sense to restructure the GUI in this way ?
Mostly OK except I think the parameters need to be on the default
screen, not in a tab that is hidden by default.
The Web Server section could be reduced to one line; this would then
allow for the Redirects/Keep Alive checkboxes to be kept on the main
page.
The parameters could then be the main tab, and other items relegated
to a second tab.
Secondly, do you have any opinion on how much effort it would be to
restructure the GUI and the code like I suggest, and still being able to read
old test plans and populate the
GUI correctly.
Restructuring the GUI is tedious, but need not cause any problems for
old test plans.
It is important not to change any of the test plan property names, and
to make sure that all the properties are copied to/from the test
element as needed.
But the placement of the items on the GUI need not affect this.
If you don't like my suggestion for restructuring the GUI, how do you think we
can add more options to this already quite crowded GUI ?
Given that re-organising the GUI is fairly tedious, perhaps it would
be sensible to produce some mock-ups to decide on the layout first?
I think this is fairly easy to do in some of the Java IDEs - both
Netbeans and Eclipse have some facilities for doing this, though I've
not looked at either lately.
[I'm not suggesting using the generated code in JMeter; just using the
IDE as a Swing drawing program to try out layouts.]
Does that sound a sensible approach?
S
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
