Date: Wed, 30 Jun 2010 23:50:24 +0200
From: St?phane Ducasse <stephane.ducasse@inria.fr>
Subject: Re: [Pharo-project] CLFramework and Pharo
To: Pharo-project@lists.gforge.inria.fr
Message-ID: <77E6AD68-79FF-4590-9FB6-7B2E1C961001@inria.fr>
Content-Type: text/plain; charset=iso-8859-1

But you rely on XML.
Second the builder (ie generating the XML) is not the problem as far as I know.
but more how to assemble the widget and make sure that the layout
are kept or specified.

Then how using an external tools can make sure that this tool got well the way layoutMorph
and other works?

Stef

> My knowledge is limited, but XML seems more portable than code Smalltalk.

I do not understand why we want portability.
Please note that the VWspec are as portable as XML between Smalltalk they are just arrays (
probably we would get a problem for the UI.Node notation but this is not the problem.

Another place to see such an example is Smalltalk/X.� I think they conformed to the VW Specs as well...

Rob