<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: [ANN] SWT 0.6 released</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Hola Andres!</FONT>
</P>
<P><FONT SIZE=2>> -----Original Message-----</FONT>
<BR><FONT SIZE=2>> From: Andres Valloud [<A HREF="mailto:sqrmax@prodigy.net">mailto:sqrmax@prodigy.net</A>]</FONT>
</P>
<P><FONT SIZE=2>[snip]</FONT>
</P>
<P><FONT SIZE=2>> > What do you do when developing?</FONT>
<BR><FONT SIZE=2>> </FONT>
</P>
<P><FONT SIZE=2>Ok, and you load anything and everything but the SIFConfig, which depends on the Module/SemanticModel being around. Thanks for the pointer to the Grooming page.</FONT></P>
<P><FONT SIZE=2> </FONT>
<BR><FONT SIZE=2>> > The image is tight! It has lost the VMConstruction stuff as well</FONT>
<BR><FONT SIZE=2>> > as Balloon3D and much other stuff.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> The idea behind this is that the VM construction stuff, </FONT>
<BR><FONT SIZE=2>> and/or VMMaker,</FONT>
<BR><FONT SIZE=2>> would be a module loadable upon request. Same with Balloon3D or</FONT>
<BR><FONT SIZE=2>> anything else.</FONT>
</P>
<P><FONT SIZE=2>yep, and by extension to what other folks have been doing, the Networking, Morphic, MVC, etc. would all be external modules/components too.</FONT></P>
<P><FONT SIZE=2> </FONT>
<BR><FONT SIZE=2>> > [Bad]</FONT>
<BR><FONT SIZE=2>> > Missing SemanticModel. We like it, we love it,</FONT>
<BR><FONT SIZE=2>> > we want more of it! :)</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Well... we'll have to ask Paul or Joseph :).</FONT>
</P>
<P><FONT SIZE=2>I have and they are working on it. :)</FONT>
</P>
<P><FONT SIZE=2>> > [Ugly]</FONT>
<BR><FONT SIZE=2>> > The UI is now outdated.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I guess that you could improve it. But so that you know, the fonts</FONT>
<BR><FONT SIZE=2>> don't have any license (as opposed to Squeak), and the XML GUI builder</FONT>
<BR><FONT SIZE=2>> should work both on Morphic and MVC.</FONT>
</P>
<P><FONT SIZE=2>Yep. The XMLUIBuilder is cool technology. However, a lot of work has occurred since the initial 3.1a image came out. The 3.1a environment looks great!!!!!</FONT></P>
<P><FONT SIZE=2>> > Do you have scripts that will allow us to take the</FONT>
<BR><FONT SIZE=2>> > latest and greatest image and strip it down to it's fur?</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I don't think it's a good idea, anyway. I think it's much </FONT>
<BR><FONT SIZE=2>> better to do</FONT>
<BR><FONT SIZE=2>> it once (and only once), do it really well (no undeclareds, all source</FONT>
<BR><FONT SIZE=2>> code can be recompiled without problems, no obsolete classes, </FONT>
<BR><FONT SIZE=2>> etc), and</FONT>
<BR><FONT SIZE=2>> from then on just put modules into the repository when you want new</FONT>
<BR><FONT SIZE=2>> stuff.</FONT>
</P>
<P><FONT SIZE=2>I would disagree, although your next paragraph puts it in a different light. The fact is that there are 4 - 5 other people doing this same exercise right now. All it is is an evolving stripper script, including code to address Undeclared, Obsolete and so on. I'm sure you *want* people kicking the tires and checking the engine. This includes prepping a release image...</FONT></P>
<P><FONT SIZE=2>> Incidentally, those scripts never existed. We had to do it </FONT>
<BR><FONT SIZE=2>> manually for</FONT>
<BR><FONT SIZE=2>> the most part, and it was a lot of work!</FONT>
</P>
<P><FONT SIZE=2>yes. Isn't a large part of that work, 'modularizing' the base classes to remove methods that are used by a stripped framework? </FONT></P>
<P><FONT SIZE=2>Over the next week, I will produce a version of my code that runs on your new events. I don't know the story with exceptions - sorry, dude. :)</FONT></P>
<P><FONT SIZE=2>later,</FONT>
<BR><FONT SIZE=2>Rob</FONT>
</P>
</BODY>
</HTML>