POSTER window
==============
1) Save current poster values in a named profile.
Users now can save the current poster values (URL, authorization values,
timeout, content type, content, file name, headers, parameter values,
the lot) as a named profile entry. These values later can be reloaded,
saved under a different name or deleted.
2) Reorganised the Actions section of the poster UI.
Added "Content Body", "Parameters" and "File Content" radio boxes. User can
select the method (e.g POST) and the content choice (content body, name
value pairs, file content). This may clear up the confusion as to how
to use the Parameters tab. If you want to post parameters, choose the
Parameters radio button and add name value pairs then post. No need to go
to the "Content to Send" tab and press "Parameter Body" button. When user
selects an action they want to perform only the options that make sense for
that action are enabled. E.g to do a GET while using file content does't
make sense.
3) User changeable font size
Added Ctl +, Ctl -, Ctl 0 key shortcuts to window to
increase/decrease/reset the font size of the window elements. These
values are saved. After resizing a window, its current window dimensions
are saved as well. Also available for the Response UI.
4) Starting new Poster instance
Added a button to the Poster UI to open a new instance of the Poster from
there without having to have the main browser window open.
RESULT window
=============
1) Syntax highlight XML response
Server reponse can be viewed in syntax highlighted and indented X(HT)ML or
in raw format.
2) Moved headers to separate tab to give make more room.
Minor bug fixes, new features:
=============================
1) Made Poster window minimizable
2) After timout is reached the request is now aborted
3) Fixed PROFIND typo
4) Added simple URL validation to prevent the horrible
"(NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]" error message
to pop up.
5) When clicking a Header or Parameter row, display selected values in the
name value text boxes.
Original issue reported on code.google.com by a...@milowski.com on 26 Sep 2011 at 2:42
Original issue reported on code.google.com by
a...@milowski.com
on 26 Sep 2011 at 2:42Attachments: