> Am 17.09.2017 um 12:12 schrieb Pierce Ng <pie...@samadhiweb.com>: > >> On Mon, Sep 11, 2017 at 06:25:55PM +0200, Stephane Ducasse wrote: >> Hi Pierce Ng >> How different is the API from Seaside? >> Because I would like to use it. >> I like to think modularly :) > > Hi Stef, > > I modeled it after Seaside's API. However, it was really just a start and > needs > much more work. I created this when investigating writing web apps in Cuis, > hence the perceived need for a standalone library. Eventually I ran out of > time > and decided to stick to full Seaside loaded into Pharo. > So you've built something like seaside canvas? I like to emphasize that seaside is not really a standalone HTML model but (as the name says) a canvas which streams markup. What we should explore is the possibility of having a HTML model that can be used for streaming, too, instead just the streaming. There could be a lot of synergies here because web frameworks, pillar, PharoJS are all working close to something like that.
my 2 cents, Norbert
