Fastest way to mock up web UI?

As others have mentioned, the store example is probably not a good if you
are looking for how to make a quick site simply.  The store example is
showing all the advanced features of the framework.

>Oh, and what are the prospects for RESTful urls in Seaside these days? Last
>time I asked about it there wasn't really a good answer - is there one
>these days? I'm not really into the whole auto-magic URLs myself; I'd
>rather have it say http://foo.bar.com/users/andreas if I want to refer to a
>user page.

Well, Seaside is really a component based application concept.  It makes, as
Ramon mentioned, web programming more like regular GUI programming.  In a
regular app you click the icon and start doing things from the begining.  
There are no URL entry points.  In Seaside instead of clicking an icon you
go to a URL to start the "application".

The "magic" part of the URL are just two variables and if you don't want to
see it you can tell Seaside to use cookies instead.

If you want RESTful urls then I would suggest taking a look at Pier.  You
can do RESTful urls in base Seaside but you have to do it all yourself.  
Pier on the other hand is already set up this way.  Another nice thing about
Pier is that you don't have to build "Pier" components if you don't need
them, you can embed normal Seaside components as well.

Using Pier might seem like a lot of things to load for a quick mock up, but
for me at least, it was the quickest way to build my website.  It isn't hard
to install either if you use the new Universe.  I think you could also use
the Pier package from SqueakMap (don't remember if it works out the
dependancies, but "Pier security" does for sure).

_________________________________________________________________
Live Search Maps – find all the local information you need, right when you
need it. http://maps.live.com/?icid=hmtag2&FORM=MGAC01

>
> Magritte is, for the most part, about abstracting the view of
> an object.
>
>
> No.  Magritte is an abstraction of making a view of an
> object.  It does happen to have generators defined for
> Seaside.  It also has them defined for Morphic.  It would be
> possible to define them for anything you wanted.

Actually, Magritte is metadata for an object, it really has nothing to do
with views at all.  The metamodel describes selectors and their
relationships to other objects, predicates for validating potential values,
constraints on fields like length, or type, datasources for potential valid
data like a state list, etc.  

Magritte is similar to pragmas except done with ordinary Smalltalk code
which allows more than just literal metadata.  Magritte metadata is
executable and can include expressions.

The metadata happens to be quite useful in generating views, but that's not
all its useful for.  It can generate db schemas, db queries, object graph
traversals, visual representations of the model, charts, graphs, anything
really.  It's just metadata, its purpose is in the eye of the developer.
Like pragmas, that metadata could be useful in a number of circumstances
unrelated to the UI.

Ramon Leon
http://onsmalltalk.com