- Pharo-users - lists.pharo.org

ZnUrl>>#= - Why Require Same Classes?
by Sean P. DeNigris March 24, 2016

March 24, 2016

= anObject ^ self class == anObject class ... Most of the time, I've seen a test for #species, not class. This matters because I have a custom ZnUrl subclass that I'd like to be equal to a ZnUrl pointing to the same place. While we're on the subject, I'm not an expert on hashing, but isn't it a problem that ZnUrl>>#hash refers to #segment, which is not immutable? ----- Cheers, Sean -- View this message in context: http://forum.world.st/ZnUrl-Why-Require-Same-Classes-tp4886102.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

2 3

patterns for representing enumerations/constants
by Peter UhnÃ¡k March 23, 2016

March 23, 2016

Hi, as this probably doesn't have one solution I am interested in your approach, if you have any. The problem is that often you want to create instances (or just return constants) in some particular domain, e.g. Color red. Color blue. Unfortunately this doesn't scale, because putting unary methods on the class-side is a good way to break your image. *1) capitalize* doesn't follow method naming conventions Color Red. ParticipantType Organization (uncapitalized returns ClassOrganization) VisibilityKind Package (package returns package) *2) have it on instance-side* need for an extra singleton and more typing Color default red. ParticipantType default organization. VisibilityKind default package. maybe #enum could work better? Color enum red. VisibilityKind enum package. *3) use ALLCAPS* looks like C/Javaâ¦ ugly af also same issue as 1) Color RED. ParticipantType ORGANIZATION. VisibilityKind PACKAGE. *4) use some prefix/suffix?* may not be enough, can be confusing when implementing a domain with given specifications Color redColor. ParticipantType organizationType. VisibilityKind packageKind *5) something better?* All the above work (obviously) but all are broken to some extentâ¦ so it's picking the best of the worst. -_- Any ideas appreciated, Peter

6 11

Setup a Launcher distribution for Pharo trainings/presentations on Windows
by Torsten Bergmann March 23, 2016

March 23, 2016

Hi, I was asked on #slack by user embee (Martin Baehr) how he can create an up to date setup with "PharoLauncher" configuration locally that he can afterwards easily distribute ("unzip and go") to 40 Windows PCs for a training/presentation. He was preparing Pharo for Singapore FOSSASIA conference workshop at the science center computer lab. I helped him with the following short guide that may be useful to others too. Have fun T. ------------------------------------------------------------------------------------------------------------------------------------------------- A. Portable version of Launcher vor Windows =========================================== 1. Go to https://ci.inria.fr/pharo/view/Launcher/job/Launcher/ and click on "VERSION=stable" for a green build 2. Download "Pharo-win.zip" (Direct link is https://ci.inria.fr/pharo/view/Launcher/job/Launcher/PHARO=40,VERSION=stabl…) 3. Extract this to c:\ so you end up with a directory "c:\Pharo" B. Create some folders ====================== 4. Create a new folder "images" 5. Create a new folder "vm" with two subfolders "spur" and "nonspur" So you end up with - Pharo !- images !- vm !- spur !- nonspur C. Install stable "non-Spur" VM =============================== The existing stable VM (before the introduction of Spur) is required for all "PreSpur" images with image version <= 50496 (so latest Pharo 4 and initial images when Pharo 5 was started before switching to Spur during Pharo 5 development) 6. Visit http://files.pharo.org/vm/pharo/win/ and download "Pharo-VM-win-stable.zip" 7. This is the Pharo 4 stable Cog VM. Extract the contents to "C:\Pharo\vm\nonspur" 8. Copy the source files C:\Pharo\PharoV10.sources also to C:\Pharo\vm\nonspur C:\Pharo\PharoV20.sources also to C:\Pharo\vm\nonspur C:\Pharo\PharoV30.sources also to C:\Pharo\vm\nonspur C:\Pharo\PharoV40.sources also to C:\Pharo\vm\nonspur D. Install latest Spur VM ========================= The new, fast and shiny Spur VM is required for all "Spur" images with image version 50497 onwards (so latest Pharo 5) 9. Visit http://files.pharo.org/vm/pharo-spur32/win/ and download "PharoVM-Spur32-win-latest.zip" 10. This is the "bleeding edge" Spur VM. Extract the contents to "C:\Pharo\vm\spur" 11. Copy only the source file C:\Pharo\PharoV40.sources also to C:\Pharo\vm\spur E. Configure Pharo Launcher =========================== 11. Start C:\Pharo\Pharo.exe by double clicking on it, this will open the Pharo Launcher window 12. At the bottom right corner of the Window there is a button called "Open Settings". This opens the settings browser for Pharo Launcher. Click on the node "PharoLauncher" in the settings tree. 13. For the setting "Spur VM Full Path" enter ".\vm\spur\Pharo.exe" and hit ENTER 14. For the setting "VM Full Path" enter ".\vm\nonspur\Pharo.exe" and hit ENTER F. Hack the "images" folder location to be relative =================================================== 15. When you try to change "Location of your images" to be relative like ".\images" you will notice that it always changes back to an absolute path "C:\Pharo\images". So we need to hack this: 16. Hit "SHIFT" + "ENTER" to open the Pharo Spotter. Enter "PhLDirectoryBasedImageRepository" to open a browser on this class. and change the class method #location to look like that location ^ FileSystem workingDirectory / 'images' 17. Close the class browser, close the settings browser and leave the Pharo Launcher by clicking on "Quit" in the bottom right corner. Note that the launcher image is saved on exit - so our code change will be in effect when we start Launcher again. Now ZIP the c:\Pharo folder and you can extract it on any computer that you like. So when you distribute the ZIP the image folder should be clean. But you can also download and include preconfigured images that you like your audience to be working with. G. Sharing caches ================= With the above setup each time you download and start an image using the Launcher a new "package-cache" for Monticello/Metacello downloads will be created for each image directory. To avoid such a cache per image and use a general cache for all images it is helpful to change the package-cache location in each image. This can easily be done: 18. Start an image and evaluate StartupPreferencesLoader preferencesGeneralFolder to find out which preferences folder usually is used. In my example this is C:\Users\root\AppData\Roaming\pharo 19. Go to this folder and create a file called "startup.st" with the following contents: |mczCache| mczCache := 'C:\Software\Pharo\cache' asFileReference. MCCacheRepository cacheDirectory: mczCache. UIManager inform: 'Package cache set to', mczCache fullName If you solely work with the setup and following our path logic you can even give this as a relative path in the startup script: mczCache := FileSystem workingDirectory parent parent / 'package-cache' Details on further startup customization can be found on https://marianopeck.wordpress.com/2012/05/12/startuploader-running-startup-…

