- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] nil inspect

by Dimitris Chloupis

is it ? I always thought it was just one of those things that is not an object , together with super and self. I vaguelly remember that 5-6 words in Smalltalk are not objects. If it is an actual object and not something else wrapped in a very thin object, I can see the reason for inspection. Otherwise I cannot say I see it. On Thu, Nov 23, 2017 at 10:45 AM Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > But it is not nothing. It is real object. > > 2017-11-23 9:03 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > >> Personally I love it >> >> what you find when you search for nothing ? >> >> Nothing >> >> :D >> >> On Wed, Nov 22, 2017 at 10:23 PM Stephane Ducasse < >> stepharo.self(a)gmail.com> wrote: >> >>> Indeed I do not really like the blank window. >>> >>> On Sat, Nov 18, 2017 at 10:18 PM, Nicolas Cellier < >>> nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> >>>> Ah OK, it's expected then? >>>> I find that surprising, because I could maybe want to look at meta side >>>> like I can for other elementary objects: >>>> >>>> [image: Images intÃ©grÃ©es 1] >>>> >>>> 2017-11-18 22:03 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: >>>> >>>>> Yes >>>>> >>>>> [image: Inline images 1] >>>>> >>>>> Cheers, >>>>> Alex >>>>> >>>>> On 18 November 2017 at 21:56, Nicolas Cellier < >>>>> nicolas.cellier.aka.nice(a)gmail.com> wrote: >>>>> >>>>>> Anyone tried 'nil inspect' recently? >>>>>> >>>>> >>>>> >>>> >>> >

Nov. 23, 2017

Re: [Pharo-dev] Advent of code

by philippe.back＠highoctane.be

I made an adventofcode channel in Discord. Time for bots... Phil On Nov 22, 2017 21:25, "Stephane Ducasse" <stepharo.self(a)gmail.com> wrote: > Ok can you put a link on the advent of code web page? > > On Wed, Nov 22, 2017 at 9:11 PM, Julien <julien.delplanque(a)inria.fr> > wrote: > >> Iâll write a README with some instructions to avoid clash when merging >> pull requests. >> >> For example, each participant could create a directory with its name and >> put all his stuff inside it. >> >> Julien >> >> Le 22 nov. 2017 Ã 21:09, Stephane Ducasse <stepharo.self(a)gmail.com> a >> Ã©crit : >> >> Tx I forked it. >> >> On Wed, Nov 22, 2017 at 5:38 PM, Julien <julien.delplanque(a)inria.fr> >> wrote: >> >>> Ok I created one [1], maybe if multiple people are playing with me we >>> can gather the different solutions we get for each puzzle in this >>> repository. >>> >>> Julien >>> >>> [1]: https://github.com/juliendelplanque/AdventOfCode2017WithPharo >>> >>> Le 22 nov. 2017 Ã 16:55, Stephane Ducasse <stepharo.self(a)gmail.com> a >>> Ã©crit : >>> >>> Julien >>> >>> could you open a github project so that we can do the same as norviq? >>> And get a log of the problems and solution? >>> >>> Stef >>> >>> On Wed, Nov 22, 2017 at 2:25 PM, Serge Stinckwich < >>> serge.stinckwich(a)gmail.com> wrote: >>> >>>> BTW, the Japanese Smalltalk community is doing an advent Calendar every >>>> year: >>>> >>>> https://qiita.com/advent-calendar/2016/smalltalk >>>> >>>> The 2017 edition is in preparation here: https://qiita.com/advent-calen >>>> dar/2017/smalltalk >>>> >>>> >>>> >>>> On Wed, Nov 22, 2017 at 1:29 PM, Stephane Ducasse < >>>> stepharo.self(a)gmail.com> wrote: >>>> >>>>> Hi pharoers >>>>> >>>>> I would like to know if you would like to participate to >>>>> http://adventofcode.com/2016 >>>>> >>>>> For example we could do the same as >>>>> https://github.com/norvig/pytudes/blob/master/ipynb/Advent%2 >>>>> 0of%20Code.ipynb >>>>> >>>>> Stef >>>>> >>>>> >>>> >>>> >>>> -- >>>> Serge Stinckwich >>>> UMI UMMISCO 209 (IRD/UPMC/UY1) >>>> "Programs must be written for people to read, and only incidentally for >>>> machines to execute."http://www.doesnotunderstand.org/ >>>> >>> >>> >>> >> >> >

Nov. 23, 2017

I love the launcher!!!!

by Stephane Ducasse

Hi I love the PharoLauncher. It helps me to manage my parallel development and projects. We should put a link on the Pharo web site because http://files.pharo.org/platform/launcher/ is arcane. Stef

Nov. 23, 2017

Re: [Pharo-dev] nil inspect

by Denis Kudriashov

But it is not nothing. It is real object. 2017-11-23 9:03 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > Personally I love it > > what you find when you search for nothing ? > > Nothing > > :D > > On Wed, Nov 22, 2017 at 10:23 PM Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > >> Indeed I do not really like the blank window. >> >> On Sat, Nov 18, 2017 at 10:18 PM, Nicolas Cellier < >> nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >>> Ah OK, it's expected then? >>> I find that surprising, because I could maybe want to look at meta side >>> like I can for other elementary objects: >>> >>> [image: Images intÃ©grÃ©es 1] >>> >>> 2017-11-18 22:03 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: >>> >>>> Yes >>>> >>>> [image: Inline images 1] >>>> >>>> Cheers, >>>> Alex >>>> >>>> On 18 November 2017 at 21:56, Nicolas Cellier < >>>> nicolas.cellier.aka.nice(a)gmail.com> wrote: >>>> >>>>> Anyone tried 'nil inspect' recently? >>>>> >>>> >>>> >>> >>

Nov. 23, 2017

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo TechTalk 21 Nov: Discord Demo

by Dimitris Chloupis

On Wed, Nov 22, 2017 at 6:03 PM Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > On Nov 21, 2017, at 19:54, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > Well done :) > > Now you can make a discord client inside the Pharo image if you want. > > > Exactly :-) I am looking for integrations that improve the developer > experience. Maybe the interface should be different from the standard > client. The question is how to integrate and why? What do you think? > > Cheers, > Juraj > Well its a highly personally question For me it was easy to, well realtive easy, because my Atlas pharo library allows me to use any python library fron inside Pharo , so techically I could use the existing Python API to make a Discord client inside Pharo , without a need to create a wrapper (live tranlation and executing of code). I was already familiar with the Discord API because I made a bot for the Discord server (I am the one that created the Discord server for Pharo. I did not intend to move the community from Slack to Discord , but Esteban liked its so much that pused it forward as an idea and it did happen). The API its quite simple so making a client inside Pharo should not be hard. But never felt the need to have a Discord client inside Pharo. On the other hand I never expected our Discord community to grow so large and so active, so fast. Unfortunately I decided to take on creating a Python project so I did not have much usage for Pharo (Python is embeded so it makes Pharo usage quite tricky for me) lately but I am still available for advice, recommendations and so forth. If you start making a Discord client inside the image, make sure you join the Discord API server, they are extremely helpful and they even have a channel for testing bots. A Discord bot uses the same API as a potential client. Now on the how... What I would have done would have been to add the client as tab to the welcome dialog we have when ones first open the image and also as an option to GTSpotter , it would be in the form of "Ask Pharo a Question" and it would send the question directly to our help channel so that beginners could get real time help with any problem they had even those unaware of the existance of Discord. Obviously the option would also exist to expand it to a full Discord interface but my idea was mostly to keep it simple and minimal. One channel, one line, one inpute, and one short list of messages scrolling back and forward. Thats one way, there are obviously billions of other ways to do this.

Nov. 23, 2017

Re: [Pharo-dev] nil inspect

by Dimitris Chloupis

Personally I love it what you find when you search for nothing ? Nothing :D On Wed, Nov 22, 2017 at 10:23 PM Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Indeed I do not really like the blank window. > > On Sat, Nov 18, 2017 at 10:18 PM, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > >> Ah OK, it's expected then? >> I find that surprising, because I could maybe want to look at meta side >> like I can for other elementary objects: >> >> [image: Images intÃ©grÃ©es 1] >> >> 2017-11-18 22:03 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: >> >>> Yes >>> >>> [image: Inline images 1] >>> >>> Cheers, >>> Alex >>> >>> On 18 November 2017 at 21:56, Nicolas Cellier < >>> nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> >>>> Anyone tried 'nil inspect' recently? >>>> >>> >>> >> >

Nov. 23, 2017

Re: [Pharo-dev] Problem with primitive instVarAt: / instVarAt:put:, what should we do ?

by ClÃ©ment Bera

