(I was actually glad to see FileSystem delayed, as I made heavy use of FileDirectory in TFFiler.)
:) But if you look at the existing code in pharo you can faint :)
Best regards, TF
On Fri, Feb 4, 2011 at 11:12 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Argh I want that! Now tony tell us what is the principle. I was thinking to add a git entry to a squeaksource but how do you manage them? Stef
I've published a tool I'm using called TFFiler.
My problem was that I had a number of external files that were required for my Seaside web application. These were CSS, Javascript, and image files that had to be placed in a specific directory tree structure. When I moved my web app to another system, I always had to remember to reconstruct the external directory tree. Over time, the directory tree got larger and more complex.
For deployment, I wanted the files to be served by Apache and not the Seaside ExternalFileLibrary. (ExternalFileLibrary was the most convenient approach during development.) This meant the directory tree should be moved to a location other than the Pharo Resources directory, which was the most convenient location during development.
The current version of Monticello does not provide a way to save external files with a project. TFFiler addresses this shortcoming. Now when I load my project from Monticello the necessary external files are deployed automatically.
Maybe someone else will find this useful as well.
http://www.tonyfleig.com/smallthoughts/blog/tffiler http://www.squeaksource.com/TFFiler
Regards, TF