- Pharo-dev - lists.pharo.org

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

How to include Moose-Finder in build

by Max Leske

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

March 19, 2014

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

by Tudor Girba

+1 Doru On Mon, Mar 17, 2014 at 8:01 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > > > seaside(a)rmod.lille.inria.fr wrote: > >> Hi! We're sending this automatic email twice a month, to give the > community an opportunity to easily know what's happening and to coordinate > efforts. Just answer informally, and feel free to spawn discussions > thereafter! > >> > >> ### Here's what I've been up to since the last WhatsUp: > > * Had a dozen or so bug fixes integrated. Surprised myself by how far I > could dig into the system and it still made sense. I've learnt a lot about > corners of the system I'd normally never poke around in. Its been fun. > > And this is cool :) > > > > >> ### What's next, until 2014-03-31 (*): > >> > >> > > Squash more bugs. > > > > > -- www.tudorgirba.com "Every thing has its own flow"

March 19, 2014

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

by Tudor Girba

### Here's what I've been up to since the last WhatsUp: - Documented how the GTInspector integrates seamlessly how to handle the DB http://www.humane-assessment.com/blog/dynamic-exploration-of-a-postgres-db-… - A little blog post about measuring and visualizing nil checks (with the new CodeCity) http://www.humane-assessment.com/blog/analyzing-the-density-of-nil-checks/ - Worked on supporting class examples in GTInspector - Worked on an initial support for contextual presentations in GTInspector - Got accepted for a 60 minutes slot at NDC Oslo to give a presentation entitled: "Pharo: Playing with live objects" http://ndcoslo.oktaset.com/t-13914 ### What's next, until 2014-03-31 (*): - start to prepare a presentation for speakerconf.com about GToolkit - release GToolkit for Pharo 3 (MetaRepoForPharo30) -- www.tudorgirba.com "Every thing has its own flow"

March 19, 2014

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

by Tudor Girba

Cool! Doru On Mon, Mar 17, 2014 at 9:14 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Added Pier3 to MetaRepoForPharo30 > > Stephan > > -- www.tudorgirba.com "Every thing has its own flow"

March 19, 2014

Re: [Pharo-dev] Couchbase client

by Esteban A. Maringolo

I don't know the exact difference between the clients of Couchbase and CouchDB. I know Couchbase forked from CouchDB, and the REST API is the same. Hopefully the CouchDB client will work. Thank you! Esteban A. Maringolo 2014-03-18 20:01 GMT-03:00 Chris Cunningham <cunningham.cb(a)gmail.com>: > I've used this one in Pharo (at least, on Pharo 2.0): > http://www.squeaksource.com/SCouchDB.html > > -cbc > > > On Tue, Mar 18, 2014 at 3:48 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: >> >> Is there a Couchbase client for Pharo? >> >> If it there is one it isn't listed in the clients list >> (http://www.couchbase.com/communities/all-client-libraries) >> >> Regards! >> >> Esteban A. Maringolo >> >

March 18, 2014