January 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Mac VM 5.3b1 ships
by John M McIntosh Jan. 11, 2010

Jan. 11, 2010

I've push the latest cocoa based 32/64bit macintel/powerpc VM 5.3b1 Various users pointed out that option-arrow key did not work, plus there was a crash due to a draw locking issue. I spent a few hours looking into the complexity of keyboard management in Cocoa and left-overs from NeXTStep. I likely still have more hours of testing for extended keyboards but it should now work for the enter/return, esc, delete, page up/down, and arrows keys with the various combinations of shift, function, control, option, and apple. The crash was related to a race condition in the os-x drawing logic. I refactored it to a more simplistic code base shared between the iPhone and OSX. As a bonus the non-complex code is actually faster than the Carbon Drawing logic found in the 3.x/4.x series of VMs, and much faster than the previous complex/broken logic. Look for the folder experimental/64bits in the regular places found via http://smalltalkconsulting.com/squeak.html or ftp://ftp.smalltalkconsulting.com/experimental/64bit/32bitImage*64bitVM/ or http://homepage.mac.com/johnmci/FileSharing.html click to experimental, 64bits , 32bitImage*64bitVM file name: Squeak 64-32 5.3b1.app.zip This *beta* VM runs in 32 or 64 bit mode on macIntel, and 32bit mode on powerpc to support Squeak 32bit images. Includes the freetype plugin, and requires os-x 10.5 or higher. -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

2 1

[Pharo-project] Categorizing method extension with pragma
by CÃ©drick BÃ©ler Jan. 11, 2010

Jan. 11, 2010

Hi, Just a 2 cents thought on method extension. Why not associating a pragma instead of using the package name prefixed by a star ? Say there is a package named MyPackage and I override a method in String or add a new one. What I'd like is keeping the original method category name (or find an appropriate one) instead of using *mypackage. For instance: String>>aMethod <package: MyPackage> ... ... ^result Then, we would have to adapt monticello for that purpose. We could also use dynamic protocols to get the list of extension method by package. What does other think ? I find it could be a good starting point to deal with packages. -- CÃ©drick

4 6

[Pharo-project] problem installing Nile
by Mariano Martinez Peck Jan. 11, 2010

Jan. 11, 2010

I don't know why, but (sometimes) I have errors trying to install Nile-All in PharoCore. This is weird becuase it says that it didn't found a version, but the version really exists. I attach screenshots. Any idea? cheers mariano

2 5

[Pharo-project] Pharo-beginner mailing list ?
by StÃ©phane Ducasse Jan. 11, 2010

Jan. 11, 2010

Hi all I remember that the squeak-beginner mailing-list (our ideas) was a huge success since it enabled people to ask questions and have less mails. So a question to you: do you think that it would be good to have a pharo-beginner mailing list? Stef

13 26

[Pharo-project] [ANN] Hudson continuous integration server support
by Yanni Chiu Jan. 10, 2010

Jan. 10, 2010

I've created a project at: http://www.squeaksource.com/HudsonBuild.html You can automate a build through a shell script run by Hudson, and view the SUnit test results through Hudson. The first example runs the unit tests in the PharoCore image, and the second example loads Pier and runs its unit tests. The examples derive from Lukas' Gofer scripts, but you could set things up to use Metacello. The build scripts are attached to this message as a zip file. A howto.txt is included in the zip, and pasted below. -- Yanni Chiu ========= howto.txt ========= ====== PART A - Prepare image and adjust build scripts ====== Unzip the build scripts - choose a build home directory, and unzip the files there - there should be an empty "images" directory Create an initial build image - get a distribution image (e.g. http://www.pharo-project.org/pharo-download) - put the image in the images directory - start the image, and refresh Gofer using: <code> Utilities updateFromServer. [ Gofer gofer load ] on: Error do: [ :err | err retry ]. Gofer gofer recompile. </code> - this update should be part of the build script, but it was not working for me when it's run from a startup script. - save the image as "core" Adjust build scripts - edit the core.sh and pier.sh scripts, setting suitable values for: SQUEAK_VM IMAGES_HOME SCRIPTS_HOME - you may have to adjust the repository locations too These sample build scripts are just a starting point for creating your own build scripts for your project. The core.sh script does not actually load any packages, it just runs the test cases in the PharoCore image. The pier.sh script loads Seaside/Magritte/Pier into the core image, then runs the test cases. ====== PART B - Integrate with Hudson ====== Download hudson.war from http://hudson-ci.org/ Start the Hudson server. - run something like: WARFILE=$HOME/apps/hudson/hudson.war LOGFILE=hudson.log nohup java -jar $WARFILE --httpPort=9090 > $LOGFILE 2>&1 & - port 9090 is used to avoid conflict with Seaside on 8080 - goto the Hudson dashboard at http://localhost:9090 Add new Hudson job - from Hudson dashboard, select "New Job" - fill in a job name, e.g. "Core" - choose the "Build a free-style software project" radio button - click on OK Configure the new job - you should be sent to the job configuration screen, after the previous step - in the "Build" section, click "Add build step", select "Execute shell" from dropdown menu - in the Command textarea that appears, type the full path to the build script: e.g. /Users/yanni/work/public/Core/pier.sh - in the "Post-build Actions" section, enable "Publish JUnit test result report" - enter "test-reports/*.xml" into the text input labelled "Test report XMLs" that appears. - save the configuration changes (i.e. click "Save"). Run the build job - after saving the new job, you should already be in the new job's control screen. If not, you can navigate there from the dashboard. - start a build by clicking on the "Build Now" link ===== HINTS ===== 1. Click on "Workspace" to see the "Wipe Out Workspace" link. If a PharoDebug.log file is generated, it will be more easy to spot, if the workspace was originally cleaned out. 2. Test your build script in a headful image beforehand. Any flaw will cause the build to stall, and you'll need to abort it (using the Hudson interface), then look at the PharoDebug.log to figure out what went wrong. 3. If the package-cache directory known to your build image still exists, then it will be used (and your packages will appear there, instead of in the Hudson workspace). If it does not exist, then a new package-cache directory will be created in the Hudson job workspace. 4. Monitor the package-cache in the Workspace, to get an idea of the progress of the build. The pier.sh build runs in a 3.5 minutes, building from a local file repository, on a MacBook. 5. Hudson timeout plugin - I've not tried this yet, but if you have a build script error, your build does not abort on its own (or, I've not waited long enough).

7 23

[Pharo-project] how to import an icon
by Tudor Girba Jan. 10, 2010

Jan. 10, 2010

Hi, I would like to import icons from external files in the image. These should be used for menus and buttons. How should I do that? What format should be used? What size? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow."

2 1

[Pharo-project] [update 1.1] #11147
by Marcus Denker Jan. 10, 2010

Jan. 10, 2010

11147 ----- Issue 1761: Unloadable-reloadable Services-Base + DeprecatedPreferences packages (part 1 - 3) ... some packages are dirty. This will be fixed next, together with part 4 and a cleanup of packages that are defined wrongly. Marcus

5 9

[Pharo-project] Pharo Smalltalk â¥
by Guido Stepken Jan. 10, 2010

Jan. 10, 2010

Pharo Smalltalk â¥ ifTrue: [developer honk] That should be valid code :) Have fun! regards, Guido Stepken

3 2

[Pharo-project] Finalization quirk
by Schwab,Wilhelm K Jan. 10, 2010

Jan. 10, 2010

I am trying to add finalization to something and appear to be at a point that finalization does not happen until I open the process browser. Any ideas? Bill

7 14

[Pharo-project] Running untrusted code & sandboxing
by Igor Stasenko Jan. 10, 2010

Jan. 10, 2010

Hello all, I am thinking, what could be done to make Squeak 100% safe when running untrusted code. >From one side, stands a compiler, but from another is run time environment. What i thinking that untrusted code should use own, sepatate class/object hierarchy and do not use any of existing objects from 'unsafe' part of image. If we could use a separation in image, like: [ core [ unsafe ] ] where 'core' is our regular image, or dev image. It is safe to have a references from objects in regular space to ones in unsafe one. But we should prevent leaking a reference to objects in 'core' area being captured by any objects in 'unsafe' area, where untrusted code runs. Ultimately, before running an untrusted code, we should swap the specialObjectsArray, so all things, which VM primitives could see, will be pointing inside unsafe space, and therefore we making impossible to obtain a pointer to any object from 'core' area even when using primitives. But then, once we switch a specialObjectsArray, and if there is no objects pointing back to core, VM will GC it mercilessly. And of course, once untrusted code finished its job, or interrupt occurs, we should be able to switch whole VM context back to core. So, there should be a pointer back to core area. But once we have it, we have a chance that malicious code could find it and break from the jail. Well, maybe with help of specialized compiler, which knows what primitives are unsafe, we could hide this reference? Any other ideas in this regard? -- Best regards, Igor Stasenko AKA sig.

3 4