- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Nautilus as default/only Systembrowser for pharo3

by kilon alios

there is no "should" in a open source project. Saying that I very much doubt it there is a single pharoer that does not care about the stability and improvement of his own code. Experimentation is part of the game of learning, and without learning you can have no bug fixes. If you don't understand the problem then you cant fix it. Or even worse you may think its not broken in the first place. On Tue, Dec 24, 2013 at 11:06 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > 2013/12/24 kilon alios <kilon.alios(a)gmail.com> > >> I agree too , having realistic expectations is the wise thing to do. All >> of us want the Stars and the Moon , the question is what we can really >> have and that we all or at least most of us do contribute even in very >> small portions. Whats better way to live than improve the very things we >> love ? >> >> Personally I love all the new "unclean" things I see in pharo. Why keep >> things in a closet because of unknown bugs, unleash them to the world and >> let the world shape them to something mature. Thats how you make great >> code. >> >> >> On Tue, Dec 24, 2013 at 3:52 PM, StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr> wrote: >> >>> >>> >> I really like Nautilus, the groups, the history navigation, the code >>> panel with the color warning for >>> >> long methods. It is good doing experiments with new or better >>> developer tools. >>> >> >>> >> But some parts just looking as "quickly hacked into it", just to make >>> it running. >>> >> And there are bugs. >>> >> Nautilus could need some refactoring/code cleanup. >>> >> >>> >> In my point of view, in a clean and stable pharo release, >>> >> all smalltalks tools (browser debugger inspectro ...) should show you >>> >> "look, thats the way of doing it in smalltalk /pharo". >>> >> >>> >> >>> >> I would really like to more emphasis on "clean and stableâ. >>> >>> Oh yes. Now if somebody has 5 engineers that do not know what to do, I >>> have some ideas :) >>> >>> > Yes.. the problem is not the âwantâ but the âdoââ¦ in the end we always >>> need to manage >>> > it with the limited resources we haveâ¦ >>> >>> + 1 >>> This is why we should simplify and clean it. >>> >>> Stef >>> >> >> > > I understand, lack of time/manpower. But if we have the time, to introduce > new or experimental things, > we should focus to have stable tools. > > >

Dec. 24, 2013

Re: [Pharo-dev] Nautilus as default/only Systembrowser for pharo3

by Nicolai Hess

2013/12/24 kilon alios <kilon.alios(a)gmail.com> > I agree too , having realistic expectations is the wise thing to do. All > of us want the Stars and the Moon , the question is what we can really > have and that we all or at least most of us do contribute even in very > small portions. Whats better way to live than improve the very things we > love ? > > Personally I love all the new "unclean" things I see in pharo. Why keep > things in a closet because of unknown bugs, unleash them to the world and > let the world shape them to something mature. Thats how you make great > code. > > > On Tue, Dec 24, 2013 at 3:52 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> >> >> I really like Nautilus, the groups, the history navigation, the code >> panel with the color warning for >> >> long methods. It is good doing experiments with new or better >> developer tools. >> >> >> >> But some parts just looking as "quickly hacked into it", just to make >> it running. >> >> And there are bugs. >> >> Nautilus could need some refactoring/code cleanup. >> >> >> >> In my point of view, in a clean and stable pharo release, >> >> all smalltalks tools (browser debugger inspectro ...) should show you >> >> "look, thats the way of doing it in smalltalk /pharo". >> >> >> >> >> >> I would really like to more emphasis on "clean and stableâ. >> >> Oh yes. Now if somebody has 5 engineers that do not know what to do, I >> have some ideas :) >> >> > Yes.. the problem is not the âwantâ but the âdoââ¦ in the end we always >> need to manage >> > it with the limited resources we haveâ¦ >> >> + 1 >> This is why we should simplify and clean it. >> >> Stef >> > > I understand, lack of time/manpower. But if we have the time, to introduce new or experimental things, we should focus to have stable tools.

Dec. 24, 2013

Re: [Pharo-dev] Transparent colors with NBOpenGL?

by Igor Stasenko

On 24 December 2013 21:01, Ronie Salgado <roniesalg(a)gmail.com> wrote: > Hi Denis, > > The shape color is not enough to know about its transparency, because it > could have a texture with partially transparent elements. Despite that, > there's another kind of transparency, fully opaque or fully transparent, > which doesn't require special rendering. That other kind of transparency is > supported by the multi-pass lighting models. > > ... and there are many different techniques for rendering scenes with semi-transparent objects, including ray-tracing. Some solutions are simple some are complex, and require significant efforts for implementing them, like properly organizing/adjusting data structures and rendering pipeline. So, answering question if it 'can be automatic', - yes, if someone will implement it. OpenGL out-of-the-box, don't have such automagic. Greetings > Ronie Salgado > > > 2013/12/24 Denis Kudriashov <dionisiydk(a)gmail.com> > >> Hi >> >> 2013/12/24 Alexandre Bergel <alexandre.bergel(a)me.com> >> >>> >>> el1 := (R3CubeShape new color: (Color purple alpha: 0.2)) element. >>> el2 := (R3CubeShape new color: (Color purple alpha: 0.2)) element. >>> el1 makeTranslucent. >> >> >> Can it be automatic? Element has color which know about its transparency >> > > -- Best regards, Igor Stasenko.

Dec. 24, 2013

Re: [Pharo-dev] Nautilus as default/only Systembrowser for pharo3

by kilon alios

I agree too , having realistic expectations is the wise thing to do. All of us want the Stars and the Moon , the question is what we can really have and that we all or at least most of us do contribute even in very small portions. Whats better way to live than improve the very things we love ? Personally I love all the new "unclean" things I see in pharo. Why keep things in a closet because of unknown bugs, unleash them to the world and let the world shape them to something mature. Thats how you make great code. On Tue, Dec 24, 2013 at 3:52 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > >> I really like Nautilus, the groups, the history navigation, the code > panel with the color warning for > >> long methods. It is good doing experiments with new or better developer > tools. > >> > >> But some parts just looking as "quickly hacked into it", just to make > it running. > >> And there are bugs. > >> Nautilus could need some refactoring/code cleanup. > >> > >> In my point of view, in a clean and stable pharo release, > >> all smalltalks tools (browser debugger inspectro ...) should show you > >> "look, thats the way of doing it in smalltalk /pharo". > >> > >> > >> I would really like to more emphasis on "clean and stableâ. > > Oh yes. Now if somebody has 5 engineers that do not know what to do, I > have some ideas :) > > > Yes.. the problem is not the âwantâ but the âdoââ¦ in the end we always > need to manage > > it with the limited resources we haveâ¦ > > + 1 > This is why we should simplify and clean it. > > Stef >

Dec. 24, 2013

Re: [Pharo-dev] Transparent colors with NBOpenGL?

by Ronie Salgado

Hi Denis, The shape color is not enough to know about its transparency, because it could have a texture with partially transparent elements. Despite that, there's another kind of transparency, fully opaque or fully transparent, which doesn't require special rendering. That other kind of transparency is supported by the multi-pass lighting models. Greetings Ronie Salgado 2013/12/24 Denis Kudriashov <dionisiydk(a)gmail.com> > Hi > > 2013/12/24 Alexandre Bergel <alexandre.bergel(a)me.com> > >> >> el1 := (R3CubeShape new color: (Color purple alpha: 0.2)) element. >> el2 := (R3CubeShape new color: (Color purple alpha: 0.2)) element. >> el1 makeTranslucent. > > > Can it be automatic? Element has color which know about its transparency >

Dec. 24, 2013

Re: [Pharo-dev] Filter in Nautilus

by Juraj Kubelka

Thank you to remind me. I will fix it on Thursday. Jura. -- Juraj Kubelka > El 24/12/2013, a las 13:57, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> escribiÃ³: > > Hi Juraj > > did you fix the problem reported with the search input capturing events or I do not know what that was reported a > while ago? > > Stef >> On 24 Dec 2013, at 00:47, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: >> >> And what about to set the same filter when opening browser from browser? >> >> And maybe history can be shared? >> >> Cheers, >> Jura >> >> -- >> 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 >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >

Dec. 24, 2013

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

by Serge Stinckwich

I'm trying to signup on INRIA CI site here : https://ci.inria.fr/users/new without success ... apparently the continue button is inactive. Regards, 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. > > Regards, > Christophe. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Dec. 24, 2013

Re: [Pharo-dev] problem while parsing xml

by HernÃ¡n Morales Durand

I have tried in Pharo 2.0 configurations from Config Browser (ConfigurationOfXMLParser-StephaneDucasse.16) and latest from http://www.smalltalkhub.com/mc/PharoExtras/XMLParser/main(ConfigurationOfXM… and both have this bug. HernÃ¡n 2013/12/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi Satoshi > > Did you try with the latest configuration of XMLParser? > Because I do not know what it is in Moose. > 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. 24, 2013

Re: [Pharo-dev] [Moose-dev] #deepCollect:

by StÃ©phane Ducasse

Hi chris I think that it would be great if: - your api is compatible with the one of doru - that we can introduce your extension to Pharo - keep the package of doru outside because it is larger. With such approach we could get a first version with your code and a larger one with the one of doru and people would love it on demand. Stef On 13 Dec 2013, at 18:02, Chris Cunningham <cunningham.cb(a)gmail.com> wrote: > Hi. > > I was reading with interest the blog post on Traversal-enabled objects ( http://www.humane-assessment.com/blog/traversal-enabled-pharo-objects ) when I noticed the method #deepCollect: referenced. Interestingly, I have a method called #deepCollect: that is use (wtih related methods like #deepDo: and #deepSelect:). I suspect these uses may be compatible, with the traveral versions being more generic. > > My set of #deep methods allow arbitrary flattening of collections. The #flatCollect: suite in Pharo today flattens objects 1 level; the #deepCollect: flattens the collections as many levels deep as they are nested. I found this to be a really useful ability when I work with PetitParser parsings, which tend give back massively nested Arrays by default. > > If you are interested, it is published at: http://www.smalltalkhub.com/#!/~cbc/DeepCollection/ . > > -cbc

Dec. 24, 2013

Re: [Pharo-dev] Are #explorerContents and #hasContentsInExplorer obsolete ?

by StÃ©phane Ducasse

I do not know but we should log that somewhere. Stef On 21 Dec 2013, at 15:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > It seems that #explorerContents and #hasContentsInExplorer are no longer used. > > Implementing a new Eye inspector with #addSpecialFields: seems to affect both the Inspector view as well as the Tree Inspector. > > So, should they be removed ? > > Sven >

Dec. 24, 2013