June 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] some small rubric issues

by stepharo

Thanks Nicolai Franck is quite bold to work on Nautilus and PluggableTextMorph :) We thank alain for his continuous support and help. But indeed we break things from time to time. Stef Le 25/6/15 16:19, Nicolai Hess a Ã©crit : > > Please con someone look at these issues, they are easy to fix (i > think), but I can not > write to rubrics repository > > 15273 <https://pharo.fogbugz.com/default.asp?15273> > Issue regarding print block in the playground window > 15312 <https://pharo.fogbugz.com/default.asp?15312> > Wrong position for completion menu in Rubric/Playground > 15663 <https://pharo.fogbugz.com/default.asp?15663> > styling in spotter preview broken > > thanks, > nicolai >

June 25, 2015

Giving skype lectures to cameron students

by stepharo

Hi we are giving some skype lectures to cameron students with damien. A fun experience, because the network is so bad that I cannot demo Pharo interactively. But I'm learning from it. Stef

June 25, 2015

Re: [Pharo-dev] some small rubric issues

by Esteban Lorenzano

> On 25 Jun 2015, at 16:19, Nicolai Hess <nicolaihess(a)web.de> wrote: > > Please con someone look at these issues, they are easy to fix (i think), but I can not > write to rubrics repository > yes you can. I just added you to Pharo team (no idea why you werenât there before) :) Esteban > 15273 <https://pharo.fogbugz.com/default.asp?15273> > Issue regarding print block in the playground window > 15312 <https://pharo.fogbugz.com/default.asp?15312> > Wrong position for completion menu in Rubric/Playground > 15663 <https://pharo.fogbugz.com/default.asp?15663> > styling in spotter preview broken > > thanks, > nicolai >

June 25, 2015

Re: [Pharo-dev] [Pharo-users] the importance of your story

by Serge Stinckwich

On Thu, Jun 25, 2015 at 3:56 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Thanks Doru for your inspiring words. > > Recently I had a âcoup de bluesâ because Pharo is completely absent from the > StackOverflow and Github scene. I feel it is like a researcher without a > webpage. Without a webpage, he does not exist. I also have this "coup de blues" from time to time for similar reason and because I have to fight sometimes to defend this choice. Thank you Doru for giving us inspiration for the future. I will come to ESUG this year. This is usually a good place to have a boost for several months after. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

June 25, 2015

DNS level changes for smalltalkhub.com Friday

by Marcus Denker

Hello, Friday morning we will do some DNS level changes for smalltalkhub.com. This should normally have no impact on the server, as the new DNS server will point to the same IP as the old. Marcus

June 25, 2015

Re: [Pharo-dev] Detecting the context/producer of code change announcements

by Martin Dias

I'm going in the direction of the Job. I started by doing some clean up in the implementation, together with Guille in a useful pair-programming session. The issue needs approval for integration: https://pharo.fogbugz.com/f/cases/15833/Remove-Notifications-from-Job-imple… MartÃn On Wed, Jun 17, 2015 at 7:03 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > Thanks for the discussion. I'm considering the ideas; I want to propose > something concrete very soon. > > If I understand well, the two positions are: > > * to extend Job with a 'description' object; > * to extend system announcements, so they know their 'parent' announcement; > > in both cases, the subscriber can lookup into the hierarchy of "tasks" > that produced an announcement. > > MartÃn > > On Sat, Jun 13, 2015 at 8:06 AM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> Hi Eliot, >> >> Le 13/06/2015 06:54, Eliot Miranda a Ã©crit : >> >>> Hi Thierry, >>> >>> On Jun 11, 2015, at 8:16 AM, Thierry Goubier <thierry.goubier(a)gmail.com >>> <mailto:thierry.goubier@gmail.com>> wrote: >>> >>> >>>> >>>> 2015-06-11 16:49 GMT+02:00 Ben Coman <btc(a)openinworld.com >>>> <mailto:btc@openinworld.com>>: >>>> >>>> >>>> Just a *very* divergent thought that I'm not sure is a good idea... >>>> maybe the parent announcement could hold the announcer of its >>>> children. >>>> >>>> >>>> The problem is then that all tools which are not interested in the >>>> parent announcement because they only deal with the low level stuff >>>> (system browser, RPackageOrganizer and friends: MessageList, Spotter, >>>> Critics browser, Finder, Versionner, Inspector, anything which listen >>>> to a code change basically) have to still listen to the parent and, on >>>> reception, subscribe to the low-level announcement, and then >>>> unsubscribe on the parent end announcement. >>>> >>> >>> It seems to me that with Ben's suggestion there need only be the >>> low-level announcement, and that subscribers interested in the >>> higher-level context could fetch it by asking the announcement for its >>> context. >>> >> >> I reacted to the fact Ben said announcer, not announcement... >> Reregistering announcers in code-aware tools is not something you do often >> [1] >> >> One aspect I forgot is the performance issues linked with announcements. >> On package loads, a huge number of announcements is generated, and just >> simple things like tracking those to refresh the display of a system >> browser needs to be optimised to avoid degrading performance significantly. >> >> Thierry >> >> [1] >> https://github.com/ThierryGoubier/AltBrowser/blob/pharo5/Alt-Browser.packag… >> >> >

June 25, 2015

Re: [Pharo-dev] GT needs love

by Nicolai Hess

