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

Re: [Pharo-users] Pharo launcher network error for Pharo 4.0 (beta)?

by Damien Cassou

On Fri, Jul 25, 2014 at 1:17 PM, Tim Mackinnon <tamackinnon(a)gmail.com> wrote: > I've tried it at home and it works fine, yesterday it didn't work in the > office (just 4.0 and 2.0) - some there must be some weird networking going > on in that office. if there is anything you can do to the source code to make it work at your office, please do and share. Thank you -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 25, 2014

[Tip] Image init scripts when working with PharoLauncher

by Torsten Bergmann

PharoLauncher [1] allows you to work with many Pharo images. You can download fresh images, clone existing ones and with its access to the Pharo CI it allows you to easily reproduce errors in specific Pharo image versions. I REALLY like this tool when working with Pharo. There is a customizable hardware key on my laptop that I can just press to open PharoLauncher, manage and launch the images and dive into the world of Pharo. To optimize my Pharo "easy access workflows" further I wanted all the images that I started with PharoLauncher: - to share a common metacello repository cache (where all the mcz are stored independent from image location) for faster loading - to have the possibility to preset the Squeaksource, SS3 and STHub password already - to set my authors name All this is already explained in Marianos blog posts [2] and [3] and the PharoEnterprise book [4]. Nonetheless I would like to share the script that I personally use. Maybe (in an adopted version) it is usefull for other PharoLauncher users as well: ===================================================================== COMMON SETTINGS FOR ALL PHARO IMAGES WHEN STARTED USING PHAROLAUNCHER ===================================================================== Open any Pharo 3.0/4.0 image and execute StartupPreferencesLoader preferencesGeneralFolder fullName in a workspace to find out the common preferences folder on your local machine. You can put a Smalltalk script into this folder, for instance "initAllImages.st" that is evaluated each time an image runs. I've found the following script very useful: ----------------------------------------------------------------- | sharedPackageCacheDirectory | "Never apply to PharoLauncher itself" (SmalltalkImage current imageName includesSubstring: 'Launcher') ifTrue: [ ^self ]. "ask if script should be applied" (UIManager default confirm: 'Apply init script from ', StartupPreferencesLoader preferencesGeneralFolder fullName,' to image') ifFalse: [^self ]. "Use a shared package cache to store Monticello MCS files for all images" sharedPackageCacheDirectory := 'C:\Pharo\commonpackage-cache' asFileReference ensureCreateDirectory; yourself. MCCacheRepository default directory: sharedPackageCacheDirectory. "Set password for Squeaksource" (MCRepositoryGroup default repositories select: [:each | (each isKindOf: MCHttpRepository) and: [((each locationWithTrailingSlash includesSubstring: 'www.squeaksource.com') or: [each locationWithTrailingSlash includesSubstring: 'http://ss3.gemstone.com/ss/'])] ]) do: [:each | each user: 'squeaksourceuser'; password: 'secretsqueaksourcepassword']. "Set password for SmalltalkHub (hub and HTTP repos)" (MCRepositoryGroup default repositories select: [:each | (each isKindOf: MCSmalltalkhubRepository) and: [each locationWithTrailingSlash includesSubstring: 'smalltalkhub.com'] ]) do: [:each | each user: 'PharoUser'; password: 'sthubpassword']. (MCRepositoryGroup default repositories select: [:each | (each isKindOf: MCHttpRepository) and: [each locationWithTrailingSlash includesSubstring: 'smalltalkhub.com'] ]) do: [:each | each user: 'PharoUser'; password: 'sthubpassword']. "Set author name" Author fullName: 'PharoUser'. UIManager default inform: 'Script applied'. ----------------------------------------------------------------- Hope it is usefull for others too. Bye T. [1] http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher [2] http://marianopeck.wordpress.com/2012/05/19/pharo-tips-and-tricks/ [3] http://marianopeck.wordpress.com/2012/05/12/startuploader-running-startup-s… [4] https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Startup…

July 25, 2014

Re: [Pharo-users] Pharo launcher network error for Pharo 4.0 (beta)?

by Tim Mackinnon

I've tried it at home and it works fine, yesterday it didn't work in the office (just 4.0 and 2.0) - some there must be some weird networking going on in that office. Anyway - glad I can use it at home, as its a very handy launcher! Thanks for creating it, and to those helping maintain it. Tim -- View this message in context: http://forum.world.st/Pharo-launcher-network-error-for-Pharo-4-0-beta-tp476… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 25, 2014

Reference documentation on Trait

by Hilaire

Hi, Do we have such document(s)? Thanks Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://launchpad.net/istoa

July 25, 2014

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

by Peter UhnÃ¡k

But isn't that a bit... weird to use cache to move data from one image to another? I would expect cache to be just a cache even if in reality it is just a regular repository. On Fri, Jul 25, 2014 at 12:48 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 24.07.2014 um 23:43 schrieb Stephan Eggermont <stephan(a)stack.nl>: > > > 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; > > I don't think that this is an issue with todays filesystems. If you want > to cleanup a package-cache you could use something like this > > ---- > $ cat bin/clean-package-cache > #!/bin/sh > > find /opt/mc/package-cache/ -atime +180d -exec mv {} ~/.Trash \; > ââ > > It moves all files that have not been accessed for half a year into the > trash folder (I'm a Mac user). You can have this run automatically if add a > file > > ---- > $ cat Library/LaunchAgents/org.selfish.cleanPackageCache.plist > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" " > http://www.apple.com/DTDs/PropertyList-1.0.dtd"> > <plist version="1.0"> > <dict> > <key>Label</key> > <string>org.selfish.cleanPackageCache</string> > <key>ProgramArguments</key> > <array> > <string>/Users/norbert/bin/clean-package-cache</string> > </array> > <key>StartInterval</key> > <integer>86400</integer> > </dict> > </plist> > ââ > > > - Metacello configurations might load different versions of packages > than you'd expect > > Indeed > > Norbert >

July 25, 2014

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

by Norbert Hartl

Am 24.07.2014 um 23:43 schrieb Stephan Eggermont <stephan(a)stack.nl>: > 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; I don't think that this is an issue with todays filesystems. If you want to cleanup a package-cache you could use something like this ---- $ cat bin/clean-package-cache #!/bin/sh find /opt/mc/package-cache/ -atime +180d -exec mv {} ~/.Trash \; ââ It moves all files that have not been accessed for half a year into the trash folder (I'm a Mac user). You can have this run automatically if add a file ---- $ cat Library/LaunchAgents/org.selfish.cleanPackageCache.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>org.selfish.cleanPackageCache</string> <key>ProgramArguments</key> <array> <string>/Users/norbert/bin/clean-package-cache</string> </array> <key>StartInterval</key> <integer>86400</integer> </dict> </plist> ââ > - Metacello configurations might load different versions of packages than you'd expect Indeed Norbert

July 24, 2014

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