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

Re: [Pharo-dev] problem while parsing xml

by StÃ©phane Ducasse

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 features for Roassal 3d

by Yuriy Tymchuk

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. Uko On 27 Dec 2013, at 13:31, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On 27 Dec 2013, at 11:57, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> Hi! >> >> Ronie will visit Igor and RMoD for more than one month, starting next week. Roassal 3d will be our daily plate. >> >> Broad question: What are the features you would like to see in Roassal 3d? > > I do not know but the list that ronie sent is already nice. > >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > >

Dec. 27, 2013

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

by Benjamin

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] Filter in Nautilus

by Juraj Kubelka

There were some conflicts with the latest image 30664. New slice is SLICE-Issue-12518-Shared-package-filter-history-list-JurajKubelka.2 Cheers, Jura El 27-12-2013, a las 11:37, Juraj Kubelka <juraj.kubelka(a)gmail.com> escribiÃ³: > I have just implemented it in Pharo 30661. See: > - https://pharo.fogbugz.com/f/cases/12518/Shared-package-filter-history-list > - https://pharo.fogbugz.com/f/cases/12515/Set-the-package-filter-on-browse-fu… > > You can load SLICE-Issue-12518-Shared-package-filter-history-list-JurajKubelka.1 > Thanks for any comment. > > Cheers, > Jura > > El 24-12-2013, a las 5:15, Alexandre Bergel <alexandre.bergel(a)me.com> escribiÃ³: > >>> And what about to set the same filter when opening browser from browser? >> >> +1 >> >>> And maybe history can be shared? >> >> +1 >> >> Alexandre >> >> >>> >>> -- >>> Juraj Kubelka >>> >>>> El 23/12/2013, a las 18:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> escribiÃ³: >>>> >>>> The thing is what if you have different things in a handful of browsers? I think that it can make sense to use it in nautilus with tabs. Or be able to quickly browse previous filters. >>>> >>>> Uko >>>> >>>>> On 23 Dec 2013, at 21:29, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>> >>>>> Hi! >>>>> >>>>> I have the impression that it would be great to reuse the filter lastly set when opening a new nautilus. >>>>> For example, if I have a browser with the filter "^Roassal2|^Trachâ, I would like to have the same when opening a new browser. >>>>> >>>>> Am I the only one to feel this? >>>>> >>>>> Cheers, >>>>> Alexandre >>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >

Dec. 27, 2013

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

by Andrei Chis

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] Filter in Nautilus

by Juraj Kubelka

I have just implemented it in Pharo 30661. See: - https://pharo.fogbugz.com/f/cases/12518/Shared-package-filter-history-list - https://pharo.fogbugz.com/f/cases/12515/Set-the-package-filter-on-browse-fu… You can load SLICE-Issue-12518-Shared-package-filter-history-list-JurajKubelka.1 Thanks for any comment. Cheers, Jura El 24-12-2013, a las 5:15, Alexandre Bergel <alexandre.bergel(a)me.com> escribiÃ³: >> And what about to set the same filter when opening browser from browser? > > +1 > >> And maybe history can be shared? > > +1 > > Alexandre > > >> >> -- >> Juraj Kubelka >> >>> El 23/12/2013, a las 18:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> escribiÃ³: >>> >>> The thing is what if you have different things in a handful of browsers? I think that it can make sense to use it in nautilus with tabs. Or be able to quickly browse previous filters. >>> >>> Uko >>> >>>> On 23 Dec 2013, at 21:29, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>> >>>> Hi! >>>> >>>> I have the impression that it would be great to reuse the filter lastly set when opening a new nautilus. >>>> For example, if I have a browser with the filter "^Roassal2|^Trachâ, I would like to have the same when opening a new browser. >>>> >>>> Am I the only one to feel this? >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Dec. 27, 2013

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