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

Re: [Pharo-dev] State of SVG importer

by hilaire

Got it working on 3.0. Indeed gradient is not handled. However I can see a ASGradient hierarchy. Hilaire -- View this message in context: http://forum.world.st/State-of-SVG-importer-tp4710870p4711359.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 30, 2013

Re: [Pharo-dev] State of SVG importer

by hilaire

Ok -- View this message in context: http://forum.world.st/State-of-SVG-importer-tp4710870p4711353.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 30, 2013

[update 3.0] #30432

by Marcus Denker

30432 ----- 11687 Merge Opal with Opal Repository https://pharo.fogbugz.com/f/cases/11687 - fixed 11210: error when creating a method in the debugger - added timesRepeat: optimization - fixed some 'isNil ifTrue:' to 'ifNil:' - fixed some typos. - add an AbstractCompiler class - fixed a temp mapping debugger bug in case of a scope nested in an optimized scope. - added cleanBlock analysis (However Opal does not use the result of the analysis) Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Tests-MarcusDenk… http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenke…

Sept. 30, 2013

Re: [Pharo-dev] Backport of memory issue solution to Pharo 2.0?

by Goubier Thierry

This is really something I need. I couldn't solved a related issue many months ago when developping with Spec under 2.0; now that I'm backporting Esteban's solution, I'm not entirely sure I'm picking the right changes (i.e. the backport fix reduces to far less code, given that Spec has evolved a bit between 2.0 and 3.0). Thierry Le 30/09/2013 09:27, StÃ©phane Ducasse a Ã©crit : > esteban told me that he found a way to systematically reproduce the problem with his massive online game or something like that. > > Stef > > > On Sep 30, 2013, at 9:26 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> I did some work on the relevant issue, as far as I could understand it (issue 11639). >> >> Now, if I could find a way to check that it really cures the problem... >> >> Thierry >> >> Le 29/09/2013 21:14, StÃ©phane Ducasse a Ã©crit : >>> >>> On Sep 29, 2013, at 9:08 PM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>> >>>> I am experiencing the ever growing image issue in dev work and it is really a pain. >>>> >>>> Any back porting to 2.0? >>> >>> Yes it is planned. Just did not have the time last week. >>> If somebody wants to help this is more than welcome. >>> >>>> >>>> TIA >>>> Phil >>> >>> >>> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 30, 2013

Re: [Pharo-dev] Backport of memory issue solution to Pharo 2.0?

by StÃ©phane Ducasse

esteban told me that he found a way to systematically reproduce the problem with his massive online game or something like that. Stef On Sep 30, 2013, at 9:26 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > I did some work on the relevant issue, as far as I could understand it (issue 11639). > > Now, if I could find a way to check that it really cures the problem... > > Thierry > > Le 29/09/2013 21:14, StÃ©phane Ducasse a Ã©crit : >> >> On Sep 29, 2013, at 9:08 PM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >> >>> I am experiencing the ever growing image issue in dev work and it is really a pain. >>> >>> Any back porting to 2.0? >> >> Yes it is planned. Just did not have the time last week. >> If somebody wants to help this is more than welcome. >> >>> >>> TIA >>> Phil >> >> >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Sept. 30, 2013

Re: [Pharo-dev] Backport of memory issue solution to Pharo 2.0?

by Goubier Thierry

I did some work on the relevant issue, as far as I could understand it (issue 11639). Now, if I could find a way to check that it really cures the problem... Thierry Le 29/09/2013 21:14, StÃ©phane Ducasse a Ã©crit : > > On Sep 29, 2013, at 9:08 PM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > >> I am experiencing the ever growing image issue in dev work and it is really a pain. >> >> Any back porting to 2.0? > > Yes it is planned. Just did not have the time last week. > If somebody wants to help this is more than welcome. > >> >> TIA >> Phil > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 30, 2013

[update 3.0] #30431

by Marcus Denker

30431 ----- 11718 SyntaxError is a really bad name https://pharo.fogbugz.com/f/cases/11718 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1278.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Tools-MarcusDenker.112… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-MarcusDenke…

Sept. 30, 2013

Re: [Pharo-dev] Dynamically adding nodes to Roassal

by Tudor Girba

You would get answers to these questions faster on the moose mailing list. Doru On Mon, Sep 30, 2013 at 8:13 AM, roberto.minelli(a)usi.ch < roberto.minelli(a)usi.ch> wrote: > Anyone can help here? > > On Sep 20, 2013, at 5:32 PM, roberto.minelli(a)usi.ch wrote: > > > Hi, > > > > It's me again.. > > > > I managed to have something *almost* working, but the behavior of the > ROTreeMapLayout is not clear to me. > > > > Using the ROMondrianViewBuilder I can specify the size of the Tree map, > but then I am not able to dynamically add nodes. Well, at least I did not > manage to do that. So I moved to pure Roassal, as suggested by Alejandro. > > > > Here's how my actual code looks like: http://ws.stfx.eu/CFM522Z9X3ES > > > > I am a beginner with Roassal, so I spend some time to figure out how to > draw the tree map in this way. I did not really quite understand why I have > to add the ROBox new size: 200 to the ROElement, but I'll figure it out. > > > > The thing is when I try to add the new node. Following, again, > Alejandro's advice I am writing something like: > > > > "I add a new node, re-layout the view, and signalUpdate" > > rawView add: ((ROElement on: 10) + (ROBox new size: 200)). > > (ROTreeMapLayout withWeightBlock: [ :e | e model ]) applyOn: rawView > elements. > > rawView signalUpdate . > > > > The result is quite strange, the view is indeed updated but I cannot > understand why all sizes are messed up. > > > > My questions, in short are: How can I fix the overall size of the tree > map? Am I doing everything correct till now? > > > > Thanks again for your help, > > Roby > > > > On Sep 20, 2013, at 11:24 AM, roberto.minelli(a)usi.ch wrote: > > > >> Hi, > >> > >> I was playing around with Roassal (in particular, a tree map) and I > have a question: Is there a way to dynamically adding nodes? I mean, once > the view is generated to update the #nodes by adding a new node (and > associations as well, i.e., edges) and have the visualization re- > >> > >> Thanks in advance. > >> > >> Roby > > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 30, 2013

Re: [Pharo-dev] Dynamically adding nodes to Roassal

by roberto.minelli＠usi.ch

Anyone can help here? On Sep 20, 2013, at 5:32 PM, roberto.minelli(a)usi.ch wrote: > Hi, > > It's me again.. > > I managed to have something *almost* working, but the behavior of the ROTreeMapLayout is not clear to me. > > Using the ROMondrianViewBuilder I can specify the size of the Tree map, but then I am not able to dynamically add nodes. Well, at least I did not manage to do that. So I moved to pure Roassal, as suggested by Alejandro. > > Here's how my actual code looks like: http://ws.stfx.eu/CFM522Z9X3ES > > I am a beginner with Roassal, so I spend some time to figure out how to draw the tree map in this way. I did not really quite understand why I have to add the ROBox new size: 200 to the ROElement, but I'll figure it out. > > The thing is when I try to add the new node. Following, again, Alejandro's advice I am writing something like: > > "I add a new node, re-layout the view, and signalUpdate" > rawView add: ((ROElement on: 10) + (ROBox new size: 200)). > (ROTreeMapLayout withWeightBlock: [ :e | e model ]) applyOn: rawView elements. > rawView signalUpdate . > > The result is quite strange, the view is indeed updated but I cannot understand why all sizes are messed up. > > My questions, in short are: How can I fix the overall size of the tree map? Am I doing everything correct till now? > > Thanks again for your help, > Roby > > On Sep 20, 2013, at 11:24 AM, roberto.minelli(a)usi.ch wrote: > >> Hi, >> >> I was playing around with Roassal (in particular, a tree map) and I have a question: Is there a way to dynamically adding nodes? I mean, once the view is generated to update the #nodes by adding a new node (and associations as well, i.e., edges) and have the visualization re- >> >> Thanks in advance. >> >> Roby > >

Sept. 30, 2013

Re: [Pharo-dev] Use pharo users mailing list

by Friedrich Dominicus

Stephan Eggermont <stephan(a)stack.nl> writes: > Kilon wrote >>Here is a radical suggestion you probably don't want to hear. >>Close down Pharo users mailing list, redirect everyone to stackoverflow. > > Definitely not. Stackoverflow is nearly dead, and seriously unsuitable for > small languages. Good questions will get closed by clueless people. > Good answers will get downvoted because they go against majority > views. The ranking system is heavily skewed towards popular languages. > Stackoverflow doesn't allow discussions (and interesting questions), > which is a major reason to have these lists. > > To see for yourself, take a look at the questions related to OODBs. Well I just can confirmm that for me. I can not judge if it's dead but it's at least much less interesting then two years or so ago. You cannot ask any comparison questions any more. You can not ask questions about maintainability any more, because that will get closed. No Stackoverfow is not the answer. Maybe a kind of Forum would be nice to have. At least I'm not aware of any related to Smalltalk, but I may be wrong of course. Regards Friedrich

Sept. 30, 2013