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

[ANN] Seaside 3.1 and 3.0.10 release

by Torsten Bergmann

Details here: http://lists.squeakfoundation.org/pipermail/seaside/2013-December/030350.ht…

Dec. 27, 2013

Re: [Pharo-dev] Call for fixing the selection in the debugger

by Andrei Chis

The change that seems to have caused this problem is in PluggableTextMorph>>selectionInterval: The selectionInterval instance variable of the morph is not set any more; only the model is updated, which doesn't seem to update the morph. PluggableTextMorph>>selectionInterval: sel setSelectionSelector ifNil: [ selectionInterval := sel ] ifNotNil: [ self model perform:setSelectionSelector with: sel ] This could be solved like bellow, though I'm not sure it is the best solution. If I put a halt in PluggableTextMorph >>inspectIt and hit proceed the the selection is inspected correctly, without this modification. PluggableTextMorph>>selectionInterval: sel selectionInterval := sel. setSelectionSelector ifNotNil: [ self model perform:setSelectionSelector with: sel ] On Fri, Dec 27, 2013 at 3:11 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On 27 Dec 2013, at 13:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > > Hi guys > > > > we should not let the system in such state. We cannot inspect print > expression in the debugger. > > Does anybody have an idea of the change that broke it? > > > Yes: > > https://pharo.fogbugz.com/f/cases/12144/TextModel-getSelection > > it was added in 655, so for reverting the easiest is to dl 654, do a merge > and look at all the changes > (there are just 4-5 that are not re-catorizations). > > This is on my TODO nextâ¦ > > Marcus > > >

Dec. 27, 2013

Re: [Pharo-dev] Call for fixing the selection in the debugger

by Marcus Denker

On 27 Dec 2013, at 14:11, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 27 Dec 2013, at 13:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi guys >> >> we should not let the system in such state. We cannot inspect print expression in the debugger. >> Does anybody have an idea of the change that broke it? >> > Yes: > > https://pharo.fogbugz.com/f/cases/12144/TextModel-getSelection > > it was added in 655, so for reverting the easiest is to dl 654, do a merge and look at all the changes > (there are just 4-5 that are not re-catorizations). > > This is on my TODO nextâ¦ > https://pharo.fogbugz.com/f/cases/12521/Undo-12144-TextModel-getSelection I will check if it actually solves the problem...

Dec. 27, 2013

Re: [Pharo-dev] Fwd: Your request to join pharo-contribution has been accepted

by Serge Stinckwich

On Thu, Nov 21, 2013 at 10:34 AM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > Hi, > > Le 21 nov. 2013 Ã 10:05, Serge Stinckwich a Ã©crit : > >> I would like to able to add jobs on pharo-contribution. >> How I could do that ? > > First, you go to https://ci.inria.fr and create an account (sign up). > Then, ask to join the pharo-contribution project. > We will approve the request and then give admin rights so that you will be able to create a job on jenkins. > To log on Jenkins, you will have to use the credentials of the account created on https://ci.inria.fr. Ok I register on ci.inria.fr with my adress : serge.stinckwich(a)ird.fr I request to join the pharo-contribution project. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Dec. 27, 2013

Re: [Pharo-dev] Call for fixing the selection in the debugger

by Marcus Denker

On 27 Dec 2013, at 13:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > we should not let the system in such state. We cannot inspect print expression in the debugger. > Does anybody have an idea of the change that broke it? > Yes: https://pharo.fogbugz.com/f/cases/12144/TextModel-getSelection it was added in 655, so for reverting the easiest is to dl 654, do a merge and look at all the changes (there are just 4-5 that are not re-catorizations). This is on my TODO nextâ¦ Marcus

Dec. 27, 2013

Re: [Pharo-dev] problem while parsing xml

by StÃ©phane Ducasse

I pushed the latest version of the configuration to the MetacelloRepository. Now unfortunately the last version still has the same problem. stef On 23 Dec 2013, at 18:26, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: > Hello > > using: Pharo3.0 Latest update: #30659 (it occurs same error to > Pharo2.0 Latest update: #20628) > (Moose 4.9 with XML-Parser (DamienCassou.143) has no_err) > > 1. load XMLParser (StephaneDucasse.16) from Configuration browser > 2. select and inspect it below: > ^ XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> > <!DOCTYPE score-partwise PUBLIC > "-//Recordare//DTD MusicXML 3.0 Partwise//EN" > "http://www.musicxml.org/dtds/partwise.dtd"> > <score-partwise version="3.0"> > <part-list> > <score-part id="P1"> > <part-name>Music</part-name> > </score-part> > </part-list> > <part id="P1"> > <measure number="1"> > <attributes> > <divisions>1</divisions> > <key> > <fifths>0</fifths> > </key> > <time> > <beats>4</beats> > <beat-type>4</beat-type> > </time> > <clef> > <sign>G</sign> > <line>2</line> > </clef> > </attributes> > <note> > <pitch> > <step>C</step> > <octave>4</octave> > </pitch> > <duration>4</duration> > <type>whole</type> > </note> > </measure> > </part> > </score-partwise> > ' readStream. > > 3. and get DNU: SmallInteger>>asciiValue > > 'case of XMLZincClient>>#get: > 'http://www.musicxml.com/dtds/partwise.dtd' timeout: ... onError: ... > returns binaryStream? > > > -- > -- > "NISHIHARA Satoshi" > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] > <PharoDebug.log>

Dec. 27, 2013

Re: [Pharo-dev] Strange inspector behavior

by Sven Van Caekenberghe

CharacterSet is more like a Set, not a SequenceableCollection. Something along the lines of EyeSetInspector would fit better. But I tried setting EyeSetInspector as CharacterSet>>#inspectorClass which failed. The question is, is CharacterSet a correct Collection subclass ? And what assumptions does the EyeCollectionInspector make ? On 27 Dec 2013, at 13:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > while trying to understand the problem with the asciiValue for XML I get the following strange > that I cannot reproduce with a simple collection still I want to report it because I can reproduce > with the XML package > > I inspect SeparatorCharacters and I get > > <Screen Shot 2013-12-27 at 13.02.55.pdf> > > now as soon as click on the inspector I get an error printing. > > I thought that there was different paths for the self and each elementsâ¦ but I got lost. > > <Screen Shot 2013-12-27 at 13.03.22.pdf>

Dec. 27, 2013

Strange inspector behavior

by StÃ©phane Ducasse

Hi while trying to understand the problem with the asciiValue for XML I get the following strange that I cannot reproduce with a simple collection still I want to report it because I can reproduce with the XML package I inspect SeparatorCharacters and I get now as soon as click on the inspector I get an error printing. I thought that there was different paths for the self and each elementsâ¦ but I got lost.

Dec. 27, 2013

Re: [Pharo-dev] Call for fixing the selection in the debugger

by StÃ©phane Ducasse

this is also happening in the implementors pane. in fact it is impossible to select a new selection. > Hi guys > > we should not let the system in such state. We cannot inspect print expression in the debugger. > Does anybody have an idea of the change that broke it? > > Stef

Dec. 27, 2013

Call for fixing the selection in the debugger

by StÃ©phane Ducasse

Hi guys we should not let the system in such state. We cannot inspect print expression in the debugger. Does anybody have an idea of the change that broke it? Stef

Dec. 27, 2013