November 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Should Nautilus use Rubric?

by Tudor Girba

TxText will become on top of my todo list starting with December or January. Cheers, Doru On Sat, Nov 8, 2014 at 9:15 AM, stepharo <stepharo(a)free.fr> wrote: > And we will need help. > Reading examples, trying and asking questions..... > > Stef > > Indeed. Really great! >> >> Doru >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> On 07 Nov 2014, at 18:23, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: >>> >>> This is the great news! Thanks! >>> >>> Juraj >>> >>> On Nov 7, 2014, at 10:52 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >>>> wrote: >>>> >>>> Actually, Iâm (finally) about to integrate it (an alpha version). >>>> it will be in the image next week :P >>>> >>>> Esteban >>>> >>>> On 07 Nov 2014, at 14:32, Norbert Hartl <norbert(a)hartl.name> wrote: >>>>> >>>>> I think we should submit TxModel to the vaporware awards 2014 :) >>>>> >>>>> Norbert >>>>> >>>>> Am 07.11.2014 um 14:24 schrieb Esteban Lorenzano <estebanlm(a)gmail.com >>>>>> >: >>>>>> >>>>>> I would say yes. >>>>>> we would like to have rubric everywhere we need a real editor :) >>>>>> (while waiting for the new TxModel, this is the âless pain pathâ, IMO) >>>>>> >>>>>> Esteban >>>>>> >>>>>> On 07 Nov 2014, at 14:07, Juraj Kubelka <juraj.kubelka(a)gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>> Hi! >>>>>>> >>>>>>> Is it worth to integrate Rubric into Nautilus? Or is there any >>>>>>> reason not to do it? >>>>>>> >>>>>>> Thank you a lot! >>>>>>> Juraj >>>>>>> >>>>>> >>> >> > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 8, 2014

Musings (Was: NAtiveBoost error)

by Andreas Wacknitz

> Am 07.11.2014 um 16:51 schrieb Kjell Godo <squeaklist(a)gmail.com>: > > This is off topic. > > I tried to post it as a top level thread but I have become unknown. Why do you expect that? Many people here are using Smalltalk for years. Just because you have been silent for some time doesnât mean everybody will forget about you :) > > I don't know if you want this crap in here but I have decided not to wait for the > > postmaster to get back to me on the subject of becoming known. Feel free. > > > > > > ( Original-SUBJECT: "( picoVerse-:( what about state , is state really evil? ) )" ) > > > > > > > I am a Smalltalker. > > But in the past few months i have been running with the Haskellers. > > The Haskellers hate state. > > This seemed strange at first because as a Smalltalker i love(d) state. State iswas my friend. > > 90% of my life as a Smalltalker is state wrangling. I am a state herder. > > The debugger is my staff I use to whack the state. And TestCase is my sheep dog. > > But to the Haskellers > > state is > > the evil trinity > > of > > satan the anti christ and the false prophet > > all rolled into one. > > State is the true dev incarnation of the total catastrophe of development Armageddon. > > Blood up to the bridles for hundreds of miles. Dogs and cats living together. Mass hysteria. > > They say. > > I'm not sure i quite get it yet but they keep preaching on this one point most of all. > > State is evil. > > You must keep all state in a Monad. As many methods/functions m as possible > > must be 100% dependent on the input parameters ONLY. > > No hidden instance variables affecting the return value of m are allowed. > > The only effect m can have is to return a value. > > If all this is true then m is pure. > > And pure is good. Pure is very good. And the wind says > > very. > > So i wonder if any of you fellow > > Smalltalkers > > have thought about this at all. First, there are no good definitions of what is an object oriented language and what is a functional language. Thus, languages like C++, C#, Java are being considered object oriented. But their object orientation is not the same like Smalltalkâs. The same problem exists in the functional language world: Some consider LISP being functional, some deny that. Second, for some years I am constantly seeking for âthe bestâ language to solve my problems in. Alas I wasnât successful yet and donât expect to be successful in the future. Every programming paradigm has its strengths and weaknesses when it comes to real world problems. So in my eyes it is best to know the different programming paradigms and its representative languages in order to be able to choose the best fitting language for your problem at hand. Third, there have been many attempts to create multi-paradigm languages (like C++, C#, Java, Scala, â¦). The idea behind is simple: combine the best characteristics. In my eyes all of them failed because what always have been created is Frankensteinâs monster. When you combine paradigms you will may get some advantages of all but sure you will get a lot of additional complexity. Fourth, it has been said many times before: What makes Smalltalk so nice is not only the language. Itâs the whole system: the language, duck typing, the image (object world), the tools, the VM, the simplicity, the elegance, â¦ And last but not least the communities around. Regards Andreas PS: If you are interested in functional programming and donât like static typing you should have a look at Clojure. It has some nice ideas about how to deal with state concurrently. > Thanks > > Kjell E GodÃ¸ > > > > > > > > > > (((((((((( Maybe Smalltalk should be called Statewalk > > as in yak it up fuzz ball. )))))))))) >

