July 2014 - Pharo-users - lists.pharo.org

export roassal views
by rosariosm July 25, 2014

July 25, 2014

Hi, I have the following problem when i try to export a view into a png file. I use a RTMapBuilder as an example: b := RTMapBuilder new. b countries: RTMapBuilder countries. b view canvas buildMorph *extent: view view canvas camera encompassingRectangle extent ;* exportAsPNG. if i don't specify the rectangle extent (bold line), i can export without problem but i cant see the complete image. on the other hand, if a specify the rectangle extent, an error occurs. see both examples: 1) without extent <http://forum.world.st/file/n4767944/prueba2.png> 2) with extent <http://forum.world.st/file/n4767944/prueba.png> Anyone knows what is happenning?? Thanks, Rosario -- View this message in context: http://forum.world.st/export-roassal-views-tp4767944.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

2 3

Pharo launcher network error for Pharo 4.0 (beta)?
by Tim Mackinnon July 25, 2014

July 25, 2014

I was quite enjoying using Pharo Launcher - but today I am getting ânetwork errorâ for the Pharo4.0 (beta) and Pharo 2.0 (old) trees? Has something changed? Tim

3 5

Re: [Pharo-users] Recommended Pharo image updating and Metacello commit policy
by Stephan Eggermont July 25, 2014

July 25, 2014

If you use a shared package cache, you should be aware of two potential issues: - directories with a large number of files can get slow; - Metacello configurations might load different versions of packages than you'd expect Stephan

3 2

Recommended Pharo image updating and Metacello commit policy
by Peter UhnÃ¡k July 24, 2014

July 24, 2014

Having ~month old pharo image I was wondering what is the recommended way of updating it. Do I just delete everything and download a fresh one every so often (daily?), do I load new changes through Monticello? Does that upgrade the VM though? If the former what about local code I wrote but I don't want to loose or haven't completely finished? Is it possible to export workspace content and load it into fresh image? Do I just create local repository and commit there and once I am satisfied with the results I push them up (to STHub/wherever)? Or should I always push to remote repo even if the commits break the package (I would assume that should be semi-guarded by creating ConfigurationOfMyProject)? I am used to Git and I still can't wrap my head around this Monticello thing. :( Thanks, Peter

5 5

Re: [Pharo-users] [Pharo-dev] Deprecator
by Camille Teruel July 24, 2014

July 24, 2014

