I decided to create a subclass of PRPierFrame to start a new site.
The only thing I overrode from PRPierFrame is the class method
createInvironemntFor:. I remove the view widget, and reordered the
other two on the left side of the display. I then initialized this
new class, gave it a new kernel name and root, and opened it up.
It displayed as I had expected it to.
If you browse to "/Environment" -- a special hidden page (sort of a
meta-page) being used to layout Pier -- you are able to configure
your application from the web without the need of subclassing.
Problem is, the existing pier app now displays the new structure
too. Why is this? Are some Pier classes singletons?
"PRKernel instances" answers a collection of registered Pier
instances. I do not take the assumption that there is just one
instance, it is fine to run multiple kernels in one image.
When browsing to the Seaside config interface you are able to select
the kernel you want to use for your application (see screenshot
below). You might have multiple instances using the same kernel.
PRMacroExpander and MACachedBuilder are the only singletons that come
into my mind right now.