Hernan Tylim wrote:

> 
> Just store the proxy settings as preferences, but use your own ui to 
> interact with them[*].  In this way you can use a UI that will adjust to 
> your needs, but also it will allow experienced users to access the proxy 
> settings from a Browser (besides you get all the other Preference 
> features like persistence (the save to disk option) and project localness).
> 

Understand.

> But the point you mention about an end user is a very interesting one. 
> For that kind of user I want to develop an special mode of work of the 
> PreferenceBrowser.
> 
> This feature will allow developers to re-use the PreferenceBrowser 
> interface to manage their settings instead of doing its owns. This would 
> work by customizing what categories and preferences to show and making 
> possible to invoke the Preference Browser as a modal dialog from your 
> application.
> 

Exactly about something like this I was thinking when your mail arrived. 
While I was playing with Categories from your Preferences Browser I was 
imagining filtering them to use as you says.

> I don´t think this is hard to do but is far away on my priority list at 
> the moment.
> 
> *- See at the class Preferences the "add" and "get/set" method 
> categories. Instead of storing the proxy settings as instance variables 
> use getters/setters that will use Preferences to get/set the values.
> 

Thanks again.