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. > Exists external editor (UI Builders too) for generate code XAML. Then that > code could be "file in" used in a image of Pharo-Smalltalk where a class > could parse it and build the UI. The idea is use external tools like that... > > http://www.youtube.com/watch?v=kyrN_Ky3HWc&feature=PlayList&p=0DD1BED3F232BE7F&playnext_from=PL&index=0&playnext=1 > > Is a very sample tool, but exists anothers much more complete. Why re-create > a new ui builder when exists another external always best? I need only the > code for rebuild the UI, not all ui builder tool. > > I don´t know nothing of Seaside, but I understand than the mechanism for > build the UI will be the same. The same XAML code could build a equivalent > UI, but in that case for HTML explorer. But this is exactly what is done in VW with windowsSpec you can get a builder (which builds the application UI) either for your desktop or for VWWave (long time ago before seaside even if less powerful). > Well, only is a idea, surely stupid XD > > PS- My name is Gerard, without last vowel. > > > -- > View this message in context: > http://forum.world.st/CLFramework-and-Pharo-tp2273256p2274245.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
