I did something similar for StORE a few years ago. It used a pragma in the method to define the path name of the external file, with the file contents stored right after the pragma. The VW UI was extended to support keeping the external file and the method synchronized.<div>
<br></div><div>It worked well for us at the time and I think its been extended by others since then.<br><br><div class="gmail_quote">On Sat, Oct 25, 2008 at 2:29 PM, Sebastian Heidbrink <span dir="ltr"><<a href="mailto:sebastian_heidbrink@yahoo.de">sebastian_heidbrink@yahoo.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi!<br>
<br>
Small hint here. We are developing in VASt. One way to version external files in ENVY, we use at our costumer, is creating a class named like the external file resource (eg. STYLECSS) this can be imported or exported to and from ENVY. The file contents is converted to string, or binary, versioned and stored directly in ENVY. So we are able to version even external files in the Smalltalk repository....<br>
<br>
I think that might also be able for other Smalltalks...<br>
<br>
Cheers!<br>
Sebastian<br>
<br>
<br>
<br>
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: <a href="http://mail.yahoo.de" target="_blank">http://mail.yahoo.de</a><div><div></div>
<div class="Wj3C7c"><br>
<br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</div></div></blockquote></div><br></div>