Hi all Here is a call for good design sharing. I already posted a mail on that design issue but I want to restate it. I really want in the future to be able to remove Preferences (we need preferences but not the way they are). right now when I'm LittApp an application and run my little flow I will suddenly invoke the HUGE Global center (Preferences) to see what **I** have to do.... So at the end of the day we got, debugger, compiler, Morphic.... depending on preferences and this is WRONG. What we should have (illustrated really well with the MC sorting menu) is LittApp is responsible for its own preferences So it runs, and check **Itself**: "oh how should I behave, let me see ***my own*** state tell me to turn right, to be novice friendly... and I do it. Notice how little application does NOT reference to the HUGE Preference Global Now the BIG Preferences setter will just change the configuration of the little app. Preferences>>sortingLittleApp LittleApp sortTop Now of course, littApp could be a bit smarter and say BIGPreferenceSetter here are my preferences we could use pragmas to define preferences that BIGPreferences would gather and present to the user. Stef