On 24 juil. 2014, at 18:11, Ben Coman <btc(a)openInWorld.com> wrote: > Camille Teruel wrote: >> >> >> On 24 juil. 2014, at 17:05, stepharo <stepharo(a)free.fr> wrote: >> >>> Camille >>> >>> Ammonite is not that sezzy :) >> >> Because it has tentacles? :-D >> >>> May be >>> autoRepair >>> selfRepair :) >> >> Yes for example ;) > > How about 'Reprecator' because you are Rep(airing)(Dep)recations. This one is fun :) > >> >>> >>> Stef >>> On 24/7/14 14:34, Camille Teruel wrote: >>>> Hello Pharo users, >>>> >>>> I'm pleased to announce the release of Deprecator. >>>> It's a prototype of a small tool that permits you to deprecate method by annotating them with a <deprecated: ...> pragma. >>>> This pragma takes a rewrite expression as argument that specifies how to rewrite the message send to the deprecated method. >>>> If such a deprecated method is executed, a warning is thrown and a debugger opens. >>>> This debugger has a little 'Rewrite' button that permits to rewrite the sending method according to the rewrite expression and then resume the execution with the new rewritten sending method :) >>>> The implementation is a proof-of-concept and is a bit hacky here and there, but it works. >>>> >>>> Example: >>>> >>>> You have a class C with a method that you deprecate. >>>> Its rewrite expression tells that if it's executed as the result of a message send of the form: >>>> <receiver> deprecatedMethodArg1: <arg1> arg2: <arg2>, >>>> this message send should be rewritten to: >>>> <receiver> replacementMethodArg1: <arg2> arg2: <arg1>. >>>> Note you can change the order of arguments or even the receiver. >>>> >>>> C>>deprecatedMethodArg1: o1 arg2: o2 >>>> <deprecated: '`@receiver replacementMethodArg1: `@arg2 arg2: `@arg1'> >>>> ^ #deprecated >>>> >>>> C>>replacementMethodArg1: o1 arg2: o2 >>>> ^ #replacement >>>> >>>> C>>senderMethod >>>> ^ self deprecatedMethodArg1: 1 + 1 arg2: 2 + 2. >>>> >>>> Then if you execute C new senderMethod, and then click on the "Rewrite" button of the debugger, then sending method is rewritten to: >>>> >>>> C>>senderMethod >>>> ^ self replacementMethodArg1: 2 + 2 arg2: 1 + 1. >>>> >>>> and the result is #replacement. >>>> >>>> The repo is on sSmalltalkHub: >>>> MCHttpRepository >>>> location: 'http://smalltalkhub.com/mc/CamilleTeruel/Deprecator/main' >>>> user: '' >>>> password: '' >>>> >>>> I hope for comments, feature suggestions, code reviews, contributors, etc :) >>>> BTW, if you have a better name for this project let me know! >>>> For example, I thought about Ammonite because it's an extinct animal (analogy with deprecated) and it fits the sea naming theme. >>>> >>>> Cheers, >>>> Camille >>> >> >

2 1

What should I do when I get a fogbugz "Fix review needed"?
by Tim Mackinnon July 24, 2014

July 24, 2014

If I report a bug in fogbugz and it later gets fixed, I get an email with the slice its fixed in. So Iâve loaded the slice into the latest image - then Iâve done âmergeâ (Iâm still not clear on whether I should do merge or load? I think I understand that I need merge to just get those fixes?). Having retested my bug, and found that it has been fixed - I entered a comment saying which image version I tested it in, but then Iâm not sure what I should do with the status? Can someone just clarify that for me? Tim

5 4

Re: [Pharo-users] Commandline
by Stephan Eggermont July 24, 2014

July 24, 2014

With a smaller image, it gets a lot faster (except the first time) total 149096 drwx------@ 12 stephan staff 408 24 jul 17:58 . drwx------+ 3243 stephan staff 110262 24 jul 17:48 .. -rw-r--r--@ 1 stephan staff 6148 24 jul 17:49 .DS_Store -rw-rw-r--@ 1 stephan staff 10802235 24 jul 17:58 Pharo-40037.changes -rw-rw-r--@ 1 stephan staff 27244188 26 jun 00:35 Pharo-40037.image -rw-rw-r--@ 1 stephan staff 5603025 24 jul 17:52 Pharo-minimal-40122.changes -rw-rw-r--@ 1 stephan staff 6109432 24 jul 11:44 Pharo-minimal-40122.image drwxr-xr-x@ 3 stephan staff 102 3 jul 00:33 Pharo.app -rw-r--r--@ 1 stephan staff 395 24 jul 17:57 PharoDebug.log -rw-r--r-- 1 stephan staff 26546528 29 apr 12:30 PharoV30.sources -rwxr-xr-x 1 stephan staff 201 24 jul 17:51 test.st -rwxr-xr-x 1 stephan staff 193 24 jul 17:57 test2.st stephanontsimac:40122 stephan$ time ./test.st 1405006117752879898543142606244511569936384000000000 real 0m1.005s user 0m0.149s sys 0m0.062s real 0m0.297s user 0m0.148s sys 0m0.051s real 0m0.281s user 0m0.145s sys 0m0.050s vs a 40037 image real 0m0.501s user 0m0.325s sys 0m0.070s real 0m0.475s user 0m0.328s sys 0m0.066s real 0m0.499s user 0m0.346s sys 0m0.073s

1 0

Deprecator
by Camille Teruel July 24, 2014

July 24, 2014

Hello Pharo users, I'm pleased to announce the release of Deprecator. It's a prototype of a small tool that permits you to deprecate method by annotating them with a <deprecated: ...> pragma. This pragma takes a rewrite expression as argument that specifies how to rewrite the message send to the deprecated method. If such a deprecated method is executed, a warning is thrown and a debugger opens. This debugger has a little 'Rewrite' button that permits to rewrite the sending method according to the rewrite expression and then resume the execution with the new rewritten sending method :) The implementation is a proof-of-concept and is a bit hacky here and there, but it works. Example: You have a class C with a method that you deprecate. Its rewrite expression tells that if it's executed as the result of a message send of the form: <receiver> deprecatedMethodArg1: <arg1> arg2: <arg2>, this message send should be rewritten to: <receiver> replacementMethodArg1: <arg2> arg2: <arg1>. Note you can change the order of arguments or even the receiver. C>>deprecatedMethodArg1: o1 arg2: o2 <deprecated: '`@receiver replacementMethodArg1: `@arg2 arg2: `@arg1'> ^ #deprecated C>>replacementMethodArg1: o1 arg2: o2 ^ #replacement C>>senderMethod ^ self deprecatedMethodArg1: 1 + 1 arg2: 2 + 2. Then if you execute C new senderMethod, and then click on the "Rewrite" button of the debugger, then sending method is rewritten to: C>>senderMethod ^ self replacementMethodArg1: 2 + 2 arg2: 1 + 1. and the result is #replacement. The repo is on sSmalltalkHub: MCHttpRepository location: 'http://smalltalkhub.com/mc/CamilleTeruel/Deprecator/main' user: '' password: '' I hope for comments, feature suggestions, code reviews, contributors, etc :) BTW, if you have a better name for this project let me know! For example, I thought about Ammonite because it's an extinct animal (analogy with deprecated) and it fits the sea naming theme. Cheers, Camille

4 5

Browse list of methods
by Mark Rizun July 24, 2014

July 24, 2014

Hi guys, If I have list of methods, how can I open a browser containing only this methods? Best, Mark -- View this message in context: http://forum.world.st/Browse-list-of-methods-tp4769871.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

2 2

Package Dependencies Analysis : new features
by Baptiste Quide July 24, 2014

July 24, 2014

Hello Pharos Users, Since the first release of Package Dependencies Analysis, here is a summary of improvements : - tool is available in World Menu (Tools > Package Dependencies Browser) : choose your packages and browse dependencies. - add/remove packages into the analysis. - you can refresh the current analysis manually (for instance if you change a piece of code to remove/add dependency) - filter the packages displaying by name - button "find cycles" allows to find all cycles in the system where the selected packages in the tree are (it could take a while the first time you click) - contextual menu (right click) to browse scoped dependencies or find cycles among the selected packages in the tree Then, in the window displaying cycles among packages : - only dependencies among packages in the cycle are displaying (no outgoing dependencies) - packages appear by order (if you see aCycle : A, B, C, the cycle is A -> B -> C -> A) See more details : http://www.baptistequide.fr/packagedependencies.php Regards, Baptiste

3 2