[Seaside] Re: Problems with expire in Seaside

[Andreas Nilsson]

Well, then I guess it's all about design goals.
It is a lot easier to just hook up a plugin or event handler than it is 
to override classes.
Overriding a class just to hook up an event is a bit like the good old 
days of GUI toolkits where you had to override buttons to make them do 
something when clicked ;)

/Adde

On 2004-09-02, at 00.30, Avi Bryant wrote:

>
> On Sep 2, 2004, at 12:22 AM, Andreas Nilsson wrote:
>
>> Is there any way to override the expire-screen / behaviour in the 
>> current framework?
>> That's the only advantage i can see with the Forwarder solution.
>
> Sure, just subclass WAApplication and override #handleExpiredRequest:. 
>  Changing the application class used is somewhat inconvenient, and has 
> to be done programmatically rather than through the config app - trace 
> through #registerAsApplication: to see how.  But shouldn't be a huge 
> deal.
>
> Avi
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside