October 2013 - Pharo-dev - lists.pharo.org

CI

by Camillo Bruni

Could someone else try rebooting all our jenkins instances including all slaves? - host name resolving is horribly slow on all slaves, the only thing that helps is rebooting - windows slaves are all down due to CI issue (being addressed by the CI maintainers) - I don't have access to the CI admin site, due to a Error 500

Oct. 30, 2013

Re: [Pharo-dev] moose 4.9

by Usman Bhatti

On Wed, Oct 30, 2013 at 12:23 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Yes. Right away. > > Could anyone please move the build job to run on Pharo 3.0? > That should be too difficult with zero-conf scripts for Pharo 3.0. I can do it. I'd like to keep the 4.9 job in the jenkins for a few days until downstream projects adapt themselves. So, I'll create a new job Moose 5.0 with Pharo 3.0 on the jenkins and we'll remove the current job in a few days. Is that ok with you? > > Doru > > > On Wed, Oct 30, 2013 at 11:29 AM, Andrei Chis <chisvasileandrei(a)gmail.com>wrote: > >> Super. >> So this means we finally more to Pharo 3? >> >> Andrei >> >> >> On Wed, Oct 30, 2013 at 10:38 AM, Tudor Girba <tudor(a)tudorgirba.com>wrote: >> >>> We are happy to announce version 4.9 of the Moose Suite: >>> http://moosetechnology.org/download/4.9 >>> >>> >>> This is a minor release still based on Pharo 2.0. The differences from >>> Moose 4.8 are: >>> >>> The Mondrian engine was removed. The transition to Roassal is now >>> complete. >>> - Small fixes in Roassal layouts and rendering. >>> - Small fix in FAMIX regarding manipulation of accesses. >>> - Small visual fix in Glamour for rendering splitters in tables. >>> >>> A list of issues addressed in this release can be found at: >>> http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… >>> >>> The Moose Suite 4.9 comes for each platform as a separate bundle: >>> - Moose Suite 4.9 for Mac >>> >>> https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-mac.zip >>> - Moose Suite 4.9 for Windows >>> >>> https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-win.zip >>> - Moose Suite 4.9 for Linux >>> >>> https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-linux.zip >>> >>> The Moose Suite 4.9 can also be loaded in a Pharo 2.0 image either from >>> the Configuration Browser, or by executing the following script: >>> >>> Gofer new >>> smalltalkhubUser: 'Moose' project: 'Moose'; >>> package: 'ConfigurationOfMoose'; >>> load. >>> ((Smalltalk at: #ConfigurationOfMoose) >>> project version: '4.9-snapshot') load >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Oct. 30, 2013

Re: [Pharo-dev] moose 4.9

by Tudor Girba

Yes. Right away. Could anyone please move the build job to run on Pharo 3.0? Doru On Wed, Oct 30, 2013 at 11:29 AM, Andrei Chis <chisvasileandrei(a)gmail.com>wrote: > Super. > So this means we finally more to Pharo 3? > > Andrei > > > On Wed, Oct 30, 2013 at 10:38 AM, Tudor Girba <tudor(a)tudorgirba.com>wrote: > >> We are happy to announce version 4.9 of the Moose Suite: >> http://moosetechnology.org/download/4.9 >> >> >> This is a minor release still based on Pharo 2.0. The differences from >> Moose 4.8 are: >> >> The Mondrian engine was removed. The transition to Roassal is now >> complete. >> - Small fixes in Roassal layouts and rendering. >> - Small fix in FAMIX regarding manipulation of accesses. >> - Small visual fix in Glamour for rendering splitters in tables. >> >> A list of issues addressed in this release can be found at: >> http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… >> >> The Moose Suite 4.9 comes for each platform as a separate bundle: >> - Moose Suite 4.9 for Mac >> https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-mac.zip >> - Moose Suite 4.9 for Windows >> https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-win.zip >> - Moose Suite 4.9 for Linux >> >> https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-linux.zip >> >> The Moose Suite 4.9 can also be loaded in a Pharo 2.0 image either from >> the Configuration Browser, or by executing the following script: >> >> Gofer new >> smalltalkhubUser: 'Moose' project: 'Moose'; >> package: 'ConfigurationOfMoose'; >> load. >> ((Smalltalk at: #ConfigurationOfMoose) >> project version: '4.9-snapshot') load >> > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 30, 2013

