Dear All,
Pier (or any other seaside application) no longer needs a specialized root component in order to use ShoreComponents. The Seaside28Jetsam package now includes a ShoreHelperHelper which can be enabled in your pier app configuration. The "Helper" portion of Jetsam is entirely self contained, so could be distributed separately. The goal of the helpers concept is to avoid having to use specialized root classes for generic additions which results in combinatorial problems for multiple such additions. Helpers are Decorations which are automatically added to the root component of any application subject to configuration options. They work similarly to other Plugins in Seaside 2.8, as in, you can provide additional Helpers by subclassing WAHelper. So far, in addition to the "Shore Components Helper", Jetsam implements a "Keep Alive Helper" for keeping the session alive while the users browser is open. I find the later totally indispensable. Next I am looking to see how a similar mechanism can be used to avoid needing to subclass WASession. I aim to support Magma as a helper so that all of the different options for shared or pooled magma sessions can be orthogonal to the choice of seaside session class. If Comet could be added as a helper as well then that would also be great. best regards Keith _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
Could be interesting. You can also think about announcements which usually
neddes the anAnnouncer in the session and it's 4 or 5 methods cheers Sebastian Sastre > -----Mensaje original----- > De: [hidden email] > [mailto:[hidden email]] En nombre de Keith Hodges > Enviado el: Sábado, 27 de Octubre de 2007 00:21 > Para: SmallWiki, Magritte, Pier and Related Tools ... > Asunto: [ANN] demise of Pier-Shore > > Dear All, > > Pier (or any other seaside application) no longer needs a > specialized root component in order to use ShoreComponents. > The Seaside28Jetsam package now includes a ShoreHelperHelper > which can be enabled in your pier app configuration. > > The "Helper" portion of Jetsam is entirely self contained, so > could be distributed separately. > > The goal of the helpers concept is to avoid having to use > specialized root classes for generic additions which results > in combinatorial problems for multiple such additions. > > Helpers are Decorations which are automatically added to the > root component of any application subject to configuration > options. They work similarly to other Plugins in Seaside 2.8, > as in, you can provide additional Helpers by subclassing WAHelper. > > So far, in addition to the "Shore Components Helper", Jetsam > implements a "Keep Alive Helper" for keeping the session > alive while the users browser is open. I find the later > totally indispensable. > > Next I am looking to see how a similar mechanism can be used > to avoid needing to subclass WASession. I aim to support > Magma as a helper so that all of the different options for > shared or pooled magma sessions can be orthogonal to the > choice of seaside session class. If Comet could be added as a > helper as well then that would also be great. > > best regards > > Keith > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
Sebastian Sastre wrote:
> Could be interesting. You can also think about announcements which usually > neddes the anAnnouncer in the session and it's 4 or 5 methods > > cheers > > Sebastian Sastre > > Actually that is exactly what I was thinking about... all for one button on a web page! Keith _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
Free forum by Nabble | Edit this page |