April 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo 6 screenshot

by Tudor Girba

:) Doru > On Apr 24, 2017, at 1:39 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> The problem is that we need a proper Roassal integration without the white background :). Otherwise it looks not so nice. > > It is on the wayâ¦ > Give us a couple of hours :-) > > Alexandre > > > >> >> Doru >> >> >>> On Apr 24, 2017, at 10:14 AM, phil(a)highoctane.be wrote: >>> >>> Nice, I'd put some more Roassal things, like Sunburst >>> >>> >>> On Mon, Apr 24, 2017 at 9:14 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> I like it ! >>> >>>> On 24 Apr 2017, at 08:58, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >>>> >>>> Hi, >>>> >>>> I tried to prepare some "geeky" screenshot for Pharo 6 announcements and advertisements. >>>> >>>> https://goo.gl/photos/NF5EC6dCinXRWosA9 >>>> >>>> -- Pavel >>> >>> >>> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> âSoftware has no shape. Actually, it has no one shape. It has many." >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. -- www.tudorgirba.com www.feenk.com "Beauty is where we see it."

April 24, 2017

Re: [Pharo-dev] Pharo 6 screenshot

by Alexandre Bergel

> The problem is that we need a proper Roassal integration without the white background :). Otherwise it looks not so nice. It is on the wayâ¦ Give us a couple of hours :-) Alexandre > > Doru > > >> On Apr 24, 2017, at 10:14 AM, phil(a)highoctane.be wrote: >> >> Nice, I'd put some more Roassal things, like Sunburst >> >> >> On Mon, Apr 24, 2017 at 9:14 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> I like it ! >> >>> On 24 Apr 2017, at 08:58, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >>> >>> Hi, >>> >>> I tried to prepare some "geeky" screenshot for Pharo 6 announcements and advertisements. >>> >>> https://goo.gl/photos/NF5EC6dCinXRWosA9 >>> >>> -- Pavel >> >> >> > > -- > www.tudorgirba.com > www.feenk.com > > âSoftware has no shape. Actually, it has no one shape. It has many." > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 24, 2017

Pharo Site showing Error 502 - Bad gateway

by Tim Mackinnon

Hi guys - just noticed the Pharo site is showing: Error 502 Ray ID: 35488f38618f69ef â¢ 2017-04-24 11:00:32 UTC Bad gateway Looks like some cloudflare configuration issue? But it also means the Pharo days page is not available. I also noticed the Pharo site isnât serving with https as well? Given how easy it is to get a free cert - should this be changed as well? Tim

April 24, 2017

Re: [Pharo-dev] Pharo 6 screenshot

by Tudor Girba

The problem is that we need a proper Roassal integration without the white background :). Otherwise it looks not so nice. Doru > On Apr 24, 2017, at 10:14 AM, phil(a)highoctane.be wrote: > > Nice, I'd put some more Roassal things, like Sunburst > > > On Mon, Apr 24, 2017 at 9:14 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I like it ! > > > On 24 Apr 2017, at 08:58, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > > Hi, > > > > I tried to prepare some "geeky" screenshot for Pharo 6 announcements and advertisements. > > > > https://goo.gl/photos/NF5EC6dCinXRWosA9 > > > > -- Pavel > > > -- www.tudorgirba.com www.feenk.com âSoftware has no shape. Actually, it has no one shape. It has many."

April 24, 2017

Re: [Pharo-dev] confused about hanging pointer

by Henrik Nergaard

Hi Ben, --------------- Smalltalk garbageCollect. Pharo3DarkTheme allInstances first pointersTo collect: [ :each | each class ] "{ClassVariable. Context. Context. Context. Context. Context. Context. Context. Context. Context. Context}" --------------- >I can't understand where in that method a pointer/reference could remain held. ??? The references are held in contexts created by block closures like "[aSystemWindow closeBoxHit]". These contexts are created because the block closure uses a variable from the outer scope. The block closures in all the #create...BoxFor: methods is not exectued at once but used as callbacks for buttons and is why you can still see references to an old theme, because the callback is still the same in these buttons. [aSystemWindow closeBoxHit] could be rewritten to (MessageSend reciever: aSystemWindow selector: #closeBoxHit ) making it easier to GC the old theme when themes are changed. Best regards, Henrik ________________________________ Fra: Pharo-dev <pharo-dev-bounces(a)lists.pharo.org> pÃ¥ vegne av Ben Coman <btc(a)openinworld.com> Sendt: 24. april 2017 04:50:25 Til: Pharo Development List Emne: [Pharo-dev] confused about hanging pointer Background: I'm looking into https://pharo.fogbugz.com/f/cases/19973/DarkTheme-tool-bar-icons Take for example UITheme>> windowMaximizeForm "Answer the form to use for the maximize button of a window." "self haltOnce." ^self forms at: #windowMaximize ifAbsent: [ "self haltOnce" Form extent: 10@10 depth: Display depth] If I uncomment the top haltOnce, and then right-click on an item in the bottom toolbar, a debug window shows up as expected. After changing the theme, I would expect "forms" to be nil. But uncommenting only the second haltOnce inside the block, then changing "System > Settings > Appearance > User interface theme" to white then back to dark, and then right-click on an item in the bottom toolbar, does *not* produce a debug window. Now upon booting a freshly downloaded 60469 image... Pharo3DarkTheme allInstances size "==> 1" then after changing System > Settings > Appearance > User interface theme to white then back to dark... Pharo3DarkTheme allInstances size "==> 2" Its almost like changing themes creating a new instance of Pharo3DarkTheme, but it doesn't get installed in the right places. Preliminary check... "Booted fresh 60469 image. Opened a playground." Pharo3DarkTheme allInstances collect: [:i | i identityHash -> i pointersTo size]. "{748241152->8}" "Opened System > Settings" Pharo3DarkTheme allInstances collect: [:i | i identityHash -> i pointersTo size]. "{748241152->14}" "1. Changed Appearance > User interface theme to white then back to dark" Pharo3DarkTheme allInstances collect: [:i | i identityHash -> i pointersTo size]. "{748241152->6. 954809088->12}" "2. Changed Appearance > User interface theme to white then back to dark" Pharo3DarkTheme allInstances collect: [:i | i identityHash -> i pointersTo size]. "{748241152->6. 954809088->1. 721110784->12}" "3. Changed Appearance > User interface theme to white then back to dark" Pharo3DarkTheme allInstances collect: [:i | i identityHash -> i pointersTo size]. "{748241152->6. 954809088->1. 721110784->1. 127158784->12}" "Closed settings window." Smalltalk garbageCollect. Pharo3DarkTheme allInstances collect: [:i | i identityHash -> i pointersTo size]. "{748241152->6. 127158784->12}" Pharo3DarkTheme allInstances first pointersTo inspect. Pharo3DarkTheme(UITheme)>>createCloseBoxFor: Pharo3DarkTheme(UIThemeWatery)>>createCollapseBoxFor: Pharo3DarkTheme(UIThemeWatery)>>createExpandBoxFor: Pharo3DarkTheme(UITheme)>>createCloseBoxFor: Pharo3DarkTheme>>createMenuBoxFor: For a moment I was confused, by seeing only five items, but of course the sixth was from the block variable "i". Question: What I really am confused about is, for example in... UITheme>>createCloseBoxFor: aSystemWindow "Answer a button for closing the window." ^(self newCloseControlIn: aSystemWindow for: aSystemWindow action: [aSystemWindow closeBoxHit] help: 'Close this window' translated) extent: aSystemWindow boxExtent I can't understand where in that method a pointer/reference could remain held. ??? cheers -ben

April 24, 2017

Re: [Pharo-dev] Pharo 6 screenshot

by phil＠highoctane.be