Re: [Pharo-dev] moose 4.9

by Andrei Chis

Super. So this means we finally more to Pharo 3? Andrei On Wed, Oct 30, 2013 at 10:38 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > We are happy to announce version 4.9 of the Moose Suite: > http://moosetechnology.org/download/4.9 > > > This is a minor release still based on Pharo 2.0. The differences from > Moose 4.8 are: > > The Mondrian engine was removed. The transition to Roassal is now complete. > - Small fixes in Roassal layouts and rendering. > - Small fix in FAMIX regarding manipulation of accesses. > - Small visual fix in Glamour for rendering splitters in tables. > > A list of issues addressed in this release can be found at: > http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… > > The Moose Suite 4.9 comes for each platform as a separate bundle: > - Moose Suite 4.9 for Mac > https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-mac.zip > - Moose Suite 4.9 for Windows > https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-win.zip > - Moose Suite 4.9 for Linux > > https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-linux.zip > > The Moose Suite 4.9 can also be loaded in a Pharo 2.0 image either from > the Configuration Browser, or by executing the following script: > > Gofer new > smalltalkhubUser: 'Moose' project: 'Moose'; > package: 'ConfigurationOfMoose'; > load. > ((Smalltalk at: #ConfigurationOfMoose) > project version: '4.9-snapshot') load >

Oct. 30, 2013

VirtualBox with host-only interface on Mavericks

by Max Leske

For all of you who use VirtualBox on OS X with host-only interfaces: VirtualBox on Mavericks will prevent the OS from shutting down if you have host-only interfaces configured (and will clutter your dock with VirtualBox iconsâ¦). You may use the attached bash script to fix the symptoms (thereâs no solution yet). You will need to edit the script to match the number of host-only interfaces you have configured. Cheers, Max

Oct. 30, 2013

moose 4.9

by Tudor Girba

We are happy to announce version 4.9 of the Moose Suite: http://moosetechnology.org/download/4.9 This is a minor release still based on Pharo 2.0. The differences from Moose 4.8 are: The Mondrian engine was removed. The transition to Roassal is now complete. - Small fixes in Roassal layouts and rendering. - Small fix in FAMIX regarding manipulation of accesses. - Small visual fix in Glamour for rendering splitters in tables. A list of issues addressed in this release can be found at: http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… The Moose Suite 4.9 comes for each platform as a separate bundle: - Moose Suite 4.9 for Mac https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-mac.zip - Moose Suite 4.9 for Windows https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-win.zip - Moose Suite 4.9 for Linux https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-linux.zip The Moose Suite 4.9 can also be loaded in a Pharo 2.0 image either from the Configuration Browser, or by executing the following script: Gofer new smalltalkhubUser: 'Moose' project: 'Moose'; package: 'ConfigurationOfMoose'; load. ((Smalltalk at: #ConfigurationOfMoose) project version: '4.9-snapshot') load

Oct. 30, 2013

Re: [Pharo-dev] Slides of my Lecture this morning..

by HernÃ¡n Morales Durand

I really liked it. Thank you Marcus. HernÃ¡n 2013/10/29 Marcus Denker <marcus.denker(a)inria.fr> > Hi, > > I am just visiting Jordi Delgado in Barcelona and I gave a lecture in his > course this morning. > âAdvanced Reflection in Pharoâ, this is meant to be a lecture after an > introduction to standard > Smalltalk reflection. > > SlideShare > http://www.slideshare.net/MarcusDenker/lecture-27685035 > > PDF > http://marcusdenker.de/talks/13BarcelonaLecture/ > > > Marcus >

