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

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

Re: [Pharo-dev] Couchbase client

by Chris Cunningham

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

Couchbase client

by Esteban A. Maringolo

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

Removing tools

by Pavel Krivanek

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 18, 2014

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

by Max Leske

On 18.03.2014, at 15:13, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > > > Le 17/03/2014 22:49, Max Leske a Ã©crit : >> >>> - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION >> >> - annoy Esteban some more with libgit2 >> - get other people to work on LibGit > > This is the project we should look at? > > http://smalltalkhub.com/#!/~StefanMarr/LibGit/commits Yes, thatâs the one. Itâs still pretty unstable so I donât recommend that you look at it yet. That should change in the next couple of days though (as might the location of the repository actuallyâ¦). Iâll keep you posted and will let you know once it makes sense for others to work on it. Max > >> - move the repository to the FileSystem-Git-Dev team >> - get fetch / pull working >> - try to get the LibGit build working with Moose > > 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 18, 2014

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

by Pharo4Stef

On 18 Mar 2014, at 17:02, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Hello, > > For blockClosures it is normal, block closure arguments have always been assignable since smalltalk-80. No this is wrong. > We could add a warning to discourage it, but we cannot forbid it, or we will not be able to load lots of frameworks and libraries that use it. No they should not > So 12419 is not a bug to me, it's a feature. No this is a bug. > > For methods it is a bug, thanks for noticing. I will check. > > > > > 2014-03-18 15:45 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de>: > similiar to issue 12419 block arguments should be read only > > > 2014-03-18 15:21 GMT+01:00 Camille Teruel <camille.teruel(a)gmail.com>: > > Indeed, I can compile: > > C>>foo: arg > ^ arg := 3 > > And 'C new foo: 1' returns 3... > > > On 18 mars 2014, at 15:16, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > extent: newExtent > > > > vertical > > ifTrue: [ newExtent := self defaultWidth @ newExtent y ] > > ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. > > > > super extent: newExtent > > > > Can you verify it? Arguments should be not assignable. > > > > -- > > Best regards, > > Igor Stasenko. > > > >

March 18, 2014