- Pharo-users - lists.pharo.org

Re: [Pharo-users] Recommended Pharo image updating and Metacello commit policy

by Stephan Eggermont

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

July 24, 2014

Re: [Pharo-users] Recommended Pharo image updating and Metacello commit policy

by Peter UhnÃ¡k

Thank you all so much! This is is exactly what I was looking for and a lot more. On Thu, Jul 24, 2014 at 6:29 PM, Ben Coman <btc(a)openinworld.com> wrote: > Sven Van Caekenberghe wrote: > > Hi Peter, > > I and I guess most people, keep their working image for days to weeks. After all, it is one of the main strengths to have a persistent environment containing all you customisations, all code you loaded, your workspaces, in essence, your world. > > That being said, you should keep all your important code in an MC repository (at least in the package-cache, but better in a real repository, maybe a private one). That way you know your code will survive an image crash. > > > Peter, > You may want to use a local "Global Package Cache" as described here... > http://marianopeck.wordpress.com/2012/05/19/pharo-tips-and-tricks/ > which you can use with StartupLoader as described here... > > http://marianopeck.wordpress.com/2012/05/12/startuploader-running-startup-s… > cheers -ben > > > When and if you want to upgrade, you can now do so. You have to decide if the trouble is worth it. I always keep the old images, just in case. > > HTH, > > Sven > > PS: You can save workspaces to files, or use ScriptManager for multiple ones. There also exists various solutions to move preferences and/or settings around, YMMV. > > On 24 Jul 2014, at 14:58, Peter UhnÃ¡k <i.uhnak(a)gmail.com> <i.uhnak(a)gmail.com> wrote: > > > > 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 > > > > > >

July 24, 2014

Re: [Pharo-users] [Pharo-dev] Deprecator

by Sean P. DeNigris

camille teruel wrote > >> How about 'Reprecator' because you are Rep(airing)(Dep)recations. > This one is fun :) Ha ha ha, worth it for humor value alone! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Deprecator-tp4769844p4769961.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 24, 2014

Re: [Pharo-users] Recommended Pharo image updating and Metacello commit policy

by Ben Coman

July 24, 2014

Re: [Pharo-users] [Pharo-dev] Deprecator

by Camille Teruel

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 >>> >> >

July 24, 2014

Re: [Pharo-users] What should I do when I get a fogbugz "Fix review needed"?

by Ben Coman

July 24, 2014

Re: [Pharo-users] Commandline

by Stephan Eggermont

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

July 24, 2014

Re: [Pharo-users] Deprecator

by stepharo

Yes but again this is a UI Do you think that DynamicWebServer is better than Seaside :)? Even VW people got it right this time. They webserver is called Sioux Stef >> but this is just a tooling issue > Tooling would certainly help, but I think the issue is a little deeper. It's > about the amount of effort required to understand the purpose of the > project. If you're scanning a list of titles of possible projects, and you > see "DeprecationRewriter" or "MigrationHelper", you have an idea whether > it's helpful or not, but something like "Playa" forces you to dig into the > metadata you're talking about. Also, once the project is in core, the same > applies to seeing "Debugger", "Compiler", etc in the browser > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Deprecator-tp4769844p4769909.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

July 24, 2014

Re: [Pharo-users] Commandline

by Norbert Hartl

Am 24.07.2014 um 16:42 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > On 24 Jul 2014, at 16:34, phil(a)highoctane.be wrote: > >> One question I have is how fast the load of an image and processing by an image is when compared with bash. > > Obviously, it is slower, there is a whole image that needs to be loaded, etc. > > $ cat test.st > #!/Users/sven/tmp/pharo4/pharo-vm/Pharo.app/Contents/MacOS/Pharo --headless /Users/sven/tmp/pharo4/Pharo.image st --quit > FileStream stdout nextPutAll: 42 factorial asString; cr. > > $ time ./test.st > 1405006117752879898543142606244511569936384000000000 > > real 0m0.644s > user 0m0.516s > sys 0m0.067s > > So about half a second overhead. > That#s what I meant pixelflux:cmdline norbert$ time ./test.st #('--quit' './test.st') 1405006117752879898543142606244511569936384000000000 real 0m0.414s user 0m0.284s sys 0m0.054s Then I just opened the image executed "ImageCleaner cleanupForProduction" and saved. pixelflux:cmdline norbert$ time ./test-cofp.st #('--quit' './test-cofp.st') 1405006117752879898543142606244511569936384000000000 real 0m0.338s user 0m0.225s sys 0m0.051s If it is an issue at all this is easy to mitigate. A real test would include a complexer scenario where other files are loaded and this way others would be in the same range as pharo I guess. Norbert

July 24, 2014

Re: [Pharo-users] Deprecator

by Sean P. DeNigris

stepharo wrote > but this is just a tooling issue Tooling would certainly help, but I think the issue is a little deeper. It's about the amount of effort required to understand the purpose of the project. If you're scanning a list of titles of possible projects, and you see "DeprecationRewriter" or "MigrationHelper", you have an idea whether it's helpful or not, but something like "Playa" forces you to dig into the metadata you're talking about. Also, once the project is in core, the same applies to seeing "Debugger", "Compiler", etc in the browser ----- Cheers, Sean -- View this message in context: http://forum.world.st/Deprecator-tp4769844p4769909.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 24, 2014