March 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Setup a Launcher distribution for Pharo trainings/presentations on Windows

by Damien Cassou

Torsten Bergmann <astares(a)gmx.de> writes: > 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. that's amazing work Torsten, thank you very much. What about adding a Jenkins job that would create this automatically? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

March 23, 2016

Re: [Pharo-users] [Pillar] Logo for Pillar

by stepharo

I think more about the ones below the pier :) http://www.routard.com/photos/los_angeles/18237-la_jetee_de_malibu.htm http://fr.dreamstime.com/photos-libres-de-droits-jetÃ©e-avec-le-restaurant-Ã -la-mer-baltique-allemagne-image14938888 but this is not good for a logo. the one that sustain the pier :) It was literally that in fact Le 22/3/16 16:00, Ben Coman a Ã©crit : > On Fri, Mar 18, 2016 at 10:30 PM, Thibault ARLOING > <thibault.arloing(a)hotmail.fr> wrote: >> Hi, >> >> >> With a mate, we've worked on a logo for Pillar. >> >> We just want feedbacks on it. > I like the style. But as a logo I think it is too thin. > > When I think of pillar I think of > http://tinyurl.com/pillar-images > > And for a logo, something like... > http://www.presentation-process.com/wp-content/uploads/powerpoint-pillar-tu… > > Attached is a concept I knocked up. Its too detailed for a logo, and > the font was plagiarized from > http://tinyurl.com/hhc5a3d > but may provide inspiration. > > cheers -ben

March 23, 2016

Beta testers for the Pharo mooc

by stepharo

Hi guys we are looking for beta tester (We do not have yet the english translation for the mooc). If you are interested contact me on stephane.ducasse(a)inria.fr Stef

March 23, 2016

Re: [Pharo-users] Seaside 3.1 and 3.2 in Pharo 5

by Johan Brichau

Torsten pointed me to a typo I made for loading version 3.2.0. This is the correct version: âLoad pre-release 3.2" Metacello new configuration: 'Seaside3'; repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main' <http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'>; version: â3.2.0'; load You could also already use the symbolic version #release3.2, but itâs not released yet :) Metacello new configuration: 'Seaside3'; repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main' <http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'>; version: #'release3.2'; load thx for trying and the feedback! Johan > On 20 Mar 2016, at 19:49, Johan Brichau <johan(a)inceptive.be> wrote: > > 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' <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' <http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'>; > version: #â3.2.0'; > load

March 23, 2016

Re: [Pharo-users] Setup a Launcher distribution for Pharo trainings/presentations on Windows

by stepharo

cool ressource!!! Le 23/3/16 09:45, Torsten Bergmann a Ã©crit : > 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 tohttps://ci.inria.fr/pharo/view/Launcher/job/Launcher/ and click on "VERSION=stable" > for a green build > 2. Download "Pharo-win.zip" > (Direct link ishttps://ci.inria.fr/pharo/view/Launcher/job/Launcher/PHARO=40,VERSION=stable,VM=vm,label=linux/lastSuccessfulBuild/artifact/Pharo-win.zip) > > 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. Visithttp://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. Visithttp://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-… > >

March 23, 2016

Re: [Pharo-users] Setup a Launcher distribution for Pharo trainings/presentations on Windows

by Martin BÃ¤hr

Excerpts from Torsten Bergmann's message of 2016-03-23 09:45:09 +0100: > I was asked on #slack by martin 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. thank you again torsten. you saved me a lot of work there. the workshop went quite well, btw, the audience was enthusiastic. sadly though it was very small too. the kids were more interested in IoT and android workshops than learning smalltalk. i need to work on a more capturing introduction for next time. or maybe look into smalltalk for robots or something like that. greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin BÃ¤hr working in china http://societyserver.org/mbaehr/

March 23, 2016

Setup a Launcher distribution for Pharo trainings/presentations on Windows

by Torsten Bergmann

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

March 23, 2016

Re: [Pharo-users] Customizing SmalltalkEditor context menu issue

by Nicolai Hess

2016-03-22 22:27 GMT+01:00 Ala'a Mohammad <amalawi(a)gmail.com>: > Hi, > > I'm trying to modify the context menu of the code editor through > modification to SmalltalkEditor class >> smalltalkEditorMenuOn: > Hi Ala'a > > testing the modification with > (PragmaMenuBuilder pragmaKeyword: 'smalltalkEditorMenu' model: nil) > menu popUpInWorld > The context menu for Nautilus code pane works a bit different. Can you test if your modifications are working in Workspace (or the workspace are in a basic inspector). > > succeeds, and shows the final shape of the menu that I want (photo > attached), but the actual one used by the system is messed up! (photo > attached) > > I tried also to execute TextEditor class >> initialize, but that did not > help. > > Another thing I did was trying to find senders and references to the > SmalltalkEditor class >> smalltalkEditorMenuOn, and find none! (So who > is calling that with a 'aBuilder'?), and the only implementation of it > is the one I'm trying to update (more confusion - pardon the puzzled > newbie). > The smalltalkEditorMenuOn: method, containing the smalltalkEditorMenu-Pragma is not called explicit. Instead, there is a Method SmalltalkEditor class >> smalltalkEditorMenuKeyword that returns the pragma name ('smalltalkEditorMenu') used to collect all methods using this pragma for defining the menus. For Nautilus, there is another step involved. First it calls SmalltalkEditor yellowButtonMenu this will ask for the pragma (SmalltalkEditor class >> smalltalkEditorMenuKeyword) and builds a menu from every method using this pragma (here only the method SmalltalkEditor class >> smalltalkEditorMenuOn: ). NOW it modifies this menu and adds (from all methods using the pragma <nautilusGlobalSourceCodeMenu> and reorganize some more entries (this is ugly, yes). > > Attached are the photos for the original menu, target menu and the > messed up menu. > > I'm using Pharo 4.0 from the official download for Linux from Pharo.org. > > my system is the following: > Linuxmint 17.1 Rebecca > 3.13.0-37-generic #64-Ubuntu SMP > > What I'm doing wrong? and/or what I'm missing? > > Thanks in advance for the help. > > Regards, > > Ala'a >

March 22, 2016

Re: [Pharo-users] [Pharo-dev] 3 new Pharo videos

by Torsten Bergmann

March 22, 2016

Customizing SmalltalkEditor context menu issue

by Ala'a Mohammad

Hi, I'm trying to modify the context menu of the code editor through modification to SmalltalkEditor class >> smalltalkEditorMenuOn: testing the modification with (PragmaMenuBuilder pragmaKeyword: 'smalltalkEditorMenu' model: nil) menu popUpInWorld succeeds, and shows the final shape of the menu that I want (photo attached), but the actual one used by the system is messed up! (photo attached) I tried also to execute TextEditor class >> initialize, but that did not help. Another thing I did was trying to find senders and references to the SmalltalkEditor class >> smalltalkEditorMenuOn, and find none! (So who is calling that with a 'aBuilder'?), and the only implementation of it is the one I'm trying to update (more confusion - pardon the puzzled newbie). Attached are the photos for the original menu, target menu and the messed up menu. I'm using Pharo 4.0 from the official download for Linux from Pharo.org. my system is the following: Linuxmint 17.1 Rebecca 3.13.0-37-generic #64-Ubuntu SMP What I'm doing wrong? and/or what I'm missing? Thanks in advance for the help. Regards, Ala'a

March 22, 2016