UI improvements

[GoogleCodeExporter]

1) If I type the beginning of a content-type and then open the combo-box it
should position itself at the strings starting with my prefix.

2) I should be able to use application/xml without a charset argument
(because the xml already specifies its own charset).

Original issue reported on code.google.com by gili.tza...@gmail.com on 26 Nov 2008 at 10:17

[GoogleCodeExporter]

For (1): I agree on this. I wanted to do this for easing my own pain. But 
during the
initial search, I was not able to find easy to use Swing library/API for this. 
I will
do more search.

(2): This is a difficult question. Because it is always better to send charset
details in HTTP header irrespective of the HTTP payload mentioning it. Probably 
what
I can do is let the user choose the default Charset and encoding to be set when
starting RESTClient. This will ease the experience of setting it after each 
re-launch.

Original comment by subwiz on 27 Nov 2008 at 6:25

• Changed state: Accepted

[GoogleCodeExporter]

Thing is, you pretty much have to provide an encoding for XML documents because 
they
can exist outside of HTTP. Once you mandate that the document has an encoding it
makes little sense to provide it in the HTTP envelope. You don't want to risk
potential conflict between the two. Technically speaking, if the HTTP charset 
and xml
document encoding disagree the HTTP charset is supposed to win out. Needless to 
say
this confuses many people.

Anyway, this is why I mandate in my protocols that the XML documents have 
encodings
but the HTTP envelop must not.

Original comment by gili.tza...@gmail.com on 27 Nov 2008 at 6:31

[GoogleCodeExporter]

This might be what you're looking for:
http://javadesktop.org/swinglabs/build/weekly/latest/swingx-HEAD/javadoc/org/jde
sktop/swingx/autocomplete/AutoCompleteComboBoxEditor.html

Also, consider using a newer L&F such as Nimbus or Substance. I don't feel too
strongly on this point but it couldn't hurt :)

Original comment by gili.tza...@gmail.com on 27 Nov 2008 at 6:51

[GoogleCodeExporter]

Thanks for pointing me to the jdesktop autocomplete package. Let me see if this 
will
help us.

Original comment by subwiz on 27 Nov 2008 at 7:17

[GoogleCodeExporter]

Autocomplete feature has been made. Rev. 337 has the fix. I'm closing this 
issue. I
will open a new issue for L&F suggestion.

On the issue of HTTP header having charset, I believe it is essential. 
Probably, what
I will do is when Charset is not specified, I will remove `charset=' from 
getting
generated.

Original comment by subwiz on 27 Nov 2008 at 2:12

• Changed state: Fixed

[GoogleCodeExporter]

http://code.google.com/p/rest-client/issues/detail?id=76

This is the L&F issue.

Original comment by subwiz on 27 Nov 2008 at 2:20