Oct. 30, 2013

Re: [Pharo-dev] [Pharo-users] Pharo Sprint in Buenos Aires Nov 7th

by HernÃ¡n Morales Durand

What is the agenda? I would like to create UI visually. Any interest on this? HernÃ¡n 2013/10/29 Gisela Decuzzi <giseladecuzzi(a)gmail.com> > Hello, we are organizing a Pharo Sprint in Bs As: > > When: November 7th, starting at 10:00 am > Where: 10 Pines (Av Leandro N. Alem 693 5Â°B) > > >

Oct. 30, 2013

Re: [Pharo-dev] About BitBlt current -> BitBlt (Fuel)

by Max Leske

Bleeding edge only: Name: Fuel-MaxLeske.787 Author: MaxLeske Time: 29 October 2013, 11:41:05.948727 pm UUID: 2199a684-70e6-4dee-b3f1-ee389d959aed Ancestors: Fuel-MarianoMartinezPeck.775, Fuel-MaxLeske.786 merging tips from 3.0 development and fuel repo On 29.10.2013, at 19:56, Max Leske <maxleske(a)gmail.com> wrote: > Thanks Mariano, Iâll look at that. > > On 29.10.2013, at 15:39, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > >> Max, we use a primitive from BitBtl to perform writing of word-like instances (Bitmaps etc). It makes writing word objects way faster. >> Check the method #copyWordObjectToBuffer: aWordObject and its senders. >> >> Cheers, >> >> >> >> On Tue, Oct 29, 2013 at 6:55 AM, Max Leske <maxleske(a)gmail.com> wrote: >> Stef, what exactly is the influence on Fuel? I looked at the changes of your slice and couldnât find anythingâ¦ >> >> Max >> >> >> On 25.10.2013, at 16:26, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> > Hi >> > >> > I just pushed a change cleaning some strange usage. >> > BitBlt was sometimes invoked via BitBlt current (which just returned the BitBlt class). >> > Apparently in Squeak they removed it too. >> > >> > Now it touches Fuel so Fuel guys can you merge on your side too? >> > >> > https://pharo.fogbugz.com/f/cases/12009/BitBlt-current-BitBlt >> > >> > Stef >> >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >

Oct. 29, 2013

Re: [Pharo-dev] Tests with multiple processes

by Norbert Hartl

Chris, Am 29.10.2013 um 22:35 schrieb Chris Muller <asqueaker(a)gmail.com>: > Testing with real sockets, across multiple images is the only way I > would trust my own networking programs. OSProcess makes that an easy, > one-click affair. > Agreed. That is what we do in addition. Iâm doing tests for the logic behind the network. So this more about mocking the end-to-end communication in order to make a proper set of business logic tests. Norbert > On Mon, Oct 28, 2013 at 5:50 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> Iâm working on project that deals with server to server communication. For the test suite it is necessary to simulate the two ends of the communication within one test. The problem is that in a single threaded environment you make a send call SC from server A to B but the response of B will happen before SC returned. That makes every state change the happens in A after SC bogus from a call flow perspective. >> >> There are two approaches that have their own problems. >> >> 1) Until now Iâm reordering parts of the call stack to simulate the return of a call before the actual call is sent. But now I have nested sends that make my simple approach not working anymore. I could elaborate my approach by using something like delimited continuations to make a less brittle approach to stack call reordering in order to cope with the problem. That would need some work and the stack in the debugger will look a little bit odd/confusing. >> >> 2.) The product will later have a dispatcher process that dispatches each send operation in its own process. That would solve one problem: the timing of when actions happen. But Iâm not sure if it will be easy to orchestrate actions in a way that I would call controlled in order to have reliable tests. >> >> Are there any approaches to simulate coroutines in a single thread environment or approaches to deal with multiple processes within one process? >> >> It is hard to explain and I hope my description of the problem is understandable >> >> thanks in advance, >> >> Norbert >

Oct. 29, 2013