[Seaside] render methods vs non-render methods in components
ramon.leon at allresnet.com
Mon Mar 31 16:47:24 UTC 2008
> > renderFooOn: html
> Exactly, and put it into a category called #rendering.
> > But what about the other methods? How would you know if another
> > method is being called from a render method or from a
> callback, or maybe both?
> Exactly the same pattern, call it #render([A-Z][a-z]+)*On:
> and put it into a category called #rendering.
> > Should I put all callback support into a separate protocol
> I mostly put these into a category called #actions.
> Well, what I'm thinking about is the auxiliary methods?
> Maybe it's always obvious, but I'm thinking about the case
> where sometimes a callback method would call it, and
> sometimes a render method would call it. I'm wondering if
> I'm thinking about a case that usually doesn't happen, or
> whether this actually does run into trouble.
I just don't see this happening in my code. Component transitions are
almost always bound to some user action so it's pretty clear just from the
method name (#save, #cancel, #search, etc.) that this method is used in a
More information about the seaside