Dear All,
The idea of "helpers" is to add plug-in functionality to Seaside in a way which is orthogonal to the conventional (and somewhat overloaded) means of extension via subclassing WASession et al to provide specialized facilities. Helpers are provided in the same manner as other Plug-Ins in Seaside, by providing subclasses of WAHelper and WASessionHelper. Helpers may simply be "enabled" in the configuration interface for each application. I have been using helpers for a while in my apps. I have two types of helpers. Rendering Helpers and Session Helpers. Rendering Helpers: (so far) 1. WAKeepAliveHelper for keeping the session alive while the users browser is open. I find this totally indispensable. 2. ShoreHelperHelper which allows you to use ShoreComponents without a specialized RootClass. Session Helpers: (so far) 1. Announcements Helper for Lukas' Announcements framework (in the blue corner) 2. AXAnnouncements Helper for Levente Uzonyi's AXAnnouncements framework (in the red corner) 3. CometHelper for Comet. 4. MagmaHelper for Magma. The "Helper" portion of Jetsam is entirely self contained, so can be distributed separately and if you find it useful I think it could be a candidate 2.9 If anyone has any ideas for additional helpers then please let me know. best regards Keith _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
I forgot to mention that the helpers interface adds the ever useful.
WASession-#properties Although I dont add the ususal propertyAt: accessors since I think the IdentityDictionary returned has standard enough behaviour so as not to need to overload the session class too much. Keith _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by keith1y
2007/10/27, Keith Hodges <[hidden email]>:
> Dear All, > > The idea of "helpers" is to add plug-in functionality to Seaside in a way which is orthogonal to the conventional (and somewhat overloaded) means of extension via subclassing WASession et al to provide specialized facilities. > > Helpers are provided in the same manner as other Plug-Ins in Seaside, by providing subclasses of WAHelper and WASessionHelper. Helpers may simply be "enabled" in the configuration interface for each application. > > I have been using helpers for a while in my apps. I have two types of helpers. Rendering Helpers and Session Helpers. > > Rendering Helpers: (so far) > > 1. WAKeepAliveHelper for keeping the session alive while the users > browser is open. I find this totally indispensable. > > 2. ShoreHelperHelper which allows you to use ShoreComponents without a specialized RootClass. > > Session Helpers: (so far) > > 1. Announcements Helper for Lukas' Announcements framework (in the blue corner) > 2. AXAnnouncements Helper for Levente Uzonyi's AXAnnouncements framework (in the red corner) > 3. CometHelper for Comet. > 4. MagmaHelper for Magma. > > The "Helper" portion of Jetsam is entirely self contained, so can be > distributed separately and if you find it useful I think it could be a candidate 2.9 > > If anyone has any ideas for additional helpers then please let me know. Cincom is up to something similar. It would be a good idea to talk with them. Cheers Philippe _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |