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

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

by Andrei Chis

PluggableTextMorph maintains its own selectionInterval. When the PluggableTextMorph >>selectionInterval: it is called it sets the selection in the model. This will trigger MorphicTextAdapter>>setSelectionFromModel: that should adapt the selection in the morph: MorphicTextAdapter >>setSelectionFromModel: aSelection self widget ifNotNil: [:w | w selectionInterval ~= aSelection ifTrue: [ w setSelection: aSelection ]]. However, the second test (w selectionInterval ~= aSelection) will always return false. This is because PluggableTextMorph>>selectionInterval has the following implementation '^ textMorph editor selectionInterval' And in the editor the selection is already correct (even before PluggableTextMorph >>selectionInterval: is called). Actually most of the methods from PluggableTextMorph that change the selection also explicitly update the selectionInterval instance variable. So the previous solution should work. @Doru this is related with Spec, so we should not have it in Glamour. On Fri, Dec 27, 2013 at 5:07 PM, Benjamin < Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > I think that when the model is notified, it will set it in the morph > So it will happen twice > > Ben > > On 27 Dec 2013, at 15:52, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Wouldn't then explicitly setting the selection of the morph before setting > it in the model be ok? > > PluggableTextMorph>>selectionInterval: sel > selectionInterval := sel. > setSelectionSelector > ifNotNil: [ self model perform:setSelectionSelector with: sel ] > > > On Fri, Dec 27, 2013 at 4:28 PM, Benjamin < > Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > >> 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] problem while parsing xml

by StÃ©phane Ducasse

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> </score-partwise> ' readStream. produces the error while XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> <score-partwise version="3.0"> <part-list> <score-part id="P1"> <part-name>Music</part-name> </score-part> </part-list> </score-partwise> ' readStream. does not. Stef

Dec. 27, 2013

Re: [Pharo-dev] Change Sorter

by StÃ©phane Ducasse

A bug I thought it was fixed during the sprint. Ben this is an opportunity to contribute :) On 27 Dec 2013, at 16:45, btc(a)openinworld.com wrote: > In build 30644 I notice that ChangeSorter seems to have lost most of its usual menu items. For example... > * Copy class to the other change set > * Move class to the other change set > * File out > > Is this intentional as a transition to something else? > cheers -ben > >

Dec. 27, 2013

Re: [Pharo-dev] problem while parsing xml

by Sven Van Caekenberghe

It seems logical that a CharacterSet contains Characters even if its internal implementation uses a bitmap, its API should - I would expect. If nextChar is an Integer in the first code piece, maybe you are reading from a binary stream instead of from a character stream ? On 27 Dec 2013, at 16:34, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > Iâm trying to understand asciiValue > > skipSeparators > | nextChar | > [(nextChar := self peek) not Nil > and: [SeparatorCharacters includes: nextChar]] > whileTrue: [self next]. > > > SeparatorCharacters is a CharacterSet > > nextChar is an integer > > and > > CharacterSet>>includes: aCharacter > aCharacter asciiValue >= 256 > ifTrue: [^ false]. > ^ (map at aCharacter asciiValue + 1) >0 > > but Iâm stuck. > > Stef > > >

Dec. 27, 2013

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

by Tudor Girba

Hi, I reported the problem already: https://pharo.fogbugz.com/f/cases/12479/SpecDebugger-cannot-inspect-from-th… I just tried the GTDebugger in the latest Pharo and it works just fine. If the problem would be in the PluggableTextMorph, it should affect the GTDebugger, too since it is using only a slightly more specialized widget. Or? Andrei, do you have an idea? Cheers, Doru On Fri, Dec 27, 2013 at 4:40 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > **thanks** guys for looking into that because this is blocking. > > Stef > > > > I think that when the model is notified, it will set it in the morph > So it will happen twice > > Ben > > On 27 Dec 2013, at 15:52, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Wouldn't then explicitly setting the selection of the morph before setting > it in the model be ok? > > PluggableTextMorph>>selectionInterval: sel > selectionInterval := sel. > setSelectionSelector > ifNotNil: [ self model perform:setSelectionSelector with: sel ] > > > On Fri, Dec 27, 2013 at 4:28 PM, Benjamin < > Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > >> 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 >>>> >>>> >>>> >>> >>> >> >> > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 27, 2013

Re: [Pharo-dev] [Seaside-dev] [Seaside] [ANN] Seaside 3.1 and 3.0.10 release

by Sven Van Caekenberghe

On 27 Dec 2013, at 11:57, Philippe Marschall <philippe.marschall(a)gmail.com> wrote: > We are pleased to announce the releases of Seaside 3.1 and 3.0.10. That is great news. Congratulations and thank you to the whole team. > Seaside 3.1 is a feature release and contains a range of improvements > and fixes from a variety of people. Seaside 3.0.10 is a minor release > of Seaside 3.0 containing only a single bug fix. > > The changes can be view here: > http://code.google.com/p/seaside/wiki/Seaside310Changelog and here: > http://code.google.com/p/seaside/wiki/Seaside3010Changelog > > A one-click image is available here: > http://www.seaside.st/distributions/Seaside-3.1-OneClick.zip and here: > http://www.seaside.st/distributions/Seaside-3.0.10-OneClick.zip > Mavericks user beware the one click images are not signed. Itâs a pity those are still based on Pharo 1.3, which is becoming quite old now. > Seaside's Metacello configuration has been updated, so Seaside 3.1 can > be loaded into Pharo with: > > Gofer new > url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; > package: 'ConfigurationOfSeaside3'; > load. > ((Smalltalk at: #ConfigurationOfSeaside3) project version: #stable) load. Images of Pharo 2.0 or 3.0 with Seaside preloaded can be found here: https://ci.inria.fr/pharo-contribution/job/Seaside/ Sven > For more control over what gets loaded check out the class comment of > ConfigurationOfSeaside3 that lists the supported groups. > > We would like to thank everybody who contributed to these releases. > > The Seaside Team > _______________________________________________ > seaside-dev mailing list > seaside-dev(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Dec. 27, 2013

Change Sorter

by btc＠openinworld.com

In build 30644 I notice that ChangeSorter seems to have lost most of its usual menu items. For example... * Copy class to the other change set * Move class to the other change set * File out Is this intentional as a transition to something else? cheers -ben

Dec. 27, 2013

Re: [Pharo-dev] Call for features for Roassal 3d

by Yuriy Tymchuk

Wow, this are really cool in-depth tasks. Uko On 27 Dec 2013, at 17:41, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On 27 Dec 2013, at 16:29, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> I wasnât able to find Ronieâs list. >> >> One thing that I find crucial - is navigation. Video-game navigation is cool, but you must agree that itâs not always what you need. Maybe it would be useful to be able to rotate around the centre of a scene (or around element). Iâm not sure about my proposals, but navigation should be interesting to look on. >> > > here are the items: > > Some tasks required are as follow: > - An easy way to make bindings for C++ libraries. For this I am going to start extending SWIG(http://www.swig.org/) so it can generate bindings for Pharo NativeBoost. > - Bindings for the Bullet physics engine(http://bulletphysics.org/wordpress/). With the extensions for swig, this is trivial. > - An importer for COLLADA. COLLADA is a XML based asset exchange format, with a wide support in different 3d model editors, such as Blender. > - For Linux, a new VM display module is required. The current that uses just X11 suffers of severe tearing and flickering. I would like to make a display module for the VM that uses SDL2, which is a cross platform library that supports hardware accelerated graphics, or cross platform creation of an OpenGL context. > - I think that garbage collection would require some determinism/time constraint or write some guidelines to avoid triggering the gargbage collector. When I'm testing the particles, I can see some noticeable pause, that I attribute to the garbage collector. >

Dec. 27, 2013

Re: [Pharo-dev] Call for features for Roassal 3d

by StÃ©phane Ducasse

On 27 Dec 2013, at 16:29, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > I wasnât able to find Ronieâs list. > > One thing that I find crucial - is navigation. Video-game navigation is cool, but you must agree that itâs not always what you need. Maybe it would be useful to be able to rotate around the centre of a scene (or around element). Iâm not sure about my proposals, but navigation should be interesting to look on. > here are the items: Some tasks required are as follow: - An easy way to make bindings for C++ libraries. For this I am going to start extending SWIG(http://www.swig.org/) so it can generate bindings for Pharo NativeBoost. - Bindings for the Bullet physics engine(http://bulletphysics.org/wordpress/). With the extensions for swig, this is trivial. - An importer for COLLADA. COLLADA is a XML based asset exchange format, with a wide support in different 3d model editors, such as Blender. - For Linux, a new VM display module is required. The current that uses just X11 suffers of severe tearing and flickering. I would like to make a display module for the VM that uses SDL2, which is a cross platform library that supports hardware accelerated graphics, or cross platform creation of an OpenGL context. - I think that garbage collection would require some determinism/time constraint or write some guidelines to avoid triggering the gargbage collector. When I'm testing the particles, I can see some noticeable pause, that I attribute to the garbage collector.

Dec. 27, 2013

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

by StÃ©phane Ducasse

**thanks** guys for looking into that because this is blocking. Stef > I think that when the model is notified, it will set it in the morph > So it will happen twice > > Ben > > On 27 Dec 2013, at 15:52, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > >> Wouldn't then explicitly setting the selection of the morph before setting it in the model be ok? >> >> PluggableTextMorph>>selectionInterval: sel >> selectionInterval := sel. >> setSelectionSelector >> ifNotNil: [ self model perform:setSelectionSelector with: sel ] >> >> >> On Fri, Dec 27, 2013 at 4:28 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >> 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