5 4

Setup a Launcher distribution for Pharo trainings/presentations on Windows
by Torsten Bergmann March 23, 2016

March 23, 2016

Hi Martin, >the kids were more interested in IoT and android workshops than learning smalltalk. Yes - I played lately with some stuff myself like IBeacons (which you could get now for small money already) and BLE on Android. The Smart Mirror is also a nice idea. All cool stuff as well. >i need to work on a more capturing introduction for next time. >or maybe look into smalltalk for robots or something like that. Maybe the Pi would be interesting too next time: https://www.youtube.com/watch?v=sfxFqQIuawg https://medium.com/concerning-pharo/pharo-pi-9eef257b6a21 Bye T.

1 0

[Pillar] Logo for Pillar
by Thibault ARLOING March 23, 2016

March 23, 2016

Hi, With a mate, we've worked on a logo for Pillar. We just want feedbacks on it. You can fin the logo join files. thanks :) Good afternoon, Thibault

11 13

Seaside 3.1 and 3.2 in Pharo 5
by Johan Brichau March 23, 2016

March 23, 2016

Hi Pharoers, If you are looking to use Seaside in Pharo 5, please go ahead and let us know if you run into any issues. Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are green [1]. Also: I know the finalization of 3.2.0 is long overdue, so news about that is coming soon. cheers, Johan [1] https://ci.inria.fr/pharo-contribution/job/Seaside/ <https://ci.inria.fr/pharo-contribution/job/Seaside/> âLoad release 3.1" Metacello new configuration: 'Seaside3'; repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; version: #'release3.1'; load. âLoad pre-release 3.2" Metacello new configuration: 'Seaside3'; repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; version: #â3.2.0'; load

4 5

Re: [Pharo-users] [Pharo-dev] 3 new Pharo videos
by Torsten Bergmann March 22, 2016

March 22, 2016

1 0

Pharo launcher in homebrew cask
by Filip Krikava March 22, 2016

March 22, 2016

Hi, I find Pharo launcher incredibly useful and I was surprised not to find it in homebrew cask [1]. Pharo itself is there. I have therefore created a PR: https://github.com/caskroom/homebrew-cask/pull/19956 /cheers Filip [1] https://github.com/caskroom/homebrew-cask

4 3

What frameworks/libraries are available for creating programming languages with Pharo
by Dimitris Chloupis March 22, 2016

March 22, 2016

If lisp is ideal for creating new languages so is Smalltalk so I was wondering what kind of libraries there are out there for helping with the creation of new languages in Pharo. I know about SmaCC and PettitParser , what else is out there ?

2 2

FLMethodChanged: Materialization error. Method DmQuartalsplan>>#initialize: changed its bytecodes.
by Johannes Brauer March 22, 2016

March 22, 2016

Hi, I am trying to port a pharo2 application to pharo4. Therefore I have to migrate some fuel files from version 1.9 to 1.9.4. I've done this using the script shown in the EnterprisePharo Book in my pharo2 image, no problem. But trying to load the migrated fuel file into my pharo4 image I get the error message shown above. The source code of the initialize methods is the same in both images, of course. But the byte codes differ: Pharo2: 37 <70> self 38 <42> pushLit: SortedCollection 39 <8F 02 00 08> closureNumCopied: 0 numArgs: 2 bytes 43 to 50 â¦ Pharo4: 37 <70> self 38 <40> pushLit: SortedCollection 39 <8F 02 00 08> closureNumCopied: 0 â¦ What can I do? Johannes

2 4