- Pharo-dev - lists.pharo.org

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

by Benjamin

ok :( Then I run out of brilliant idea :P Ben On 27 Dec 2013, at 15:25, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Adding 'self changed' at the end of the current PluggableTextMorph>>selectionInterval: doesn't solve the problem. > > > On Fri, Dec 27, 2013 at 4:15 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > Because when the focus changes, the morph is proposed to redraw itself > Try with a > > self changed > > at the end > > Ben > > On 27 Dec 2013, at 14:44, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > >> >> 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 Andrei Chis

Adding 'self changed' at the end of the current PluggableTextMorph>>selectionInterval: doesn't solve the problem. On Fri, Dec 27, 2013 at 4:15 PM, Benjamin < Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > Because when the focus changes, the morph is proposed to redraw itself > Try with a > > self changed > > at the end > > Ben > > On 27 Dec 2013, at 14:44, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > > 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 Benjamin

Because when the focus changes, the morph is proposed to redraw itself Try with a self changed at the end Ben On 27 Dec 2013, at 14:44, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > 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] Thank you for Pharo

by Tudor Girba

Thank you for your message. Thank you for your enthusiasm. And thank you for sticking with us. About your particular problem domain you could probably benefit from looking more closely into Moose ( http://www.moosetechnology.org/about/contact) which is a broader platform for software and data analysis built on top of Pharo, and Roassal is part of it. Cheers, Doru On Fri, Dec 27, 2013 at 11:16 AM, Volkert Barr <volkert(a)nivoba.de> wrote: > Thank you for Pharo â¦. > > I am following the development of Pharo since its fork from Squeak, and i > am really impressed what you crazy guys all have archived the last years. > It all evolved to really nice language, a fantastic nice looking live > programming environment, cool packages and a growing ecosystems. I have so > much fun using Pharo. Thank you. > > 2011 i gave me a push to learn Pharo and last year i decided to do a small > research prototype with it. The goal is a tool to analyze and visualize > application landscapes. I have implemented a small repository model for the > different architecture levels, some data analytic rules on top the model, > and some model visualizations. For visualization i use Roassal/Mondrian. > For Data-In/-Export i use simply NeoCSV. Next year i plan to add more data > analytic rules, to add model transformation operations to "simulate" > landscape transformations (projects), and to use 3D visualizations with > Roassal3D (City Metaphor). If all works fine, we see what 2015 brings ... > > Pharo is really a productivity boost for me. If you are able to play > around with the objects in an interactive environment life is getting so > much easier. > > My wishes for Pharo: > > - Some kind of "Pharo Capability Map". It is really hard to understand for > a newbie what Pharo is all supporting, what is planed for the future, what > the library names are, .... > - Stable Pharo 3.0 > - Roassal3D (Roassal is so coooool, one of the killer frameworks for > Pharo). > - More User Interface programming examples > - 64 Bit VM and MultiCore Support > > Thank you guys, and best wishes for 2014 > Volkert > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 27, 2013

[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