Hi Keith, no sorry, I didn't had the time to look at or merge it yet. Indeed this it is a bit difficult, since you changes to PRPierMain break all my productive applications. Also I have some problems with the way you write code: Personally I pay a lot of attention to the way the source is formatted, especially that it is properly indented, that there are no unnecessary statements or brackets. Especially that it is readable, nice looking and well fitting with the existing code. I started to like the approach with the widgets and worked on that. In fact, my initial concerns were certainly not valid. The latest changes I committed came all from the requirements when setting up a new productive server for a lecture here in Bern. For a productive setup behind Apache there is no access to the configuration application from outside the local network anyway. How would you change the settings then? I started from your code and extended it and added a superclass to share some functionality. Just lately I also added a browse view to navigate around the structures and to have an overview of the permissions, users and groups (like the unix ls -la). Mhh, this certainly does not work, since the component is called outside the scope of the dynamic-variable. Thus it should work if you move the dynamic-variable outside the call: openWidget: widget titled: title PRCurrentContext use: self during: [ self call: (widget context; addDecoration: (WAWindowDecoration new title: title; yourself); yourself) ] Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch