Merging

Hi Keith, I am trying to merge all your changes, though I see some problems in Pier. For Magritte all your code should be merged in now. 1. Pier-Security-kph.40 - Pier-Security-kph.40 adds several cool widgets to Pier to add, create and edit users and groups. I do not properly understand why these are widgets and not commands? This means that I need a special place inside Pier where I add those widgets to be able to use them somewhere protected? Why not transform them into commands, so that they can also be properly logged with the persistency framework? Maybe provide a special Meta-Command that displays a special administrator interface to be able to trigger those commands without cluttering up the command interface with 10 new commands? 2. Your new persistency mechanisms looks cool. Does it work yet? How is the performance? I am especially interested into the Magma implementation. Your changes add a lot of external dependencies, why not put the new persistency mechanisms into their own packages? People could load then Pier-Magma if they want to use Magma or Pier- XML if they want XML persistency. Just my cents ;-) Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch