> -----Original Message-----
> From: squeak-dev-bounces at lists.squeakfoundation.org 
> [mailto:squeak-dev-bounces at lists.squeakfoundation.org] On 
> Behalf Of Andreas Raab
> Sent: Wednesday, March 28, 2007 9:51 AM
> To: The general-purpose Squeak developers list
> Subject: Re: Fastest way to mock up web UI?
> 
> Hi -
> 
> This is an interesting point. But I'm not sure I understand 
> Magritte enough to be able to make a good decision. First, I 
> think Magritte isn't being used to define application control 
> flow, is this correct? If not, how does one define control 
> flow in Magritte (data flow I can see by having editors on 
> editors on editors but control flow seems different). 

Workflow can be accomplished by subclassing WATask instead of WAComponent.
Tasks are components with no UI, that mediate child components.  They are
one of the most unique things about seaside and use continuations to allow
you to model the entire workflow as a single clear method.

>   Second, Magritte is effectively an extension to Seaside, no? 
> Therefore, any decision about Magritte would imply to go with 
> Seaside too (incl. the good and the bad of it).
> Thanks for any insight you can provide.
> 
> Cheers,
>    - Andreas

No, Magritte is a meta model on top of classes.  It's a stand alone package
that can be used from Seaside, Morphic, or just plain Smalltalk.  The
package for Magritte enabled Seaside views is separate.  

In practice, Magritte is mostly used in Seaside, but the model is useful by
itself.  For example, I've used Magritte's meta model to generate Glorp
descriptions dynamically.  It contains everything I need, types, required
fields, relationships to other classes, etc.

Ramon Leon
http://onsmalltalk.com