I'd like to suggest a feature, some method like:<div><br></div><div>TFFiler class >> fullPathOf: aFileName</div><div><br></div><div>That returns the full system path for a given file.</div><div><br></div><div>Cheers,</div>
<div><br></div><div>Bernat.</div><div><br><div class="gmail_quote">2011/2/7 AxiNat <span dir="ltr"><<a href="mailto:tibabenfortlapalanca@gmail.com">tibabenfortlapalanca@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Tony, great work!<div><br></div><div>I'll be using this one in production too :)</div><div><br></div><div>Bernat Romagosa.</div><div><br><div class="gmail_quote">2011/2/4 Sven Van Caekenberghe <span dir="ltr"><<a href="mailto:sven@beta9.be" target="_blank">sven@beta9.be</a>></span><div>
<div></div><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Great idea Tony, this is indeed quite useful.<br>
<br>
Thanks (again) for sharing this and for doing all the documentation work!<br>
<font color="#888888"><br>
Sven<br>
</font><div><div></div><div><br>
On 04 Feb 2011, at 19:17, Tony Fleig wrote:<br>
<br>
> I've published a tool I'm using called TFFiler.<br>
><br>
> My problem was that I had a number of external files that were<br>
> required for my Seaside web application. These were CSS, Javascript,<br>
> and image files that had to be placed in a specific directory tree<br>
> structure. When I moved my web app to another system, I always had to<br>
> remember to reconstruct the external directory tree. Over time, the<br>
> directory tree got larger and more complex.<br>
><br>
> For deployment, I wanted the files to be served by Apache and not the<br>
> Seaside ExternalFileLibrary. (ExternalFileLibrary was the most<br>
> convenient approach during development.) This meant the directory tree<br>
> should be moved to a location other than the Pharo Resources<br>
> directory, which was the most convenient location during development.<br>
><br>
> The current version of Monticello does not provide a way to save<br>
> external files with a project. TFFiler addresses this shortcoming. Now<br>
> when I load my project from Monticello the necessary external files<br>
> are deployed automatically.<br>
><br>
> Maybe someone else will find this useful as well.<br>
><br>
> <a href="http://www.tonyfleig.com/smallthoughts/blog/tffiler" target="_blank">http://www.tonyfleig.com/smallthoughts/blog/tffiler</a><br>
> <a href="http://www.squeaksource.com/TFFiler" target="_blank">http://www.squeaksource.com/TFFiler</a><br>
><br>
> Regards,<br>
> TF<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>
<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></div></div><br></div>
</blockquote></div><br></div>