- Pharo-users - lists.pharo.org

Re: [Pharo-users] TFFiler: creates file containers to store external files in Monticello

by StÃ©phane Ducasse

> > (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(a)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 >>> >> >> >> >

Feb. 4, 2011

Re: [Pharo-users] TFFiler: creates file containers to store external files in Monticello

by Tony Fleig

Hi Stef, It is quite simple really. (It had to be for me to figure it out.) First a class of the specified name is constructed. Then the files are read in, compressed with gzip and encoded into base-64 strings. Then a class method is created for each file that answers that string. The class method is named with a base-36 encoding of the file path in order to ensure a valid method name. A dictionary of the base36-encoded method names keyed by the file path is created and that is serialized with ReferenceStream, compressed, and base-64-encoded as well. A class method called #fileList is created that reverses the process to re-create the original dictionary. To restore a file, it is looked up in the fileList dictionary by its path and then the corresponding method is invoked to obtain the encoded content. The content is then decoded, uncompressed, and written to the file path. There are a number of class methods copied from TFFiler into the file container class that is created for such things as adding, removing, replacing, displaying, and listing the file container's contents as well as redirecting the file restoring to alternate destination. The created file container class contains a class comment that lists the contents of the file container. It is updated as necessary when files are added or removed. (I was actually glad to see FileSystem delayed, as I made heavy use of FileDirectory in TFFiler.) Best regards, TF On Fri, Feb 4, 2011 at 11:12 AM, StÃ©phane Ducasse <stephane.ducasse(a)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 >> > > >

Feb. 4, 2011

Re: [Pharo-users] TFFiler: creates file containers to store external files in Monticello

by StÃ©phane Ducasse

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 >

Feb. 4, 2011

Re: [Pharo-users] [Seaside] TFFiler: creates file containers to store external files in Monticello

by Sven Van Caekenberghe

Great idea Tony, this is indeed quite useful. Thanks (again) for sharing this and for doing all the documentation work! Sven On 04 Feb 2011, at 19:17, Tony Fleig wrote: > 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 > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Feb. 4, 2011

TFFiler: creates file containers to store external files in Monticello

by Tony Fleig

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

Feb. 4, 2011

Re: [Pharo-users] Matrix

by Paul DeBruicker

On 02/03/2011 02:25 PM, HernÃ¡n Morales Durand wrote: > It seems only Paul DeBruicker can do that, he's the project admin. > Paul? > OK. I did that. Is it important to link to Didier's email in the project? I also added HernÃ¡n as an admin. Let me know if there's anything else. Paul > 2011/2/3 StÃ©phane Ducasse<stephane.ducasse(a)inria.fr>: >> Could you add that didier agreed to release his code under MIT >> Tx >> >> Stef >> >> On Feb 3, 2011, at 4:43 PM, HernÃ¡n Morales Durand wrote: >> >>> Thanks Werner, I will check later with the VW image too but I've >>> integrated your fix. I've splitted the tests to their own package. The >>> repository is world writable so feel free to add future improvements. >>> >>> HernÃ¡n >>> >>> 2011/2/3 Werner Kassens<wkassens(a)libello.com>: >>>> Hi HernÃ¡n, >>>> i had a superficial look at DHBNumerical and it does indeed what i wanted to >>>> do, thanks again. >>>> i ran DHB-Numerical-Tests and it showed 5 errors.i added this method: >>>> DhbNevilleInterpolator>>initialize >>>> super initialize. >>>> leftErrors :=#(). >>>> rightErrors :=#() >>>> and the tests showed only 1 error. i havent looked, what the code does, it >>>> was only an instinctive fix, hence use with caution. the last error is not >>>> fixable in this instinctive way, one would have to understand how >>>> DhbClusterFinder actually finds clusters, and i have not yet looked at the >>>> doku and dont have the time at the moment. >>>> werner >>>> >>>>

Feb. 3, 2011

Re: [Pharo-users] Matrix

by Werner Kassens

Hi HernÃ¡n, a fix for the last error in DHBNumerical would be to change DhbEuclideanCluster>>centerOn to: centerOn: aVector "(c) Copyrights Didier BESSET, 2000, all rights reserved. Initial code: 2/16/00 " center := aVector. accumulator := DhbVectorAccumulator new: (aVector ifNil:[0] ifNotNil: [aVector size]). i am glad that i am able to download a package and im certain i would mess up everything if i would try to upload something, hence i would appreciate it, if you would do that if you deem it appropriate. werner

Feb. 3, 2011

Re: [Pharo-users] Pharocasts: GUI with Polymorph

by Denis Kudriashov

Hello, I really exciting in how #changed: work. It is from old smalltalk MVC? 2011/2/3 laurent laffont <laurent.laffont(a)gmail.com> > Develop a contact manager desktop application. > > You will learn: > - how Pharo helps the "Program by intention" style of programming > - how to create basic persistency of created Contact object > - how to compose a GUI, basic widgets, events and layout > > http://www.pharocasts.com/2011/02/pharo-gui-with-polymorph.html > > <http://www.pharocasts.com/2011/02/pharo-gui-with-polymorph.html> > Laurent Laffont - @lolgzs <http://twitter.com/#%21/lolgzs> > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ >

Feb. 3, 2011

Re: [Pharo-users] Matrix

by HernÃ¡n Morales Durand

It seems only Paul DeBruicker can do that, he's the project admin. Paul? 2011/2/3 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Could you add that didier agreed to release his code under MIT > Tx > > Stef > > On Feb 3, 2011, at 4:43 PM, HernÃ¡n Morales Durand wrote: > >> Thanks Werner, I will check later with the VW image too but I've >> integrated your fix. I've splitted the tests to their own package. The >> repository is world writable so feel free to add future improvements. >> >> HernÃ¡n >> >> 2011/2/3 Werner Kassens <wkassens(a)libello.com>: >>> Hi HernÃ¡n, >>> i had a superficial look at DHBNumerical and it does indeed what i wanted to >>> do, thanks again. >>> i ran DHB-Numerical-Tests and it showed 5 errors.i added this method: >>> DhbNevilleInterpolator>>initialize >>> super initialize. >>> leftErrors :=#(). >>> rightErrors :=#() >>> and the tests showed only 1 error. i havent looked, what the code does, it >>> was only an instinctive fix, hence use with caution. the last error is not >>> fixable in this instinctive way, one would have to understand how >>> DhbClusterFinder actually finds clusters, and i have not yet looked at the >>> doku and dont have the time at the moment. >>> werner >>> >>>

Feb. 3, 2011

Re: [Pharo-users] Pharocasts: GUI with Polymorph

by StÃ©phane Ducasse

argh the kind of mail I cannot skip fast :) Thanks a lot laurent! S. On Feb 3, 2011, at 12:46 PM, laurent laffont wrote: > Develop a contact manager desktop application. > > You will learn: > - how Pharo helps the "Program by intention" style of programming > - how to create basic persistency of created Contact object > - how to compose a GUI, basic widgets, events and layout > > http://www.pharocasts.com/2011/02/pharo-gui-with-polymorph.html > > > Laurent Laffont - @lolgzs > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/

Feb. 3, 2011