March 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] How to include Moose-Finder in build

by Max Leske

On 19.03.2014, at 11:16, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Something is wrong with your setup or with some collision caused by something else you are loading. The image should be in the range of 40-50 MB. Youâre right. Although I donât know why, running all of that in a fresh image works fine. Sorry about that! Cool! I now have Moose tools :) > > Could you give me the exact script you are using? > > Cheers, > Doru > > > > > On Wed, Mar 19, 2014 at 11:10 AM, Max Leske <maxleske(a)gmail.com> wrote: > Thanks Doru. > > Looks much better now. Unfortunately my image is now unusable because thereâs no memory left (even after saving and restarting it. The image with tools loaded is 450MB). > I retried without the installation code, simply loading GToolkit. The result is always that I have about 8MB of memory left in the image. > > I have to focus my energy on Git at the moment so Iâm not going to invest time to find out whatâs wrong. I still want to use GToolkit, so if you (or anybody else) can help out, that would be great. > > Cheers, > Max > > > > On 19.03.2014, at 08:54, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi Max, >> >> I am happy you want to give these tools a try :). >> >> The tools do not install themselves automatically because I think it is not a good practice to tie code loading with installation. To setup the Moose image, we actually have a command line handler that allows you to simply trigger this from the CI job: >> >> ./pharo $JOB_NAME.image mooseimagesetup --signature=$BUILD_URL >> >> You can also trigger from the image: >> MooseImageSetupCommandLineHandler activateWith: (CommandLineArguments withArguments: {}) >> >> This installs the theme, the fonts, preferences and the GToolkit playground, inspector and debugger. >> >> However, for developing in Pharo, you do not need all of Moose, and almost certainly do not need the Moose Finder. You likely only need the GToolkit. >> >> spec project: 'GToolkit' with: [ >> spec >> className: 'ConfigurationOfGToolkit'; >> version: #development; >> file: 'ConfigurationOfGToolkit'; >> repository: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main' ]. >> >> To install the tools, you have to install them manually at the moment - but I will create a command line handler for that soon: >> GTPlayground registerToolsOn: Smalltalk tools. >> GTInspector registerToolsOn: Smalltalk tools. >> GTGenericStackDebugger registerToolsOn: Smalltalk tools. >> GTGenericStackDebugger registerExtraToolsOn: Smalltalk tools. >> "GTPPDebugger registerToolsOn: Smalltalk tools." "only if you need it for PetitParser" >> GTGlamourDebugger registerToolsOn: Smalltalk tools. >> ACGlamourDebugger registerToolsOn: Smalltalk tools. >> GTSUnitDebugger registerToolsOn: Smalltalk tools. >> GTMoldableDebugger enableDebuggerWindowDistinctColor: true >> >> To install the white theme: >> GLMWhitespaceTheme >> defaultSettings: nil; >> setPreferredWorldBackground; >> beCurrent >> >> To install the fonts, you can just do this: >> #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBold') do: [ :each | >> Smalltalk globals >> at: each asSymbol >> ifAbsent: [ >> Gofer new >> smalltalkhubUser: 'girba' project: 'FreeFonts'; >> package: each; >> load ]. >> (Smalltalk at: each asSymbol) new install ]. >> FreeTypeSystemSettings loadFt2Library: true. >> FreeTypeFontProvider current updateFromSystem >> >> Let me know how it goes. >> >> Cheers, >> Doru >> >> >> >> >> On Wed, Mar 19, 2014 at 8:24 AM, Max Leske <maxleske(a)gmail.com> wrote: >> Hi >> >> I want to use the Moose UI tools for development and since I have a CI job for the project I thought I could just load Moose and be done with it. That doesnât seem to work however. >> >> I tried loading #development but when I do that I get the FallbackMenu instead of the world menu and no new inspectors / browsers. Here are the conditions of my build: >> - I want to start my build from a fresh Pharo3 image >> - I only want the Moose UI tools (I donât need any of the parsers etc.) >> - it would be nice if, when I open a built image, the default tools are already set to the Moose ones >> >> I know that there is a development Moose build for Pharo3, so Iâm a bit surprised that I canât just load the configurationâ¦ >> >> BTW: this is how I tried to load Moose (maybe I just screwed up the configuration): >> >> baseline02: spec >> <version: '0.2-baseline'> >> >> spec for: #common do: [ >> spec blessing: #baseline. >> >> spec package: 'LibGit2Bindings' with: [ >> spec repository: 'http://smalltalkhub.com/mc/MaxLeske/LibGit2Bindings/main' ]. >> >> spec project: 'Moose' with: [ >> spec >> className: 'ConfigurationOfMoose'; >> file: 'ConfigurationOfMoose'; >> version: #development; >> loads: #(Core UI); >> repository: 'http://smalltalkhub.com/mc/Moose/Moose/main' ]. >> >> spec package: 'Phexample' with: [ >> spec repository: 'http://smalltalkhub.com/mc/Phexample/Phexample/main' ]. >> >> spec repository: 'http://smalltalkhub.com/mc/StefanMarr/LibGit/main'. >> spec package: 'LibGit-Core' with: [ >> spec >> requires: #(Phexample LibGit2Bindings Moose); >> postLoadDoIt: #postLoadRecompile ] >> ]. >> >> Iâd appreciate any help (and if nobody helps me Doru will probably kick my ass for still not using Moose :p) >> >> Cheers, >> Max >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

March 19, 2014

Re: [Pharo-dev] How to include Moose-Finder in build

by Tudor Girba

Hi, Something is wrong with your setup or with some collision caused by something else you are loading. The image should be in the range of 40-50 MB. Could you give me the exact script you are using? Cheers, Doru On Wed, Mar 19, 2014 at 11:10 AM, Max Leske <maxleske(a)gmail.com> wrote: > Thanks Doru. > > Looks much better now. Unfortunately my image is now unusable because > there's no memory left (even after saving and restarting it. The image with > tools loaded is 450MB). > I retried without the installation code, simply loading GToolkit. The > result is always that I have about 8MB of memory left in the image. > > I have to focus my energy on Git at the moment so I'm not going to invest > time to find out what's wrong. I still want to use GToolkit, so if you (or > anybody else) can help out, that would be great. > > Cheers, > Max > > > > On 19.03.2014, at 08:54, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi Max, > > I am happy you want to give these tools a try :). > > The tools do not install themselves automatically because I think it is > not a good practice to tie code loading with installation. To setup the > Moose image, we actually have a command line handler that allows you to > simply trigger this from the CI job: > > ./pharo $JOB_NAME.image mooseimagesetup --signature=$BUILD_URL > > You can also trigger from the image: > MooseImageSetupCommandLineHandler activateWith: (CommandLineArguments > withArguments: {}) > > This installs the theme, the fonts, preferences and the GToolkit > playground, inspector and debugger. > > However, for developing in Pharo, you do not need all of Moose, and almost > certainly do not need the Moose Finder. You likely only need the GToolkit. > > spec project: 'GToolkit' with: [ > spec > className: 'ConfigurationOfGToolkit'; > version: #development; > file: 'ConfigurationOfGToolkit'; > repository: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main' ]. > > To install the tools, you have to install them manually at the moment - > but I will create a command line handler for that soon: > GTPlayground registerToolsOn: Smalltalk tools. > GTInspector registerToolsOn: Smalltalk tools. > GTGenericStackDebugger registerToolsOn: Smalltalk tools. > GTGenericStackDebugger registerExtraToolsOn: Smalltalk tools. > "GTPPDebugger registerToolsOn: Smalltalk tools." "only if you need it for > PetitParser" > GTGlamourDebugger registerToolsOn: Smalltalk tools. > ACGlamourDebugger registerToolsOn: Smalltalk tools. > GTSUnitDebugger registerToolsOn: Smalltalk tools. > GTMoldableDebugger enableDebuggerWindowDistinctColor: true > > To install the white theme: > GLMWhitespaceTheme defaultSettings: nil; setPreferredWorldBackground; > beCurrent > > To install the fonts, you can just do this: > #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' > 'SourceSansProBold') do: [ :each | > Smalltalk globals > at: each asSymbol > ifAbsent: [ > Gofer new > smalltalkhubUser: 'girba' project: 'FreeFonts'; > package: each; > load ]. > (Smalltalk at: each asSymbol) new install ]. > FreeTypeSystemSettings loadFt2Library: true. > FreeTypeFontProvider current updateFromSystem > > Let me know how it goes. > > Cheers, > Doru > > > > > On Wed, Mar 19, 2014 at 8:24 AM, Max Leske <maxleske(a)gmail.com> wrote: > >> Hi >> >> I want to use the Moose UI tools for development and since I have a CI >> job for the project I thought I could just load Moose and be done with it. >> That doesn't seem to work however. >> >> I tried loading #development but when I do that I get the FallbackMenu >> instead of the world menu and no new inspectors / browsers. Here are the >> conditions of my build: >> - I want to start my build from a fresh Pharo3 image >> - I only want the Moose UI tools (I don't need any of the parsers etc.) >> - it would be nice if, when I open a built image, the default tools are >> already set to the Moose ones >> >> I know that there is a development Moose build for Pharo3, so I'm a bit >> surprised that I can't just load the configuration... >> >> BTW: this is how I tried to load Moose (maybe I just screwed up the >> configuration): >> >> baseline02: spec >> <version: '0.2-baseline'> >> >> spec for: #common do: [ >> spec blessing: #baseline. >> >> spec package: 'LibGit2Bindings' with: [ >> spec repository: ' >> http://smalltalkhub.com/mc/MaxLeske/LibGit2Bindings/main' ]. >> >> spec project: 'Moose' with: [ >> spec >> className: 'ConfigurationOfMoose'; >> file: 'ConfigurationOfMoose'; >> version: #development; >> loads: #(Core UI); >> repository: ' >> http://smalltalkhub.com/mc/Moose/Moose/main' ]. >> >> spec package: 'Phexample' with: [ >> spec repository: ' >> http://smalltalkhub.com/mc/Phexample/Phexample/main' ]. >> >> spec repository: ' >> http://smalltalkhub.com/mc/StefanMarr/LibGit/main'. >> spec package: 'LibGit-Core' with: [ >> spec >> requires: #(Phexample LibGit2Bindings >> Moose); >> postLoadDoIt: #postLoadRecompile ] >> ]. >> >> I'd appreciate any help (and if nobody helps me Doru will probably kick >> my ass for still not using Moose :p) >> >> Cheers, >> Max >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