Thanks. Am 24.06.2015 9:37 nachm. schrieb "stepharo" <stepharo(a)free.fr>: > thanks andrei > > > Le 24/6/15 15:38, Andrei Chis a Ã©crit : > > I'll have a look a bit later today > > > Cheers, > Andrei > > On Wed, Jun 24, 2015 at 3:33 PM, stepharo <stepharo(a)free.fr> wrote: > >> >> >> >> Hi guys >> >> Nicolas proposed several fixes of GT and we are waiting that someone with >> a bit of knowledge integrate them in GT. >> I can do it but I would prefer that somebody with knowledge takes 10 min >> to do it. >> >> Stef >> > > >

June 25, 2015

some small rubric issues

by Nicolai Hess

Please con someone look at these issues, they are easy to fix (i think), but I can not write to rubrics repository 15273 <https://pharo.fogbugz.com/default.asp?15273> Issue regarding print block in the playground window 15312 <https://pharo.fogbugz.com/default.asp?15312> Wrong position for completion menu in Rubric/Playground 15663 <https://pharo.fogbugz.com/default.asp?15663> styling in spotter preview broken thanks, nicolai

June 25, 2015

Re: [Pharo-dev] [Pharo-users] the importance of your story

by Max Leske

> On 25 Jun 2015, at 15:56, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Thanks Doru for your inspiring words. > > Recently I had a âcoup de bluesâ because Pharo is completely absent from the StackOverflow and Github scene. It might not have âmuch trafficâ on SO but the number of posts per week has grown *significantly*. A lot of the questions seem to com from GSoC students of CS students from around the world which is pretty cool actually. > I feel it is like a researcher without a webpage. Without a webpage, he does not exist. And here I thought researchers defined themselves through the number of publications :) > > But I have faith things will soon change... > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Jun 25, 2015, at 8:39 AM, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >> >> Hi, >> >> I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". While the talk is less technical, I did exemplified the message by demoing Spotter in comparison with the search support from Eclipse. >> >> There are several things I would like to emphasize. >> >> I compared our solution with an "industry standard" one. We often think our system as being niche and perhaps not mature enough. We need to change that perception about our work. We build state of the art. >> >> One thing that I did not mention explicitly in the talk is the size of the implementation. The Spotter implementation is 3500 lines of code -- and that it is so large because it currently comes with its own widgets. Furthermore, the extensions average 8 lines per custom processor (including the method header and the pragma). This is orders of magnitude smaller than what is typically out there, and it is precisely the reason why we can compete even if we are fewer. >> >> But, to get out there and compete we have to set that high goal for ourselves. For example, with GT we do not want to compete. We want to outcompete. So can you. >> >> While details are important, high goals require us to get away from those details. Only polishing details will tend to limit you to incremental improvements. We need to jump from time to time. But, these jumps are hard. On the one hand, it is hard to find the right jump and convince people to jump with you. On the other hand, they are hard to predict. For example, Spotter would have not been predictable one year ago. >> >> Yet, dry goals are not enough to keep us going. We need stories that make us dream. And the beauty is that Pharo breaths such a story. We should not limit ourselves to that story only. For example, with GT we want to reinvent the developer experience by making the developer be able to mold visual tools to her context because that is the only effective way to build sustainable systems. This little point of view will turn the IDE upside down, and this is only possible in a system like Pharo. >> >> Choose your high goal and tell its story through the system that you build. And remember that Pharo already offers a beautiful story to start from. >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> >> "Every thing has its own flow" >

June 25, 2015

Re: [Pharo-dev] [Pharo-users] the importance of your story

by Alexandre Bergel

Thanks Doru for your inspiring words. Recently I had a âcoup de bluesâ because Pharo is completely absent from the StackOverflow and Github scene. I feel it is like a researcher without a webpage. Without a webpage, he does not exist. But I have faith things will soon change... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jun 25, 2015, at 8:39 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". While the talk is less technical, I did exemplified the message by demoing Spotter in comparison with the search support from Eclipse. > > There are several things I would like to emphasize. > > I compared our solution with an "industry standard" one. We often think our system as being niche and perhaps not mature enough. We need to change that perception about our work. We build state of the art. > > One thing that I did not mention explicitly in the talk is the size of the implementation. The Spotter implementation is 3500 lines of code -- and that it is so large because it currently comes with its own widgets. Furthermore, the extensions average 8 lines per custom processor (including the method header and the pragma). This is orders of magnitude smaller than what is typically out there, and it is precisely the reason why we can compete even if we are fewer. > > But, to get out there and compete we have to set that high goal for ourselves. For example, with GT we do not want to compete. We want to outcompete. So can you. > > While details are important, high goals require us to get away from those details. Only polishing details will tend to limit you to incremental improvements. We need to jump from time to time. But, these jumps are hard. On the one hand, it is hard to find the right jump and convince people to jump with you. On the other hand, they are hard to predict. For example, Spotter would have not been predictable one year ago. > > Yet, dry goals are not enough to keep us going. We need stories that make us dream. And the beauty is that Pharo breaths such a story. We should not limit ourselves to that story only. For example, with GT we want to reinvent the developer experience by making the developer be able to mold visual tools to her context because that is the only effective way to build sustainable systems. This little point of view will turn the IDE upside down, and this is only possible in a system like Pharo. > > Choose your high goal and tell its story through the system that you build. And remember that Pharo already offers a beautiful story to start from. > > Cheers, > Doru > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow"

June 25, 2015