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

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

by Goubier Thierry

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

March 19, 2014

Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31

by Tudor Girba

On Wed, Mar 19, 2014 at 8:35 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > ### Here's what I've been up to since the last WhatsUp: > > - reported a couple bugs for Pharo 3.0 > - got one commercial deal signed with Pharo as the underlying technology > Great! We are looking forward for a new success story. > - learning Roassal > :) Doru ### What's next, until 2014-03-31 (*): > > - another deal coming - proposal in the intertubes > > Phil > > -- www.tudorgirba.com "Every thing has its own flow"

March 19, 2014

Re: [Pharo-dev] Removing tools

by Pavel Krivanek

Hi Torsten, we plan to do that in Pharo/SystemConfigurations(/Unreloader). That mail was something like a late night backup of very experimental stuff :-) Cheers, -- Pavel 2014-03-19 9:08 GMT+01:00 Torsten Bergmann <astares(a)gmx.de>: > Hi Pavel, > > dont know if this is a good idea but why not: > - put this into a ConfigurationOfNoTools with a > spec postLoadDoIt: #postloadToShrinkWithLoader:package:. > - put the script into a #postloadToShrinkWithLoader:package > - store the project on STHub > - create a CI job for loading the Config > > This way one can: > - browse the changes to the script in Monticello as it progresses > - have the CI built the image automagically > - the final image can be downloaded from CI or using Pharo launcher easily > > If some simply unit tests will be applied (like checking for Undeclared, > etc) one can control > if the image will get/be/stay red or green. > > Bye > T. > > > *Gesendet:* Dienstag, 18. MÃ¤rz 2014 um 23:00 Uhr > *Von:* "Pavel Krivanek" <pavel.krivanek(a)gmail.com> > *An:* "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> > *Betreff:* [Pharo-dev] Removing tools > Hi, > > this is an initial attempt to produce an image without development tools. > Currently it leaves Workspace and Transcript in the image, has no obsolete > classes and six Undeclared. The image size is still quite big, 16.1 MB. > Tested on #30798. Do not forget to share your improvements ;-) > > Cheers, > -- Pavel >

March 19, 2014

Re: [Pharo-dev] Removing tools

by Torsten Bergmann

March 19, 2014

SmalltalkHub troubles

by Philippe Marschall

Hi I'm having trouble committing to SmalltalkHub and I don't know where to go for support. When trying to commit to Seaside31 I get the following error: HTTP/1.1 403 Forbidden Date: Tue, 18 Mar 2014 20:16:45 GMT Content-Length: 512 Vary: Accept-Encoding Server: Zinc HTTP Components 1.0 Connection: close Content-Type: text/plain Unknown token type I double checked and my username and password are correct. Cheers Philippe

March 19, 2014

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

by Tudor Girba

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 Yuriy Tymchuk

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

FileSystem-Git status update 2

by Max Leske

- 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

#checkSourcesFileAvailability: gone?

by Hilaire Fernandes

Hello, In 3.0, I don't see it anymore. Found nothing in the forum either. Thanks Hilaire -- Dr. Geo http://drgeo.eu

March 19, 2014

Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31

by phil＠highoctane.be

### Here's what I've been up to since the last WhatsUp: - reported a couple bugs for Pharo 3.0 - got one commercial deal signed with Pharo as the underlying technology - learning Roassal ### What's next, until 2014-03-31 (*): - another deal coming - proposal in the intertubes Phil

March 19, 2014