On Wed, Nov 22, 2017 at 9:05 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi clement > > you should discuss with marcus. I had the impression that he was > thinking that slot should disappear. > Then let's use fieldAt:/fieldAt:put: > > Stef > > On Wed, Nov 22, 2017 at 2:35 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> > wrote: > > Hi All, > > > > It seems Pharo is lacking the slotAt: / slotAt:put: primitive and that > the > > instVarAt: / instVarAt:put: primitive is not doing what it says it does. > > When I look at Object>>#instVarAt: I see: > > > > "[...]Answer a fixed variable in an object. The numbering of the > variables > > corresponds to the named instance variables, followed by the indexed > > instance > > variables. Fail if the index is not an Integer or is not the index of a > > fixed variable[...]" > > > > Now in Pharo 7 when one does: > > > > #(iv1) instVarAt: 1, one gets #iv1. > > > > So the comment is wrong. > > > > The reason for this is that instVarAt: / instVarAt:put: should be > primitive > > 73/74, while they are in Pharo 173/174 (primitive slotAt:/slotAt:put:). > The > > slot primitive access pointer slots of objects, whichever inst var or > > variable fields. A good example would be: > > > > | t | > > t := #temp. > > [ t ] instVarAt: 4, one gets #temp > > > > So I have two solutions for this problem: > > 1) We change the instVarAt: / instVarAt:put: primitives comments to match > > the slotAt: / slotAt:put: behavior, and in Pharo instVarAt: / > instVarAt:put: > > means in factslotAt: / slotAt:put: . > > 2) We change the instVarAt: / instVarAt:put: primitives to primitive 73 > and > > 74, we introduce slotAt: / slotAt:put: with primitive 173/174 and we ask > > everyone to fix their code relying on instVarAt: / instVarAt:put: acting > as > > slotAt: / slotAt:put: > > > > What do you think ? > > > > Best, > > > > > > -- > > ClÃ©ment BÃ©ra > > Pharo consortium engineer > > https://clementbera.wordpress.com/ > > BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq > > -- ClÃ©ment BÃ©ra Pharo consortium engineer https://clementbera.wordpress.com/ BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq

Nov. 22, 2017

Re: [Pharo-dev] Bloc Naming Suggestion

by Nicolas Cellier

I see same kind of names in Opal exceptions Maybe the intention was to clearly distinguish Error from Warning (proceedable), but the hierarchy tells already. OCSemanticError OCStoreIntoReadOnlyVariableError could be just OCStoreIntoReadOnlyVariable OCStoreIntoSpecialVariableError -> OCStoreIntoSpecialVariable OCSemanticWarning OCShadowVariableWarning OCUndeclaredVariableWarning Note that removing the Warning suffix might lead to ambiguous names... OCUndeclaredVariable might be confused as being a Variable. So maybe OCVariableUndeclared or OCVariableIsUndeclared 2017-11-22 21:25 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > +1 > > > On Sun, Nov 19, 2017 at 4:34 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > I think itâs not a bad idea. > > > > Doru > > > >> On Nov 19, 2017, at 4:31 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > >> > >> What do you think about removing the #Attribute suffix from all the > >> BrTextAttribute subclasses? The names seem pretty long (e.g. > >> BrFontGenericFamilyAttribute, the longest) and IMHO `BrTextAttribute > >> subclass: #BrFontWeight` is adequately intention revealing. Thoughts? > >> > >> > >> > >> ----- > >> Cheers, > >> Sean > >> -- > >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837. > html > >> > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "Problem solving efficiency grows with the abstractness level of problem > understanding." > > > > > > > > > > > >

Nov. 22, 2017

Re: [Pharo-dev] [ANN] Willow 4.0.0 released!

by Stephane Ducasse

Hi stephan I totally agree. So much things to try and not enough time!!!! On Sun, Nov 19, 2017 at 1:48 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Op 16-11-2017 om 15:44 schreef Gabriel Cotelli: >> >> Hi, >> >> We're happy to announce the general availability of Willow and it's >> related projects in the Web Stack ecosystem hosted at >> https://github.com/ba-st/. >> >> Willow is a Web Interaction Library that eases the burden of creating >> AJAX-based web applications. The project goals are: > > > Interesting approach. Might be useful to use as a target for (QC)Magritte. > So much things to try out, and not enough time! > > Stephan > >

Nov. 22, 2017

Re: [Pharo-dev] Deploying using the latest minimal image of Pharo (6.1)

by Stephane Ducasse

Hi Gabriel This is cool. Thanks for sharing it with us. I really want an object responsible for deploying an app. :) Your effort is nice in that directory. Keep pushing Stef On Sun, Nov 19, 2017 at 1:33 AM, gabriel sor <despotadesdibujau(a)gmail.com> wrote: > Hi, > In in the past days, in the context of the Smalltalks 2017 conference, I > talked about my attempt to deploy on production using the minimal image > of Pharo . > My goal was prepare an inmutable or staless minimal image for deploy, > without sources nor changes files. > The results are exposed in this tutorial. > The size of the image is 16 MB and it has loaded Seaside. > Just I have a pendeing issue: the staless image but everything else is > done and working. >

Nov. 22, 2017