March 19, 2014

Re: [Pharo-dev] How to include Moose-Finder in build

by Max Leske

Thanks Doru. Looks much better now. Unfortunately my image is now unusable because thereâs no memory left (even after saving and restarting it. The image with tools loaded is 450MB). I retried without the installation code, simply loading GToolkit. The result is always that I have about 8MB of memory left in the image. I have to focus my energy on Git at the moment so Iâm not going to invest time to find out whatâs wrong. I still want to use GToolkit, so if you (or anybody else) can help out, that would be great. Cheers, Max On 19.03.2014, at 08:54, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Max, > > I am happy you want to give these tools a try :). > > The tools do not install themselves automatically because I think it is not a good practice to tie code loading with installation. To setup the Moose image, we actually have a command line handler that allows you to simply trigger this from the CI job: > > ./pharo $JOB_NAME.image mooseimagesetup --signature=$BUILD_URL > > You can also trigger from the image: > MooseImageSetupCommandLineHandler activateWith: (CommandLineArguments withArguments: {}) > > This installs the theme, the fonts, preferences and the GToolkit playground, inspector and debugger. > > However, for developing in Pharo, you do not need all of Moose, and almost certainly do not need the Moose Finder. You likely only need the GToolkit. > > spec project: 'GToolkit' with: [ > spec > className: 'ConfigurationOfGToolkit'; > version: #development; > file: 'ConfigurationOfGToolkit'; > repository: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main' ]. > > To install the tools, you have to install them manually at the moment - but I will create a command line handler for that soon: > GTPlayground registerToolsOn: Smalltalk tools. > GTInspector registerToolsOn: Smalltalk tools. > GTGenericStackDebugger registerToolsOn: Smalltalk tools. > GTGenericStackDebugger registerExtraToolsOn: Smalltalk tools. > "GTPPDebugger registerToolsOn: Smalltalk tools." "only if you need it for PetitParser" > GTGlamourDebugger registerToolsOn: Smalltalk tools. > ACGlamourDebugger registerToolsOn: Smalltalk tools. > GTSUnitDebugger registerToolsOn: Smalltalk tools. > GTMoldableDebugger enableDebuggerWindowDistinctColor: true > > To install the white theme: > GLMWhitespaceTheme > defaultSettings: nil; > setPreferredWorldBackground; > beCurrent > > To install the fonts, you can just do this: > #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBold') do: [ :each | > Smalltalk globals > at: each asSymbol > ifAbsent: [ > Gofer new > smalltalkhubUser: 'girba' project: 'FreeFonts'; > package: each; > load ]. > (Smalltalk at: each asSymbol) new install ]. > FreeTypeSystemSettings loadFt2Library: true. > FreeTypeFontProvider current updateFromSystem > > Let me know how it goes. > > Cheers, > Doru > > > > > On Wed, Mar 19, 2014 at 8:24 AM, Max Leske <maxleske(a)gmail.com> wrote: > Hi > > I want to use the Moose UI tools for development and since I have a CI job for the project I thought I could just load Moose and be done with it. That doesnât seem to work however. > > I tried loading #development but when I do that I get the FallbackMenu instead of the world menu and no new inspectors / browsers. Here are the conditions of my build: > - I want to start my build from a fresh Pharo3 image > - I only want the Moose UI tools (I donât need any of the parsers etc.) > - it would be nice if, when I open a built image, the default tools are already set to the Moose ones > > I know that there is a development Moose build for Pharo3, so Iâm a bit surprised that I canât just load the configurationâ¦ > > BTW: this is how I tried to load Moose (maybe I just screwed up the configuration): > > baseline02: spec > <version: '0.2-baseline'> > > spec for: #common do: [ > spec blessing: #baseline. > > spec package: 'LibGit2Bindings' with: [ > spec repository: 'http://smalltalkhub.com/mc/MaxLeske/LibGit2Bindings/main' ]. > > spec project: 'Moose' with: [ > spec > className: 'ConfigurationOfMoose'; > file: 'ConfigurationOfMoose'; > version: #development; > loads: #(Core UI); > repository: 'http://smalltalkhub.com/mc/Moose/Moose/main' ]. > > spec package: 'Phexample' with: [ > spec repository: 'http://smalltalkhub.com/mc/Phexample/Phexample/main' ]. > > spec repository: 'http://smalltalkhub.com/mc/StefanMarr/LibGit/main'. > spec package: 'LibGit-Core' with: [ > spec > requires: #(Phexample LibGit2Bindings Moose); > postLoadDoIt: #postLoadRecompile ] > ]. > > Iâd appreciate any help (and if nobody helps me Doru will probably kick my ass for still not using Moose :p) > > Cheers, > Max > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

March 19, 2014

Re: [Pharo-dev] FileSystem-Git status update 2

by Tudor Girba

+1.. Keep going :) Doru On Wed, Mar 19, 2014 at 9:43 AM, Goubier Thierry <thierry.goubier(a)cea.fr>wrote: > > > Le 19/03/2014 08:46, Max Leske a Ã©crit : > > - I moved all the code to the FileSystemGitDev team on Smalltalkhub >> - we now have a working LibGit2 build (tests fail but that will be fixed >> in the coming days) >> - we got simple fetch working yesterday (yay!) >> - we (which means Stefan) started rewriting our tests with SUnit, moving >> away from Phexample (for several reasons) >> >> Today's program: >> - migrate more tests >> - fix initialization and setup issues >> - try to perform a complete fetch + merge (without conflicts) >> - implement clone >> - try to get push working >> >> Have a great day! >> > > With such news, it is a great day :) > > Thanks for the effort, > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > -- www.tudorgirba.com "Every thing has its own flow"

