February 2013 - Pharo-dev - lists.pharo.org

[Pharo-project] Issue 7534 LazyListMorph>>selectionFrameForRow: fails with a 'should not happen' IS BACK
by Sean P. DeNigris Feb. 20, 2013

Feb. 20, 2013

http://code.google.com/p/pharo/issues/detail?id=7534 -- View this message in context: http://forum.world.st/Issue-7534-LazyListMorph-selectionFrameForRow-fails-w… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

8 15

[Pharo-project] [update 2.0] #20559
by Marcus Denker Feb. 20, 2013

Feb. 20, 2013

20559 ----- Issue 7492: Failing test: MCRepositoryAuthorizationTest>>#testStoredCredentialsUsesMostSpecific http://code.google.com/p/pharo/issues/detail?id=7492 Issue 7341: Failing test: ReleaseTest>>#testInstalledMethodsWithIncorrectTrailerKind http://code.google.com/p/pharo/issues/detail?id=7341 Diff information: http://ss3.gemstone.com/ss/Pharo20/Traits-MarcusDenker.458.diff http://ss3.gemstone.com/ss/Pharo20/Monticello-MarcusDenker.775.diff

1 0

[Pharo-project] Monticello and SS3 discrepancy in Pharo 2.0
by phil＠highoctane.be Feb. 19, 2013

Feb. 19, 2013

Got this thing biting me while testing the relase: I added a project of mine from the ss3.gemstone.com system and the Monticello registration over there says: MCHttpRepository location: 'http://ss3.gemstone.com/ss/HO-Experiments' user: 'PBK' password: '' I add that into Pharo as a ss3 repository. There I am asked for: MCGemstoneRepository location: 'http://ss3.gemstone.com/ss/' user: '' password: '' I didn't noticed the MCGemstoneRepository instead of MCHttpRepository and copy/pasted as usual. Then, error. Took a minute to see why and get my mcz back. So, either SS3 has to change the registration information or Pharo does something weird with SS3. I don't know. Guess I need to put things in SmalltalkHub :-) Phil

4 11

[Pharo-project] Pharo 2.0 UITheme current solidMenuIcon (and for sure some friends) are wrong due to VM problem
by phil＠highoctane.be Feb. 19, 2013

Feb. 19, 2013

I managed to load my code into Pharo 2.0 without problems. Sweet! There is some direct use of morphic all looks like to work well. Sound also works nicely. Still an issue with the World Menu where I do use menuCommandOn with an icon set to: UITheme current solidMenuIcon The icon looks quite warped or plain wrong (looks like a crappy cloud). The code of the method in 1.4 is solidMenuIconContents "Private - Method generated with the content of the file /home/plantec/dvpt/Pharo/Sprint-10-09/Icons/solidMenu.png" ^ 'iVBORw0KGgoAAAANSUhEUgAAAA4AAAAQCAYAAAAmlE46AAAABHNCSVQFBQUBSsjp7wAAAE5J REFUeF5jgACO/wykA5AmGCZGHVaNxGISNO648AO7RpAEIYxXI8lOJaSRIqeiaSbeRrwaSXAu lZxKQsiSEh0oSY+cJEdissORGUjLWgBvFzCDqCcU6AAAAABJRU5ErkJggg==' and in 2.0 it is solidMenuIconContents "Private - Method generated with the content of the file /home/plantec/dvpt/Pharo/Sprint-10-09/Icons/solidMenu.png" ^ 'iVBORw0KGgoAAAANSUhEUgAAAA4AAAAQCAYAAAAmlE46AAAABHNCSVQFBQUBSsjp7wAAAE5J REFUeF5jgACO/wykA5AmGCZGHVaNxGISNO648AO7RpAEIYxXI8lOJaSRIqeiaSbeRrwaSXAu lZxKQsiSEh0oSY+cJEdissORGUjLWgBvFzCDqCcU6AAAAABJRU5ErkJggg==' Looks like the same to me. So, something isn't right. I tried the image with the StackVM and there, the icon is right. It has the right colors instead of a white cloud. Maybe due to a plugin, I don't know. The VM I tried is the latest one I got with the ciPharoVM.sh script. My self compiled PharoVM exhibits the same problem. CogVM shows the right icons (even if it complains that the VM is too old for the image) Smalltalk vmVersion gives: 'CoInterpreter VMMaker.oscog-eem.264 uuid: 64e76092-8af7-449f-9188-e65f3bd1f08d Feb 5 2013 StackToRegisterMappingCogit VMMaker.oscog-eem.264 uuid: 64e76092-8af7-449f-9188-e65f3bd1f08d Feb 5 2013 VM: r2678 http://www.squeakvm.org/svn/squeak/branches/Cog Plugins: r2545 http://squeakvm.org/svn/squeak/trunk/platforms/Cross/plugins ' I tried with the code generated to create a cog VM from Esteban and there it works fine. Smalltalk vmVersion gives there: 'CoInterpreter VMMaker-oscog-EstebanLorenzano.231 uuid: a9e39f38-e1fa-4851-a3a3-1a0f1f7a4062 Feb 15 2013 StackToRegisterMappingCogit VMMaker-oscog-EstebanLorenzano.231 uuid: a9e39f38-e1fa-4851-a3a3-1a0f1f7a4062 Feb 15 2013 git://gitorious.org/cogvm/blessed.git Commit: 63aa6ed8a070fc730224b496e0dda7c3f8482e10 Date: 2013-02-14 11:43:21 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> ' Here is the version for the problematic VM (latest downloaded from ci) Smalltalk vm version 'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Feb 18 2013 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Feb 18 2013 git://gitorious.org/cogvm/blessed.git Commit: 05ed728452dc92732f9f23ce24a3c32bfdc0f4b8 Date: 2013-02-15 17:04:09 +0100 By: Igor Stasenko <siguctua(a)gmail.com> Jenkins build #14519 ' Maybe some NB dark magic going on... On the other side, loading PNGs from disk worked okay. (As the larger icons on the background of the screenshot demonstrate). Hope you can figure out why there is such an issue. Phil

2 2

[Pharo-project] Slices and monticello - add to package... or add package to ... ? + procedure
by phil＠highoctane.be Feb. 19, 2013

Feb. 19, 2013

I was educating myself on slices. Maybe I'll be able to contribute a bit properly one of these days. Reading from http://code.google.com/p/pharo/wiki/HowToContribute. Creating a slice in my own package-cache is all fine. Now, to add it to the PharoInbox, I watched the screencast: http://www.pharocasts.com/2010/03/how-to-contribute-to-pharo.html There is this thing were we need to go to the PharoInbox repo in the right pane on monticello. The right click and select the Add to package.. option and then select the slice. All right, I can understand but this feels like unnatural to be on a repository and ask to "Add to package..." where what I want to do is to add the package to the repository. I understand that this is required to have the repository associated with the package so that I can save the package to one of its associated repositories. Maybe "Associate with package..." may be more helpful. Also the procedure on HowToContribute is not right anymore. As the UI changed. There is my version: # How to make a slice Slice: Your modification affect more than one package: you have to create a SLICE package in your package cache A SLICE is just a package with dependents ones, so you have to indicate the dependent packages. ## Procedure Open the Monticello browser. You should see one or more packages marked as modified (they have an asterisk before their name). Select your package-cache repository on the right hand pane. Create the new SLICE (click on the ''+SLICE'' button) and follow the instructions. ### Old way _Mark all_ the modified packages (the ones with asterisks before their names) required by your SLICE package. To do this, right click on the SLICE package in the left pane and select ''add required package'', then select the package from the next menu. Repeat for all modified packages. (Yeah, boring) ### New way (Pharo 2.0 at least) Put the issue tracker number in the Issue Number box and hit "Grab" to get the title of the issue. The (un)select in the list of "Dirty Packages to be included in the slice" ### Back to regular programming... Select your package-cache repository, this will enable the save button. Save the SLICE package (click on the ''Save'' button). An mcz package will be saved in your cache for the SLICE package and all the modified packages. (Name: something along the lines of SLICE-Issue-XXXX-YYYY-ZZZZ-Comment-Initials.1) You will be prompted for a log message (for each one of them ?), type a useful comment for the first package, (copy it and paste it on the others - sure?). Make sure to give the number of the issue your SLICE addresses in the comment. Publish the package to PharoInbox repository. # Hwo to publish to the PharoInbox repository Open monticello. Select the PharoInbox repository on the right pane. Right click the repository and select "Add to package..." (this will associate the package to the repository). You'll be presented with a list of possible packages. Pick up your slice. Then, go back to Monticello Browser with a list of packages on the left and a list of repositories on the right. Select on your slice on the left. Select the PharoInbox repository on the right. Click the Save button on the top bar. That's it, slice now in PharoInbox. Phil

