- Pharo-dev - lists.pharo.org

[Pharo-project] Is there a backup place for

by Friedrich Dominicus

http://source.lukas-renggli.ch ? At least today it is not reachable from here. Regards Friedrich

June 30, 2012

Re: [Pharo-project] [Pharo-users] **IMPORTANT** MUST READ: Pharo Association and Consortium

by Marcus Denker

On Jun 28, 2012, at 2:19 PM, StÃ©phane Ducasse wrote: > > ===================== > *** Support and Answer needed*** > ===================== > > To be able to pay an engineer by the consortium, INRIA needs to make projection, build budget, pay attention to visa > and other important administrative tasks. To deal with the risk that the consortium may not collect enough to pay a full salary > we are considering to ask INRIA to help us financially. To do so we have to give some concrete figures to > INRIA and motivate our request. In addition, our team (RMOD) on its own budget will try to compensate by allocating extra resources > However, this will be only a one shot. In addition, some of our team members have been approached by google to work on chrome and dart > Virtual Machines. So if we really get a future we should build it now. > I will be a personal golden member (99EUR/year) And with Norbert and Christian, we decided that http://2denker.de (2Denker GmbH) will be a Silver Member of the consortium. Marcus -- Marcus Denker -- http://marcusdenker.de

June 30, 2012

Re: [Pharo-project] Funny example

by StÃ©phane Ducasse

> Indeed. DrGeo is not multithread safe. > > In this example, the animation is done in a background thread, at the > end of the smalltalk code this is the "canvas do: [] loop" code. > > So when playing interactively with the sketch, changing parameters for > example, your are forcing a sketch update, and at this exact same time > the animation tread may be in the re-rendering phase. So the artefact > you see is because the sampling of the locus is recalculated in one > thread and rendered (incomplete) in another thread. > > We are exploring here the Dr. Geo bounds... > I am not sure I want to investigate the case yet. don't :) Wait for a real use case Stef

June 30, 2012

Re: [Pharo-project] Funny example

by Hilaire Fernandes

Indeed. DrGeo is not multithread safe. In this example, the animation is done in a background thread, at the end of the smalltalk code this is the "canvas do: [] loop" code. So when playing interactively with the sketch, changing parameters for example, your are forcing a sketch update, and at this exact same time the animation tread may be in the re-rendering phase. So the artefact you see is because the sampling of the locus is recalculated in one thread and rendered (incomplete) in another thread. We are exploring here the Dr. Geo bounds... I am not sure I want to investigate the case yet. Hilaire On 29/06/2012 19:52, Nicolas Cellier wrote: > Nice. > Some edge case artifacts are visible though... > > Nicolas > > 2012/6/29 Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch>: >> Marin asks me if Dr. Geo can do it: >> http://www.ericforman.com/blog/anthony-mccall-solid-light/ >> >> No problem: >> http://www.dailymotion.com/video/xrupz0_1310-programmed-sketch-rulers_tech >> >> >> >> -- >> Dr. Geo -- http://www.drgeo.eu >> >> >> > > -- Dr. Geo -- http://www.drgeo.eu

June 30, 2012

Re: [Pharo-project] Funny example

by StÃ©phane Ducasse

really really nice. Stef On Jun 29, 2012, at 4:21 PM, Hilaire Fernandes wrote: > Marin asks me if Dr. Geo can do it: > http://www.ericforman.com/blog/anthony-mccall-solid-light/ > > No problem: > http://www.dailymotion.com/video/xrupz0_1310-programmed-sketch-rulers_tech > > > > -- > Dr. Geo -- http://www.drgeo.eu > > >

June 30, 2012

Re: [Pharo-project] [Moose-dev] Magritte / XML bridge

by StÃ©phane Ducasse

Norbert when I load magicMagritte and I tried the example I got an error because I got an object instead of text visitMultipleOptionDescription: aDescription | options text | options := self object readUsing: aDescription. options notNil ifTrue: [ options do: [ :each | self writeText: each asString description: aDescription ] ] ^^^^^^^^^^^^ I added that but this is probably wrong. I will take some time to look deeper into. Stef On Jun 29, 2012, at 10:54 AM, Norbert Hartl wrote: > > Am 28.06.2012 um 21:15 schrieb StÃ©phane Ducasse: > >> Hi guys >> >> I would like to show in the magritte chapter I'm revisiting a bit more meat. >> I'm playing with magritte 30 and I would like to know if there is a way to save objects based on their magritte description. >> > Yes, there is. There is a description in an old blog post of mine [1]. Don't be misled that magritte2 is mentioned there. It works as well with magritte3 (thanks to Nick Ager). You can get it > > Gofer new > renggli: 'magritte3addons'; > package: 'ConfigurationOfMagritte3AddOns'; > load > > and load the default. > > In a nutshell: > > You add to your descriptions "beXmlAttribute" or "beXmlElement". Then you can store an object with > > myObject magritteDescription toXml: myObject > > hope that helps, > > Norbert > > > [1] http://norbert.hartl.name/blog/magritte-xmlbinding/ > > > >

June 30, 2012

[Pharo-project] SqueakSource Down

by Davide Varvello

see subject -- View this message in context: http://forum.world.st/SqueakSource-Down-tp4637436.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 30, 2012

Re: [Pharo-project] Our new primate friend

by StÃ©phane Ducasse

> On Fri, Jun 29, 2012 at 4:48 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> Ulysse the Monkey is even faster than Marcus ;-) My issue went from >> FixReviewNeeded to FixToInclude in < 1 minute! Pretty cool... > so... who did the review? Indeed we should have a tag that says validatedByUlyss then somebody should still have a look at the fixes. Stef > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry >

June 30, 2012

Re: [Pharo-project] pharo monkey issue updater

by Sean P. DeNigris

EstebanLM wrote > > 'ls -la>z' system. "non piped" > That's clean enough, and very easy to implement... ByteString>>system | process | process := PipeableOSProcess waitForCommand: self. ^ process output. Of course, with the current implementation of OSProcess, it's very easy to hang the image that way, so we might want to #setNonBlockingOutput, or do our own polling... -- View this message in context: http://forum.world.st/pharo-monkey-issue-updater-tp4637322p4637418.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 29, 2012

Re: [Pharo-project] pharo monkey issue updater

by Sean P. DeNigris

Camillo Bruni-3 wrote > > ever felt bored of waiting for your issue to be checked, > try now our new monkey checker script: > > https://gitorious.org/pharo-build/pharo-build/blobs/master/pharo-shell-scri… > I was confused by this announcement and the script itself. I thought it could be parameterized to be used on any image (e.g. locally on my machine), esp. since /.image (wasn't sure exactly what the $/ meant) is the first thing in the usage instructions. When I tried it, I found hard-coded values. So... * cool monkey * I don't know what we're supposed to do with the script, unless it's to show off that we've evolved from Bash to Ruby, which is cool :) -- View this message in context: http://forum.world.st/pharo-monkey-issue-updater-tp4637322p4637413.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 29, 2012