June 2012 - Pharo-dev - lists.pharo.org

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

by StÃ©phane Ducasse

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. Excellent I will read it. I'm reading magicMagritte right now. BTW the Twitters stuff of nick is gorgeous :) > > In a nutshell: > > You add to your descriptions "beXmlAttribute" or "beXmlElement". Then you can store an object with > > myObject magritteDescription toXml: myObject Ok cool. I did that by hand in the past importElement: aXMLItem | anElement | anElement := (self class mappingTable at: aXMLItem name) new. self updateBackLinkOf: anElement. anElement magritteDescription do: [ :each | | auth | auth := aXMLItem attributeAt: each accessor readSelector asString. (#(nil 'nil' ) includes: auth) ifFalse: [ auth := each fromString: auth. each accessor write: auth to: anElement ]]. self base add: anElement. ^ anElement > > hope that helps, Do you know how relationships are handled :) > > Norbert > > > [1] http://norbert.hartl.name/blog/magritte-xmlbinding/ > > > >

June 29, 2012

Re: [Pharo-project] Let's Get Pharo 1.4 Ready for the Summer Release!

by Sean P. DeNigris

Sean P. DeNigris wrote > > Who will review one of those left, so we have a rock-solid *release this > week*?! Reviewing is simple ( > http://forum.world.st/Backporting-fixes-tp4633625p4633680.html per Steph > ): > - we go to the issue list > - try to load the code > - read the code > - check if there is a test > - check that all the tests are working (or that new ones are not > broken > So any input is important. > Sean P. DeNigris wrote > > Only two 1.4 bugs left to review. Act fast before they all disappear and > you get left out! > > http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.4+is%3Aope… > 4 more bug fixes integrated (thanks Marcus)!!! Which will be next?? -- View this message in context: http://forum.world.st/Let-s-Get-Pharo-1-4-Ready-for-the-Summer-Release-tp46… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 29, 2012

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

by Norbert Hartl

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 29, 2012

[Pharo-project] [update 2.0] #20172

by Marcus Denker

20172 ----- Issue 6205: File services should be part of the FileService package http://code.google.com/p/pharo/issues/detail?id=6205 - remove empty Multilingual-ImmPlugin - clean up some references to undeclarared -- Marcus Denker -- http://marcusdenker.de

June 29, 2012

[Pharo-project] [update 1.4] #14447

by Marcus Denker

14447 ----- Issue 6188: [BUG]: (1.4) Put back the correct order in #asert:equals: http://code.google.com/p/pharo/issues/detail?id=6188 Issue 6187: [Bug]: (1.4) Mouse down events are being processed twice http://code.google.com/p/pharo/issues/detail?id=6187 Issue 6117: SimplifiedChineseEnvironment should implement leadingChar http://code.google.com/p/pharo/issues/detail?id=6117 Issue 6082: Missed translated selector for the dialog title in the ColorChooserMorph http://code.google.com/p/pharo/issues/detail?id=6082 -- Marcus Denker -- http://marcusdenker.de

June 29, 2012

Re: [Pharo-project] Jenkins down

by Pavel Krivanek

It's working again... Now you can look at the first tests results from Gulle's bootstrapped image :-) https://ci.lille.inria.fr/pharo/view/Seed%20Project/job/Seed%20-%20SUnit%20… -- Pavel On Fri, Jun 29, 2012 at 9:50 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > Jenkins (https://ci.lille.inria.fr/pharo/) seems to be down. It > stopped responding when the job Seed - SUnit Tests was finishing. > > -- Pavel

June 29, 2012

[Pharo-project] Jenkins down

by Pavel Krivanek

Hi, Jenkins (https://ci.lille.inria.fr/pharo/) seems to be down. It stopped responding when the job Seed - SUnit Tests was finishing. -- Pavel

June 29, 2012

Re: [Pharo-project] EvaluateCommandLineHandler changes

by Guillermo Polito

But why another handler if you could put that in the CommandLineArguments? On Fri, Jun 29, 2012 at 9:06 AM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > On 2012-06-29, at 08:40, Guillermo Polito wrote: > > On Fri, Jun 29, 2012 at 8:40 AM, Guillermo Polito < > guillermopolito(a)gmail.com > >> wrote: > > > >> What if the fileIn is just joined at the end of the argument list for > >> every handler? That way you will be able to do > >> > >> meant stdin :) > > > > > >> echo "-eval blabla" | Vm Image > >> > >> or > >> > >> echo blabla | Vm Image -eval > >> > >> ls | grep fuel | vm image > >> > > why not :) We can easily do that with another command-line class which > always > returns true for #isReponsible: but has a very low priority :) > > >

June 29, 2012

Re: [Pharo-project] EvaluateCommandLineHandler changes

by Camillo Bruni

On 2012-06-29, at 08:40, Guillermo Polito wrote: > On Fri, Jun 29, 2012 at 8:40 AM, Guillermo Polito <guillermopolito(a)gmail.com >> wrote: > >> What if the fileIn is just joined at the end of the argument list for >> every handler? That way you will be able to do >> >> meant stdin :) > > >> echo "-eval blabla" | Vm Image >> >> or >> >> echo blabla | Vm Image -eval >> >> ls | grep fuel | vm image >> why not :) We can easily do that with another command-line class which always returns true for #isReponsible: but has a very low priority :)

June 29, 2012

Re: [Pharo-project] EvaluateCommandLineHandler changes

by Guillermo Polito

On Fri, Jun 29, 2012 at 8:40 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > What if the fileIn is just joined at the end of the argument list for > every handler? That way you will be able to do > > meant stdin :) > echo "-eval blabla" | Vm Image > > or > > echo blabla | Vm Image -eval > > ls | grep fuel | vm image > > > > On Thu, Jun 28, 2012 at 10:06 PM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> :3 great. BTW, los command line handlers son la papa :). >> >> >> On Thu, Jun 28, 2012 at 10:03 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: >> >>> >>> On 2012-06-28, at 22:01, Camillo Bruni wrote: >>> >>> > >>> > On 2012-06-28, at 21:31, Guillermo Polito wrote: >>> > >>> >> Hi Camillo, >>> >> >>> >> the latest introduction of this: >>> >> >>> >> "check if we have an opened stdin" >>> >> FileStream stdin ifNotNilDo:[ :stream| >>> >> stream atEnd ifFalse: [ ^ true ]]. >>> >> >>> >> (I assume for piping?) >>> > >>> > exactly.... >>> > >>> >> Is messing with my other command line args... lets say I have another >>> >> command line argument that runs tests and I do: >>> >> >>> >> Vm image --tests >>> >> >>> >> It tries to open it with the EvaluateCommandLineHandler :S... >>> >> >>> >> Args is: >>> >> >>> >> an OrderedCollection('--test') >>> >> >>> >> And the command line handlers after selecting the responsibles are: >>> >> >>> >> an OrderedCollection(EvaluateCommandLineHandler >>> >> RunTestsCommandLineHandler DefaultCommandLineHandler) >>> >> >>> >> By now I'll try putting my handler a higher priority (1 :P), but, is >>> >> this the expected behavior? >>> > >>> > >>> > >>> > you're right, that's broken (AKA we should add some tests there :P) >>> > >>> > I wanted to write something different there... >>> >>> maybe the filestream test should simply be removed, then piping in >>> commands only works when explicitely specifying the "eval" handler >>> >>> >> >

June 29, 2012