[Seaside] WAComponent class>>applicationClass fix
philippe.marschall at gmail.com
Sat Jun 30 16:16:57 UTC 2007
2007/6/29, Boris Popov <boris at deepcovelabs.com>:
> Looks like #applicationClass wasn't called anymore to allow subclasses
> to override the application, so changed hardcoded WAApplication to a
> call site here,
> applicationNamed: aString
> | application |
> application := self applicationClass named: aString.
> application configuration addAncestor: WARenderLoopConfiguration new.
> application preferenceAt: #rootComponent put: self.
> This is based on VisualWorks 2.7b1.5.1, it might be fixed in the Squeak
> stream already.
This is not the case. I remember having seen this patch before but we
rejected it because we saw no need tying a component to an application
and for subclassing applications. Can you elaborate what you need
application subclasses for?
> DeepCove Labs Ltd.
> 4th floor 595 Howe Street
> Vancouver, Canada V6C 2T5
> boris at deepcovelabs.com
> CONFIDENTIALITY NOTICE
> This email is intended only for the persons named in the message
> header. Unless otherwise indicated, it contains information that is
> private and confidential. If you have received it in error, please
> notify the sender and delete the entire message including any
> Thank you.
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the Seaside