- Pharo-users - lists.pharo.org

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

Re: [Pharo-users] BaselineOf's and Loose Dependencies

by Dale Henrichs

On 3/21/16 9:48 AM, Sean P. DeNigris wrote: > Dale Henrichs-3 wrote >> First, congratulations! > Thanks!! > > > Dale Henrichs-3 wrote >> A baseline is associated with a "git version", so there is no need to >> "pin the version down in a specific version" > Yes, but I'm not talking about a version of my main project, but a version > of a dependent project. Right ... but you were also talking about "pinning the version of a dependent project in a version of your main project" .... each git commit is a new version of your main project, the equivalent of a new numbered version in a configuration, so to "pin the version of a dependent project", you simply change the version of the dependent project ... which I did in the example I provided ... > > > Dale Henrichs-3 wrote >> in a "git project" you >> have the option of changing the specific version associated with a >> baseline on "every commit" .... > Again, yes, but what I want to do (and what I understood as best practice in > the past) is to defer the linking to a specific version until I release a > stable version of my main project. Okay ... in a git environment, the master branch of your project is the stable version and you do development on a separate "topic branch" like `dev` or `issue_88`. > That is, while I'm developing, I can be > much looser with my tracking of loose dependencies, e.g. commonly it is > enough to specify that I always want #stable. Of course, symbolic > dependencies are not a good idea for release versions, so I will want to > override the loose dependency with a specific numbered version. As I've said elsewhere I think that a symbolic version scheme based on versions (#release3, #release3.1, #release3.1.2, etc.) is superior to #stable for Monticello-based projects (those using ConfigurationOf) and it your dependent project used this scheme, there would be no need to "override the loose dependency with a specific numbered version". If the dependent project doesn't use this scheme then you are stuck with using "specific numbered versions" ... That means that on branch `dev` you'll change the version of the project to #stable and do your work, when you are preparing to merge your work on `dev` into the master branch, you will choose a "specific numbered version", replace #stable with the the numbered version, test, merge to `master` branch. The next time you start work on a new topic branch, you can choose to use #stable, or simply select the latest numbered version explicitly and develop away ... before merging to master in this scheme, just double check if there is new version availble and if not, you're good to go ... > Unfortunately, while I'm no longer getting the mentioned error, my override > seems to be ignored - `ConfigurationOfBabyPhexample project stableVersion > record loadDirective.` reports that the #stable version of BabyMock (1.3) > will be loaded instead of the version 1.2 that I specified in my > configuration. Did you use the example I provided or did you continue to try to use the original spec? The spec you provided didn't make sense to me (I figured it was copy paste errors)... > > I created an issue in my GitHub project where it might be easier to > reference the code (https://github.com/seandenigris/Baby-Phexample/issues/1) > or we can continue to discuss here. Yeah, it will be much easier to get into specific details on github ... Dale >

March 22, 2016

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

by Ben Coman

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 22, 2016

Re: [Pharo-users] Pharo launcher in homebrew cask

by Damien Pollet

FYI I was also thinking of creating a homebrew tap for pharo (VM etc). Still at the draft stage, unfortunately. On 22 March 2016 at 13:00, Damien Cassou <damien.cassou(a)inria.fr> wrote: > Filip Krikava <krikava(a)gmail.com> writes: > > > 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 > > I don't know homebrew-cask but I imagine that it is better to reference > stable files on the web rather than continuously changing files. At > least, that's true for the package manager I package(d) for. If that's > also the case here, I would recommend to use a file from: > > http://files.pharo.org/platform/launcher/blessed/ > > Files there don't change. If you are interested, I can move OS X releases > there the same way I do it for Linux releases. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > >

March 22, 2016

Re: [Pharo-users] Pharo launcher in homebrew cask

by Damien Cassou

Filip Krikava <krikava(a)gmail.com> writes: > 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 I don't know homebrew-cask but I imagine that it is better to reference stable files on the web rather than continuously changing files. At least, that's true for the package manager I package(d) for. If that's also the case here, I would recommend to use a file from: http://files.pharo.org/platform/launcher/blessed/ Files there don't change. If you are interested, I can move OS X releases there the same way I do it for Linux releases. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

March 22, 2016

Re: [Pharo-users] What frameworks/libraries are available for creating programming languages with Pharo

by Dimitris Chloupis

yes exactly, something that takes advantage of the existing pharo AST so I dont have to reinvent IDE tools etc. Because in that case I may as well do this without Pharo because then it defeats the purpose of taking advantage of all this cool Pharo functionality and would be a ton extra effort. The way I see it , because Pharo syntax is so minimal should be relative easy to implement a language on top that its syntax is nothing more than Pharo objects. Looks different but underneath its plain old Smalltalk. This is why I mentioned Lisp. On Tue, Mar 22, 2016 at 11:11 AM ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > I think in addition of the parser/compilation chain, a language is about > having a good IDE. > > The Pharo IDE depends more and more on the AST and not on the source code, > so if your new language uses an AST polymorphic with the Smalltalk AST I > guess you can have IDE tools for free (at least partly). > > At least you can consider frameworks to build code browser such as Glamour > as an available library to create a programming language. > > In addition, Omnibrower, which is the default code browser in Pharo 1.4, > can browse the code of any language. You provide Omnibrowser a language > model and it browses your code based on your model. > > > > 2016-03-22 9:48 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > >> 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 ? >> > >

March 22, 2016