Nov. 8, 2014

Re: [Pharo-dev] Visit/accept method naming philosophy

by stepharo

ben pay attention that OSWindow needs a real polish phase. We logged some items to be fixed in the pharo roadmaps on github in Events.md On 8/11/14 07:28, Ben Coman wrote: > > This is a general query and something I've wondered several times > before in different situations, but I use OSWindow as an example since > that is what I happen to be looking at this time. > > For curiosity I was having a poke around OSWindow and seeing > OSWindowMorphicEventHandler>>handleEvent: > morphicEvent := anEvent accept: self. > > I wanted to view the code that could invoke, so I used <cmd-M> on > #accept: to get the implementors, which lists 116 items, many of which > are unrelated. Now its not toooo hard to "guess" which > implementations are related, but it would be nicer to guess less. > Would it be a reasonable philosophy to distinguish each package's > #accept: method by appending the expect object type, like this... ? > > > OSWindowMorphicEventHandler>>handleEvent: > morphicEvent := anEvent acceptOSEventHandler: self. > > IRVisitor>>visitNode: elem > ^ elem acceptIRVisitor: self > > ParseNodeVisitor>>visitBlockNode: aBlockNode > aBlockNode statements do: > [:statement | statement acceptParseNode: self] > > > Or does such a convention constrain too much how you can extend a > visitor pattern? > > cheers -ben > > > > >

Nov. 8, 2014

Re: [Pharo-dev] Should Nautilus use Rubric?

by stepharo

And we will need help. Reading examples, trying and asking questions..... Stef > Indeed. Really great! > > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > >> On 07 Nov 2014, at 18:23, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: >> >> This is the great news! Thanks! >> >> Juraj >> >>> On Nov 7, 2014, at 10:52 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> Actually, Iâm (finally) about to integrate it (an alpha version). >>> it will be in the image next week :P >>> >>> Esteban >>> >>>> On 07 Nov 2014, at 14:32, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> >>>> I think we should submit TxModel to the vaporware awards 2014 :) >>>> >>>> Norbert >>>> >>>>> Am 07.11.2014 um 14:24 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>> >>>>> I would say yes. >>>>> we would like to have rubric everywhere we need a real editor :) >>>>> (while waiting for the new TxModel, this is the âless pain pathâ, IMO) >>>>> >>>>> Esteban >>>>> >>>>>> On 07 Nov 2014, at 14:07, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: >>>>>> >>>>>> Hi! >>>>>> >>>>>> Is it worth to integrate Rubric into Nautilus? Or is there any reason not to do it? >>>>>> >>>>>> Thank you a lot! >>>>>> Juraj >> >

Nov. 8, 2014

Re: [Pharo-dev] Should Nautilus use Rubric?

by stepharo

When do we get it because we will work on it while other people are on vacation.... ie monday and tuesday with igor and alain. On 7/11/14 14:52, Esteban Lorenzano wrote: > Actually, Iâm (finally) about to integrate it (an alpha version). > it will be in the image next week :P > > Esteban > >> On 07 Nov 2014, at 14:32, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> I think we should submit TxModel to the vaporware awards 2014 :) >> >> Norbert >> >>> Am 07.11.2014 um 14:24 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>> I would say yes. >>> we would like to have rubric everywhere we need a real editor :) >>> (while waiting for the new TxModel, this is the âless pain pathâ, IMO) >>> >>> Esteban >>> >>>> On 07 Nov 2014, at 14:07, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: >>>> >>>> Hi! >>>> >>>> Is it worth to integrate Rubric into Nautilus? Or is there any reason not to do it? >>>> >>>> Thank you a lot! >>>> Juraj >>> >> > >

