Active Settings refactoring done

[Marco Martin]

On Tuesday 03 January 2012, Thomas Pfeiffer wrote:
> Application-specific dialogs can also be accessed from the application
> using a button or menu entry.
> - If the application window is clearly separated into a navigation and a
> content area (like in a web browser) and has a starting page from which the
> user can navigate to different content, a button is placed on that starting
> page which navigates to the configuration "page", which is displayed inline
> in the content area
> - In all other cases, the configuration dialog is placed fullscreen above
> the application.

this seems just to describe the exact case of the browser because it's already 
there, isn't it ? ;)

so, what we need in the end, is a way that is consistent and recognizable to 
invoke config dialogs from the apps
and a guideline to say when this should and shouldn't be done.

as sebas notes should be something not too detailed, since should be an easy 
guideline (so that maybe somebody actually reads it :p)

so what could make sense would be things like 
* what component to use for the button, that is always the same icon/button is 
important
* places to put it: does the app has a toolbar? has it a screen that is not 
always there?
* cases when that button shouldn't exist

if, all of that can be kept simple enough..

Cheers,
Marco Martin