<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 10-Feb-08, at 3:38 AM, Zulq Alam wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Lukas Renggli wrote:<br><br><blockquote type="cite">The idea is to have a special FileLibrary that provides its resources<br></blockquote><blockquote type="cite">from a freely configurable file-system path, instead of using its<br></blockquote><blockquote type="cite">methods. It will be slow and inefficient (like the FileLibrary already<br></blockquote><blockquote type="cite">is), but it will make file serving easy. <br></blockquote><br>I find myself doing this whenever I have a large script or file:<br><br>MyFileLibrary>>scriptJs<br> ^ (StandardFileStream fileNamed: 'script.js')<br> contentsOfEntireFile<br></blockquote></div><br><div>Personally, I like to go in the other direction. The point of this is to be able to work with the library files using tools more suited to other languages - Javascript, CSS and whatnot, yes?</div><div><br class="webkit-block-placeholder"></div><div>I've hacked the Squeak FTP server[1] to serve the library methods as files. It #performs them for a download and recompiles them for an upload. Most text editors can handle editing remote files over FTP, so it works nicely.</div><div><br class="webkit-block-placeholder"></div><div>Colin</div><div><br class="webkit-block-placeholder"></div><div>[1] <a href="http://www.squeaksource.com/FTPServer.html">http://www.squeaksource.com/FTPServer.html</a></div><div><br class="webkit-block-placeholder"></div></body></html>