Hi all!

Quoting Avi Bryant <avi at beta4.com>:
> On 3 Sep 2002, Cees de Groot wrote:
> 
> > <delurk/>
> >
> >  <goran.hultgren at bluefish.se> said:
> > >I will take a look if/when I get time. :-) I have also been thinking
> > >about possibility of combining HttpView with Seaside, but I don't
> know
> > >if that is easy.
> > >
> > You guys should check that out. It would be good to have a single "The
> Default
> > Squeak Web App Building Framework", but with various approaches to
> building
> > forms on top of it.
> >
> > <lurk/>
> 
> Yes... this was the idea behind Seaside 2.0 - to have a series of
> layers,
> each of which could be the foundation for alternate approaches.  The
> continuation based session management I consider core, but Goran could
> layer an alternate form builder on top of it, or could use my callback
> based form builder but layer an alternate component system on top of
> it,
> etc.  Meanwhile, I'm thinking about various templating systems and
> MVC-like systems to layer on top of my components...
> 
> Avi

Sounds interesting. Currently I use Comanche very nonintrusively - HttpView just
sits ontop and I have sofar only used cookies for keeping track of logged in users.

So in theory HttpView should be easily layered on top of Seaside I think. I will
take a look some day.

Right now I have actually landed a 1 month assignment using
HttpView/Comanche/Squeak! Yiha. Not much payment but I am hoping this product
will be able to attract at least 10-100 subscribers for 80$/month. The effect of
this is that SqueakMap will have to be on hold for a while, but I will release a
version tomorrow I think with the improvements Ned talked about in the SqueakMap
browser. On the other hand HttpView will probably get some more functionality
(like radio buttons etc).

We will see in a month. :-)

regards, Göran

PS. Another cool little thing with treating Form elements like widgets is that
they can be quite smart for you. One example is the dropdown menu. In HttpView I
give it a collection with objects to show (as long as they implement "name") and
the value returned by the widget is the selected object itself - not an index or
a string or anything silly like that. :-) DS

Göran Hultgren, goran.hultgren at bluefish.se
GSM: +46 70 3933950, http://www.bluefish.se
\"Department of Redundancy department.\" -- ThinkGeek