Message: 5 > Date: Wed, 30 Jun 2010 23:50:24 +0200 > From: St?phane Ducasse <[email protected]> > Subject: Re: [Pharo-project] CLFramework and Pharo > To: [email protected] > Message-ID: <[email protected]> > 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
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
