My knowledge is limited, but XML seems more portable than code Smalltalk. 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=0DD1BED3F232BE... 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. 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.