2 1

[Pharo-project] Pharo By Example 2 Book - Assembled Files in PDF form.
by phil＠highoctane.be Feb. 19, 2013

Feb. 19, 2013

Hi all, I struggled with the fact that the PBE2 book was in tex format and not all chapters were together in a single PDF. So, I ran the scripts in order to get a version with all the parts put together. This should be made into a Jenkins job I think so that we can have the PBE2 and other books in PDF form for easier dissemination. Here is the current assembly: https://www.dropbox.com/s/t8pesgxsovy61k5/PBE2-Assembled-20130213.pdf 412 pages of Pharo explanations. How lovely! Enjoy, Phil

5 11

[Pharo-project] [update 2.0] #20558
by Esteban Lorenzano Feb. 19, 2013

Feb. 19, 2013

20558 ----- Issue 7542: invalid selection of classes when old style keybindings are activated http://code.google.com/p/pharo/issues/detail?id=7542 Issue 7543: add ReleaseTest for obsolete Behaviors http://code.google.com/p/pharo/issues/detail?id=7543 Diff information: http://ss3.gemstone.com/ss/Pharo20/Tools-EstebanLorenzano.1049.diff http://ss3.gemstone.com/ss/Pharo20/Tests-EstebanLorenzano.512.diff http://ss3.gemstone.com/ss/Pharo20/Nautilus-EstebanLorenzano.430.diff http://ss3.gemstone.com/ss/Pharo20/Keymapping-Core-EstebanLorenzano.142.diff

1 0

[Pharo-project] [update 2.0] #20557
by Esteban Lorenzano Feb. 19, 2013

Feb. 19, 2013

20557 ----- Issue 7530: obsolete Behavior in image http://code.google.com/p/pharo/issues/detail?id=7530 Issue 7458: Changing method in debugger (in a block activation) changes CompiledMethod but not source code http://code.google.com/p/pharo/issues/detail?id=7458 Issue 7110: Fix Refresh of ProgressBar http://code.google.com/p/pharo/issues/detail?id=7110 Issue 7085: UTC seconds conversion inconsistent http://code.google.com/p/pharo/issues/detail?id=7085 Diff information: http://ss3.gemstone.com/ss/Pharo20/Traits-EstebanLorenzano.457.diff http://ss3.gemstone.com/ss/Pharo20/Polymorph-Widgets-EstebanLorenzano.773.d… http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1356.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-EstebanLorenzano.1314.diff http://ss3.gemstone.com/ss/Pharo20/Compiler-EstebanLorenzano.377.diff

1 0

[Pharo-project] [update 2.0] #20556
by Esteban Lorenzano Feb. 19, 2013

Feb. 19, 2013

20556 ----- Issue 7521: Add PostMaterializationAction to Fueled out stack traces http://code.google.com/p/pharo/issues/detail?id=7521 Issue 7509: intersect:ifNone: Error http://code.google.com/p/pharo/issues/detail?id=7509 Issue 7452: After "ImageCleaner cleanUpForProduction" there are obsolete classes http://code.google.com/p/pharo/issues/detail?id=7452 Diff information: http://ss3.gemstone.com/ss/Pharo20/Tools-EstebanLorenzano.1048.diff http://ss3.gemstone.com/ss/Pharo20/SUnit-Utilities-EstebanLorenzano.10.diff http://ss3.gemstone.com/ss/Pharo20/Polymorph-Widgets-EstebanLorenzano.772.d… http://ss3.gemstone.com/ss/Pharo20/Fuel-EstebanLorenzano.748.diff

1 0

[Pharo-project] Fwd: [ci-announces] Deployment of a new version
by Marcus Denker Feb. 19, 2013

Feb. 19, 2013

Begin forwarded message: > From: Emmanuel Jeanvoine <emmanuel.jeanvoine(a)inria.fr> > Subject: [ci-announces] Deployment of a new version > Date: February 19, 2013 3:57:50 PM GMT+01:00 > To: ci-announces(a)inria.fr > > Hello, > > A new version of the continuous integration service will be deployed > soon. You may experience some issues in the following hours. > > Regards, > Emmanuel > > > -- > Emmanuel Jeanvoine Research Engineer > Inria Nancy - Grand Est Office B118 > http://www.inria.fr/nancy Tel +33 3 54 95 86 21

1 0