I have an existing seaside application that I would like to port
into the Pier framework, and need some pointers :)
I am sure you saw the video 'Embedding Seaside Application' at http://
1. I store some things on session; what is the Pier equivalent?
<background-information>The problem when using sessions is that they
are global and introduce a tight coupling between your application/
components and the session. If you want to combine different
components that expect different sessions you are screwed up. Of
course Pier (or Seaside) could fake different Sessions per component
(if necessary) but it doesn't at the moment.</background-information>
Exactly for the reasons given above, Pier doesn't use the Seaside
session. Just tell your Pier application configuration to use your
own Session class and proceed as shown in the Video. You application
will be the only one to bother about the session so you shouldn't run
2. Do I have to move my renderContentOn: methods to renderWidgetOn:?
No, in the latest versions #renderWidgetOn: is not used anymore. Pier
uses #renderContentOn: like any other component.
3. Should I subclass MAComponent or PRViewComponent or something
Not necessarily, unless you want to use some of the convenience
methods provided by Pier. A normal subclass of WAComponent does just
fine in most cases.
Hope this helps,