Pier pointers

I have an existing seaside application that I would like to port into  
the Pier framework, and need some pointers :)


1. I store some things on session; what is the Pier equivalent?

2. Do I have to move my renderContentOn: methods to renderWidgetOn:?

3. Should I subclass MAComponent  or PRViewComponent or something  
entirely different?


Thanks!

Brian
(I've looked on the pier Wiki and read the FAQ and have got a minimal  
grasp of Magritte (and am using it in a non Pier context), but I  
haven't found any developer getting started type documentation)

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Hi Brian,

I can't answer your question. Before, I need to know why you want to
use Pier for. How will you benefit from Pier?

Then, what do you want to keep in your application?

You have to know that Seaside component can be integrated into Pier
without any change.

2007/7/26, Brian Brown <[hidden email]>:

--
Damien Cassou

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

> 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://
www.lukas-renggli.ch/smalltalk/pier/videos/sushi.mov

> 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  
into troubles.

> 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
> entirely different?

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,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch



_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki