Fastest way to mock up web UI?

Andreas Raab andreas.raab at gmx.de
Wed Mar 28 16:50:37 UTC 2007


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). 
  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

Keith Hodges wrote:
> I think it might be worth pointing out that Pier may be an option and is 
> used by many, such as lukas for their personal websites.
> 
> Looking at the components of a web site.
> 
> Content:
>    text, files, images can all be entered and uploaded using the website 
> itself.
> Style:
>    At present the stylesheet is stored in a class, served as a set of 
> files, and can be edited directly. (I have done an 'edit style via 
> website' experiment too.)
> Layout:
>    The layout is defined as an assembly of other embedded components or 
> pages and can be edited via the website at: /seaside/pier/environment. 
> For example I replaced the header component with my own picture, this is 
> trivially easy to do.
> Nice urls: Pier supports sensible bookmarking
> 
> This is just the starting point, for any more complex stuff, seaside 
> components can be embedded, magritte is part of the base package, and 
> there are many other plugins such as rss, blog, two security models etc.
> 
> best regards
> 
> Keith
> 
> 
> 




More information about the Squeak-dev mailing list