February 2011 - Pharo-users

TFFiler: creates file containers to store external files in Monticello
by Tony Fleig Feb. 4, 2011

Feb. 4, 2011

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

3 6

Matrix
by Werner Kassens Feb. 3, 2011

Feb. 3, 2011

Hi, i use Pharo-1.1-11411 and got a few questions. i looked at the comments of Matrix: it talks about Array2D but this object does not exist? it says "Element-wise matrix arithmetic works", but this is not true: while + - * functions in this way: aNumber + aMatrix, "/" does not always function: aSmallInteger / aMatrix produces an error, because aMatrix is tested with isZero. a simple fix would be to change the first program line in SmallInteger>>/ from: aNumber isZero ifTrue: [^(ZeroDivide dividend: self) signal]. to: (aNumber isNumber and: [aNumber isZero]) ifTrue: [^(ZeroDivide dividend: self) signal]. further aMatrix + aNumber and similar arithmetic dont work. but with the above fix it would work nicely with simple implementations like this: Collection>>/ / aNumber ^aNumber adaptToCollection: self andSend: #/ and so forth. while testing these things with Fractions, i noticed this: printing {3/4} produces this output:{(3/4)}. printing {{0.75}} produces this output:#(#(0.75)). printing {{3/4}} produces this output:{((Array new: 1) at: 1 put: (3/4); yourself)}. i wonder what the last output wants to tell me? does it want to tell me, that the last thing uses up a lot more memory than the first two, and accessing it takes more time, so that i should use the second thing instead, or is it (more or less) just print output related? werner

4 9

auto compile accessors / updators
by Phil Feb. 1, 2011

Feb. 1, 2011

Is there an equivalent in in pharo/squeak of the GemStone method #compileMissingAccessingMethods cheers, phil

2 2