Nice, I'd put some more Roassal things, like Sunburst On Mon, Apr 24, 2017 at 9:14 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I like it ! > > > On 24 Apr 2017, at 08:58, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > > > Hi, > > > > I tried to prepare some "geeky" screenshot for Pharo 6 announcements and > advertisements. > > > > https://goo.gl/photos/NF5EC6dCinXRWosA9 > > > > -- Pavel > > >

April 24, 2017

Re: [Pharo-dev] Pharo 6 screenshot

by Sven Van Caekenberghe

I like it ! > On 24 Apr 2017, at 08:58, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi, > > I tried to prepare some "geeky" screenshot for Pharo 6 announcements and advertisements. > > https://goo.gl/photos/NF5EC6dCinXRWosA9 > > -- Pavel

April 24, 2017

Pharo 6 screenshot

by Pavel Krivanek

Hi, I tried to prepare some "geeky" screenshot for Pharo 6 announcements and advertisements. https://goo.gl/photos/NF5EC6dCinXRWosA9 -- Pavel

April 24, 2017

confused about hanging pointer

by Ben Coman

Background: I'm looking into https://pharo.fogbugz.com/f/cases/19973/DarkTheme-tool-bar-icons Take for example UITheme>> windowMaximizeForm "Answer the form to use for the maximize button of a window." "self haltOnce." ^self forms at: #windowMaximize ifAbsent: [ "self haltOnce" Form extent: 10@10 depth: Display depth] If I uncomment the top haltOnce, and then right-click on an item in the bottom toolbar, a debug window shows up as expected. After changing the theme, I would expect "forms" to be nil. But uncommenting only the second haltOnce inside the block, then changing "System > Settings > Appearance > User interface theme" to white then back to dark, and then right-click on an item in the bottom toolbar, does *not* produce a debug window. Now upon booting a freshly downloaded 60469 image... Pharo3DarkTheme allInstances size "==> 1" then after changing System > Settings > Appearance > User interface theme to white then back to dark... Pharo3DarkTheme allInstances size "==> 2" Its almost like changing themes creating a new instance of Pharo3DarkTheme, but it doesn't get installed in the right places. Preliminary check... "Booted fresh 60469 image. Opened a playground." Pharo3DarkTheme allInstances collect: [:i | i identityHash -> i pointersTo size]. "{748241152->8}" "Opened System > Settings" Pharo3DarkTheme allInstances collect: [:i | i identityHash -> i pointersTo size]. "{748241152->14}" "1. Changed Appearance > User interface theme to white then back to dark" Pharo3DarkTheme allInstances collect: [:i | i identityHash -> i pointersTo size]. "{748241152->6. 954809088->12}" "2. Changed Appearance > User interface theme to white then back to dark" Pharo3DarkTheme allInstances collect: [:i | i identityHash -> i pointersTo size]. "{748241152->6. 954809088->1. 721110784->12}" "3. Changed Appearance > User interface theme to white then back to dark" Pharo3DarkTheme allInstances collect: [:i | i identityHash -> i pointersTo size]. "{748241152->6. 954809088->1. 721110784->1. 127158784->12}" "Closed settings window." Smalltalk garbageCollect. Pharo3DarkTheme allInstances collect: [:i | i identityHash -> i pointersTo size]. "{748241152->6. 127158784->12}" Pharo3DarkTheme allInstances first pointersTo inspect. Pharo3DarkTheme(UITheme)>>createCloseBoxFor: Pharo3DarkTheme(UIThemeWatery)>>createCollapseBoxFor: Pharo3DarkTheme(UIThemeWatery)>>createExpandBoxFor: Pharo3DarkTheme(UITheme)>>createCloseBoxFor: Pharo3DarkTheme>>createMenuBoxFor: For a moment I was confused, by seeing only five items, but of course the sixth was from the block variable "i". Question: What I really am confused about is, for example in... UITheme>>createCloseBoxFor: aSystemWindow "Answer a button for closing the window." ^(self newCloseControlIn: aSystemWindow for: aSystemWindow action: [aSystemWindow closeBoxHit] help: 'Close this window' translated) extent: aSystemWindow boxExtent I can't understand where in that method a pointer/reference could remain held. ??? cheers -ben

