<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16414" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2></FONT> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><SPAN
class=703202101-19022007><FONT face=Arial color=#0000ff size=2> <<FONT
face=Tahoma color=#000000>Michael van der Gulik></FONT> </FONT></SPAN>I
have an image. In that image is a Namespace. I need to get that Namespace and
the source for the classes in that Namespace out of that image and in to another
image somehow - usually done using e.g. Monticello, filings stuff out,
etc.<BR><BR>The format for SqueakV9.sources, squeak.changes, changesets and
file-outs will have to change a bit if they were to support Namespaces. Rather
than changing the format, another option is to chuck everything out the window
and use a different system, such as keeping the source code and version
information in the image as Text objects. I'm just wanting people's opinions on
the technical merits of the options I mentioned in the root of this thread.
<FONT size=2><FONT face=Arial><FONT color=#0000ff><<SPAN
class=703202101-19022007> / </SPAN></FONT></FONT><FONT face=Tahoma
color=#000000>Michael van der Gulik></FONT></FONT></DIV>
<DIV><BR><SPAN class=703202101-19022007><FONT face=Arial color=#0000ff
size=2>Ok, thanks for the explanation. I think I now understand your
problem.</FONT></SPAN></DIV>
<DIV><SPAN class=703202101-19022007></SPAN> </DIV>
<DIV><SPAN class=703202101-19022007><FONT face=Arial color=#0000ff
size=2>My suggestion: </FONT></SPAN><SPAN class=703202101-19022007><FONT
face=Arial color=#0000ff size=2>Namespaces should be constructed by message
sends, just like classes are constructed by message sends. The
instructions to create/modify namespaces should be encoded in a file out as "do
it" chunks--again, just like class definitions. This may not be the ideal
solution in the long run, but it's the only workable/acceptable solution
initially.</FONT></SPAN></DIV>
<DIV><SPAN class=703202101-19022007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=703202101-19022007><FONT face=Arial color=#0000ff size=2>I
would avoid changing the canonical message sends that define classes if at all
possible. If necessary, send additional namespace-related messages to
classes in separate "do it" chunks.</FONT></SPAN></DIV>
<DIV><SPAN class=703202101-19022007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=703202101-19022007><FONT face=Arial color=#0000ff size=2>The
namespace-related "do it" chunks should silently short-circuit if the receiving
image doesn't support namespaces (although a single warning message for each
file-in might be nice--perhaps a UUID for each file-out would make that
possible.) Or, perhaps your Namespace module could be auto-installed from
SqueakMap or SqueakSource, when needed.</FONT></SPAN></DIV>
<DIV><SPAN class=703202101-19022007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=703202101-19022007><FONT face=Arial color=#0000ff
size=2>Evolution almost always works a lot better than revolution. Don't
fight against the tide. Go with the flow. When life hands you a lemon,
make lemonade.</FONT></SPAN></DIV>
<DIV><SPAN class=703202101-19022007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=703202101-19022007><FONT face=Arial color=#0000ff
size=2>--Alan</FONT></SPAN></DIV></BODY></HTML>