From: Eric Hodel <drbrain@...7.net>
Date: 2004-04-02T11:30:02-08:00
Subject: Re: Borges - coupled to html interface?

--Qcw+NG9yjQzXdZsc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Its Me (itsme213@hotmail.com) wrote:

> Why is Borges (or Seaside) coupled to an html/browser interface?

Its not, really.  I asked a related question on the Seaside list in
the course of my porting Seaside to Borges, and when you get into the
guts, you find out that Seaside is a bunch of well-factored
bolt-together pieces.  (Borges uses the same approach.)

(thread here:
http://lists.squeakfoundation.org/pipermail/seaside/2003-December/002402.ht=
ml)

The Renderer itself is actually two pices, an HtmlBuilder and an
HtmlRenderer.  The Builder only knows about HTML widgets.  The Renderer
knows about callbacks and form processing.

> It seems that the Component model (composable logical 'panes' with
> application logic) and the modelessness and free 'Back' button
> functionality, could both be useful outside the context of an HTML browse=
r.

The only thing stopping you from using it outside of an web server is
the render_on methods being written as HTML-centric.

> It seems that Components, rather than generating HTML through a renderer,
> could generate some kind of logical 'Interactor' descriptions. Different
> Renderers could then map this differently:

You can take Seaside apart kinda like Legos, the problem is finding out
where the edges of the pieces are :)

>   - HTML renderer:
>      - map to (a part of) an html page, or to some sequence of (part of)
>        html page
>   - Other UI renderer:
>      - different mapping e.g. to native widgets
>=20
> A little bit like XForms.
>=20
> Sound feasible? Worth investigating?

Absolutely!

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


--Qcw+NG9yjQzXdZsc
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQFAbb86MypVHHlsnwQRAstwAJ91RtMFaA4rALBKoqmtVU704vOHlQCdGf4K
Sz16q/21vhf+91QbWojAnN8=
=hS5N
-----END PGP SIGNATURE-----

--Qcw+NG9yjQzXdZsc--