March 19, 2014

Re: [Pharo-dev] Pharo as a NT service

by Torsten Bergmann

The Squeak VM had such a feature and it was/is widely used. For instance with Squeak it was/is easily able to install a Swiki as an NT Service and just run. There is a command line option -service: "serviceName" as you can see here: http://wiki.squeak.org/squeak/105 Pharo VM should have this too - I guess from Phillips post the code is still there. It registers the VM on the SCM (Service control manager) of Windows. Easily service registration would be really useful if provided out of the box especially for people who want to write web applications and deploy to Windows servers as one can run headless, control the service easily from the services panel or manage even clusters. Maybe it is broken, maybe related to the also broken headless support in Windows, also the stdio support of Pharo was never really finished (therefore we have a file stdout on Windows which is far from optimal) <rant> Even if it is not the best operating system: in IT reality Windows is still widely used as business platform. Currently Pharo does not really honor this these days - but should to get more business opportunities if it will (hopefully) provide better Window support in the future. </rant> Bye T. > Gesendet: Montag, 17. MÃ¤rz 2014 um 19:12 Uhr > Von: "Esteban A. Maringolo" <emaringolo(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] Pharo as a NT service > > To implement a 100% native service the executable must support certain > "functions". Which I don't think Pharo VM does. > > However you could use srvany.exe to run any executable file as a > service (http://support.microsoft.com/kb/137890) > > Regards! > Esteban A. Maringolo > > > 2014-03-17 14:58 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: > > I need to be able to run a Pharo VM+image as a service. > > > > I saw that in the Windows VM there are such flags. > > > > But I do not know how to make that work (or if it still works). > > > > Anyone knowing? > > > > Phil > >