April 24, 2017

CfP: DLS 2017 - 13th Dynamic Languages Symposium, co-located with SPLASH 2017, October 24, Vancouver, British Columbia, Canada

by Nick Papoylias

************************************************************************************ CALL FOR PAPERS DLS 2017 - 13th Dynamic Languages Symposium Co-located with SPLASH 2017, October 24, Vancouver, British Columbia, Canada http://www.dynamic-languages-symposium.org/dls-17/index.html ************************************************************************************ >From Lisp, Snobol, and Smalltalk to Python, Racket, and Javascript, Dynamic Languages have been playing a fundamental role both in programming research and practice. The 13th Dynamic Languages Symposium (DLS) at SPLASH 2017 is the premier forum for researchers and practitioners to share research and experience on all aspects on Dynamic Languages. DLS 2017 invites high quality papers reporting original research and experience related to the design, implementation, and applications of dynamic languages. Areas of interest include but are not limited to: * Innovative language features * Innovative implementation techniques * Innovative applications * Development environments and tools * Experience reports and case studies * Domain-oriented programming * Very late binding, dynamic composition, and run-time adaptation * Reflection and meta-programming * Software evolution * Language symbiosis and multi-paradigm languages * Dynamic optimization * JIT compilation * Soft/optional/gradual typing * Hardware support * Educational approaches and perspectives * Semantics of dynamic languages * Frameworks and languages for the Cloud and the IoT Submissions must not have been published previously nor being under review at other events. Research papers should describe work that advances the current state of the art. Experience papers should be of broad interest and should describe insights gained from substantive practical applications. The program committee will evaluate each contributed paper based on its relevance, significance, clarity, and originality. Papers are to be submitted electronically at https://dls17.hotcrp.com/ in PDF format. Submissions must be in the ACM SIGPLAN Conference acmart Format, 10 point font, and should not exceed 12 pages. Please see full details in the instructions for authors available at: http://conf.researchr.org/track/dls-2017/dls-2017#Instructions-for-Authors DLS 2017 will run a two-phase reviewing process to help authors make their final papers the best that they can be. Accepted papers will be published in the ACM Digital Library and will be freely available for one month, starting two weeks before the event. Important dates --------------- * Friday May 26, 2017: abstract submission (strict, 23:59 AoE or UTC-12h) * Friday June 2, 2017: paper submission (strict, 23:59 AoE or UTC-12h) * Friday July 14, 2017: first phase notification * Friday August 11, 2017: final notification * Monday August 28, 2017: camera ready * Tuesday October 24, 2017: DLS AUTHORS TAKE NOTE: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of your conference. The official publication date affects the deadline for any patent filings related to published work. Program chair ------------- Davide Ancona, DIBRIS, University of Genova, Italy davide.ancona(a)unige.it Program committee ----------------- * Guillaume Baudart, Ãcole normale supÃ©rieure, France * Alexandre Bergel, University of Chile, Chile * Lorenzo Bettini, Dipartimento di Statistica, Informatica, Applicazioni âGiuseppe Parentiâ (DISIA), Italy * Carl Friedrich Bolz, Germany * Erik Ernst, Google Inc., Denmark * Marc Feeley, UniversitÃ© de MontrÃ©al, Canada * Matthew Flatt, University of Utah, United States * Paola Giannini, UniversitÃ del Piemonte Orientale, Italy * Robert Hirschfeld, HPI, Germany * Roberto Ierusalimschy, PUC-Rio, Brazil * Crista Lopes, University of California, USA * Scott Moore, Harvard University, USA * Nick Papoulias, IRD, UPMC, France * Sukyoung Ryu, KAIST, Korea, South * Chris Seaton, Oracle Labs, United Kingdom * Manuel Serrano, Inria, France * Zehra Sura, IBM Research, United States * Jan Vitek, Northeastern University, Switzerland

April 23, 2017