Nov. 8, 2014

Re: [Pharo-dev] Should Nautilus use Rubric?

by stepharo

On 7/11/14 14:32, Norbert Hartl wrote: > I think we should submit TxModel to the vaporware awards 2014 :) Why do you say that? Did you help? Did you even try to load it. I pair programmed with Igor on it and I felt ALONE! Stef > > Norbert > >> Am 07.11.2014 um 14:24 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> I would say yes. >> we would like to have rubric everywhere we need a real editor :) >> (while waiting for the new TxModel, this is the âless pain pathâ, IMO) >> >> Esteban >> >>> On 07 Nov 2014, at 14:07, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: >>> >>> Hi! >>> >>> Is it worth to integrate Rubric into Nautilus? Or is there any reason not to do it? >>> >>> Thank you a lot! >>> Juraj >> > >

Nov. 8, 2014

Re: [Pharo-dev] Should Nautilus use Rubric?

by stepharo

Esteban This is the best way to make sure that TxText will never get any traction. People should have a look at TxText and help. Igor cannot finish it alone. Stef On 7/11/14 14:24, Esteban Lorenzano wrote: > I would say yes. > we would like to have rubric everywhere we need a real editor :) > (while waiting for the new TxModel, this is the âless pain pathâ, IMO) > > Esteban > >> On 07 Nov 2014, at 14:07, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: >> >> Hi! >> >> Is it worth to integrate Rubric into Nautilus? Or is there any reason not to do it? >> >> Thank you a lot! >> Juraj > >

Nov. 8, 2014

Re: [Pharo-dev] NAtiveBoost error

by Sven Van Caekenberghe

> On 08 Nov 2014, at 00:23, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: > > BTW, I have the websocket B plan for that (first tests make me > think it could be a better plan for my needs). > It will be a different animal, but interesting too. About Zinc Web Sockets: https://github.com/svenvc/docs/blob/master/zinc/zinc-websockets-paper.md But there is also 'STAMP', a STOMP implementation, which is a generic message queue client: https://github.com/svenvc/docs/blob/master/neo/stamp.md Both are pure Pharo. Sven

Nov. 8, 2014

Re: [Pharo-dev] edit values in GTInspector

by Tudor Girba

What Alex was saying is that he only trusts an inspector that he just opened. This is clearly not ideal. Is there a way to get reliably notified when an object changes its state? Cheers, Doru On Sat, Nov 8, 2014 at 7:37 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 07 Nov 2014, at 19:24, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > > > This is strange, I do not remember to have use this when I was using the > old inspector. I usually trust what the inspector tells me only having open > one. > > > > But thatâs the point: if the value changes, the inspector shows the old > one. So you can *not* trust it. > (and all the cool demos do not work anymore: adding an ivar to a class and > the inspector on the object shows > it, inspecting the world and showing how the mouse course position > changesâ¦) > > Marcus > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 8, 2014

Re: [Pharo-dev] inria survey

by Thierry Goubier

2014-11-08 7:32 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > > > > > I've completed it, but some ambiguities I encountered... > > > > What is "Vulgarization of science" > > French people think it is the english translation of the french word > "vulgarisation scientifique" > http://fr.wikipedia.org/wiki/Vulgarisation > > It seems to be in the english dictionary as "to make popular": > http://dictionary.reverso.net/english-definition/vulgarisation > > (coming from latin I guess lots of languages have it with kind-of-the same > meaning.) > For my german ear it sound horrible, as "vulgÃ¤r" has picked up *very* > negative > connotations. > > You really do not want to be that... or make your research that: > http://www.dict.cc/deutsch-englisch/vulgÃ¤r.html > Knowing that "vulgaire" in french has more or less the same meaning than "vulgÃ¤r" in German :) Thierry > > > Marcus > > > > >

Nov. 8, 2014