March 19, 2014

Re: [Pharo-dev] Image's size in pillar

by Natalia Tymchuk

Thank you. Best regards On Mar 17, 2014, at 9:08 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Hi Natalia, > > On Sun, Mar 16, 2014 at 2:23 PM, Natalia Tymchuk > <natalia.tymchuk(a)unikernel.net> wrote: >> but with changing the value width I didn't get changes of my images sizes. How can I make my images take half of the page's width? > > I fixed this a month ago in the development version of Pillar but > didn't release a stable version yet. > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

March 19, 2014

Pharo3 release delayed!

by Esteban Lorenzano

Ladies and gentlemen, For achieving a great 3.0 release we still have some tasks that we still need to prepare. They are not many, but we (Pharo Board) think it deserves some more effort: 1) Technically, there are still some minor bugs to tackle around RPackage and Nautilus. We do not miss much and that could be done in a couple of days work (in fact, I'm working on them and trying to have it before going to Argentina next week), but in order to be sure, we better wait a bit :). It would be great to see more eyeballs focused on these issues. 2) We want to create a real marketing strategy this time, and that requires preparation time. "Marketing strategy" sounds probably really bombastic, but in our case it means to create pages, send mails, construct the progress log, etc. We we need some time to prepare it properly. So... Pharo3 release date has been moved to April 22. Cheers, Esteban

March 19, 2014

Re: [Pharo-dev] Just found, i can compile this:

by Christophe Demarey

Le 18 mars 2014 Ã 19:50, Eliot Miranda a Ã©crit : > On Tue, Mar 18, 2014 at 10:10 AM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > Why arguments should be read only? > They are just temporary variables with an initial value. > > Read the blue book. It was a decision of the language designers to forbid assignment to arguments to allow debugging. The assignment to block arguments is a side-effect of the old BlockContext implementation of blocks where block arguments were mapped onto temporary variables of the home context. It is an anachronism and should be forbidden also. Thank you for the explanation. I'm just curious why it is so difficult to implement a debugger if arguments are assignable? If you need to restart the execution of a method, and so you need to get the initial value of the argument, I understand you cannot find the value anymore in the method context but it is available in the caller context, no? As I never implemented a debugger, I cannot figure out the difficulties.

March 19, 2014

Re: [Pharo-dev] SmalltalkHub troubles

by Nicolas Petton

Hi Philippe, Can you send me the mcz privately so I can take a look? Cheers, Nico -- Nicolas Petton http://nicolas-petton.fr

March 19, 2014

Re: [Pharo-dev] FileSystem-Git status update 2

by Pharo4Stef

+1 On 19 Mar 2014, at 08:53, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Good to see this progress! Thanks for your effort. > > Uko > > On 19 Mar 2014, at 08:46, Max Leske <maxleske(a)gmail.com> wrote: > >> - I moved all the code to the FileSystemGitDev team on Smalltalkhub >> - we now have a working LibGit2 build (tests fail but that will be fixed in the coming days) >> - we got simple fetch working yesterday (yay!) >> - we (which means Stefan) started rewriting our tests with SUnit, moving away from Phexample (for several reasons) >> >> Todayâs program: >> - migrate more tests >> - fix initialization and setup issues >> - try to perform a complete fetch + merge (without conflicts) >> - implement clone >> - try to get push working >> >> Have a great day! >> >> Cheers, >> Max > >

March 19, 2014