[Seaside] Seaside Design Questions

[Eric Hodel]

In the course of porting Seaside to Ruby, I've come across many things I
didn't understand.  After beating my head against the wall, walking
away, and coming back I figured out how they worked/why they were there.
But that still didn't clue me into a few things...

Why does WAStateRegistry use snapshot:isIdenticalTo: instead of =?  In
Smalltalk is = not always a valid indicator of two objects having the
same state?

Why are WAHtmlRenderer and WAHtmlBuilder split into two classes?
Nothing is jumping out at me to explain this.

Same for WASession and WAControllerSession, since start seems to be the
only abstract method in WASession.  Is there some extra hooks that can
be added by not subclassing from WAControllerSession?

The rest of these seem to be leftovers or things I am completely missing
the point of.

What was (is) the layout method on WAStoreBrowseFrame for?  It seems
template-ish code for renderContentOn in WAStoreBrowseFrame.

What is the Amb class for?  I don't see it used by any other part of
Seaside.

-- 
Eric Hodel - drbrain at segment7.net - http://segment7.net
All messages signed with fingerprint:
FEC2 57F1 D465 EB15 5D6E  7C11 332A 551C 796C 9F04

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20031203/2d1750e0/attachment.bin