[Seaside] Tasks, Components, Magritte and Style
nick.ager at gmail.com
Wed Mar 9 11:40:12 UTC 2011
I might be misunderstanding your question, but can't you wrap up your
WATask within a WAComponent? WAWelcome could serve as a template. As
for styles hopefully the book covers it:
Feel free to ask away if I misunderstood.
On 9 March 2011 06:45, Daniel Lyons <fusion at storytotell.org> wrote:
> On Mar 8, 2011, at 11:26 PM, Daniel Lyons wrote:
>> I'm extremely new to Seaside, and I'm getting a bit confused at the intersection between these four concepts. All I want is:
>> 1. Consistent style.
>> 2. A Task involving a Magritte-generated component, with the same style.
>> Unless I'm mistaken, the right way to get consistent style is to implement updateRoot on your component to call addStyle. How does one go about this if the root of your app is a WATask subclass? I think I'm not understanding something fundamental about either nesting components or the relationship between tasks and components, because it seems like you would want to be able to say, this component in the tree is actually the first step in a task. For example, to render a containing component that has within it a login component, but without requiring the user click on "Login" before showing the login form. I can see how to kick off a task in response to an event like clicking.
> Apparently part of the answer is to add onAnswer: to an embedded component, to catch the answer and return it to a parent component. That solves one operational question, but I'm still unclear about how to do styling properly.
> Daniel Lyons
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside