- Pharo-dev - lists.pharo.org

Call for practical tutorials
by Stephane Ducasse April 24, 2017

April 24, 2017

Hi I love the tutorial of sven on getting a reddit app in 10 classes. https://medium.com/concerning-pharo/reddit-st-in-10-cool-pharo-classes-1b53… Sven I will turn it into a mini booklet. :) And I think that it is really important to have some more. (I'm finishing a new book and the TinyBlog web app and after I want to focus on Magritte. So my plate is really full ;( and not time to learn extra stuff). I was looking at the following https://www.codementor.io/classes/build-whatsapp-messenger-clone-react?utm_… and I would love to get something in this vein for Pharo. Does anybody want to do something in that direction? Stef

1 0

confused about hanging pointer
by Ben Coman April 24, 2017

April 24, 2017

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

2 1

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

April 23, 2017

************************************************************************************ 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

1 0

#renameTo: and #moveTo:
by Alistair Grant April 23, 2017

April 23, 2017

Hi All, While recently running the test suite I've been getting failures in FileLocatorTest>>testMoveTo if the working directory when the test is run is on a different unix file system to the user's home directory. The failing primitive is 'primitiveFileRename' in module 'FilePlugin', which calls rename(), which is presumably part of libc - I didn't chase it back through the C code. libc rename() requires the source and destination filenames to be on the same file system. This has been discussed multiple times before: https://pharo.fogbugz.com/f/cases/13957/Add-exception-for-cross-volume-fold… https://pharo.fogbugz.com/f/cases/12992/Cannot-move-files-to-another-volume… https://pharo.fogbugz.com/f/cases/12965/Cannot-moveTo-FileLocator Issue 12965 is even supposed to include a fix, although when I searched through the slice I couldn't find anything that actually looked like a fix. As Nicolai suggested in 12965, the obvious solution is to implement move as copy+delete. It looks like there isn't an easy way to check whether the two files are on the same unix file system, so presumably it would be implemented as try to rename, and if that fails, try to copy and delete. Is there a reason not to propose this as a patch? Thanks, Alistair

3 7

GSOC Mentors - We need you.
by Serge Stinckwich April 22, 2017

April 22, 2017

Dear mentors, we are currently reviewing all the students proposals. Please join the #gsoc-planning on Discord for giving your insights about the students. The deadline for the final selection will be Monday 24th 6pm CEST. As a reminder, we have 5 slots given by Google this year. Regards, -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

1 0

Help browser topic ordering
by Ben Coman April 22, 2017

April 22, 2017

What is it that defines the ordering of topics in the help browser? I see slice 19963 added a "Travis Integration" topic into build 60468 http://forum.world.st/pharo-project-pharo-core-7bde98-60468-td4942945.html and its ended up at the top of the list above "Welcome", but I determine from the slice or other existing help topics where the order is defined? cheers -ben

2 1

DarkTheme - tool bar icon color inconsistent
by Ben Coman April 22, 2017

April 22, 2017

n the previous white theme, toolbar icons matched the colour of their text. This makes a lot sense and is pleasant. In the dark theme, there is no correlation. Is this oversight or deliberate intent? It jars my senses. https://pharo.fogbugz.com/f/cases/19973/DarkTheme-tool-bar-icons cheers -ben

2 1

Order of evaluation bug with in lined to:do: in both Opal and Squeak compilers.
by Eliot Miranda April 22, 2017

April 22, 2017

Hi All, just stumbled across a bytecode compiler bug that's in both the Squeak compiler and the Opal compiler. I'm told by ClÃ©ment that Opal mimics the bug to avoid crashing legacy code. So there may be places that depend on this bug. It would be good to eliminate the dependencies and the bug. For illustration look at the to:do: loop in the ifNil: arm in Context>>privRefresh: Context>>privRefresh "Reinitialize the receiver so that it is in the state it was at its creation." closureOrNil ifNotNil: [pc := closureOrNil startpc. self stackp: closureOrNil numArgs + closureOrNil numCopiedValues. 1 to: closureOrNil numCopiedValues do: [:i | self tempAt: closureOrNil numArgs + i put: (closureOrNil at: i)]] ifNil: [pc := method initialPC. self stackp: method numTemps. method numArgs+1 to: method numTemps do: [:i | self tempAt: i put: nil]] This should evaluate method numArgs + 1 then method numTemps. If it were written as a non-in-lined (method numArgs+1 to: method numTemps) do: [:i| self tempAt: i put: nil] then the [self tempAt: i put: nil] block would be created next. But the bytecode for the inlined version is self stackp: method numTemps. 63 <70> self 64 <84 40 03> pushRcvr: 3 67 <D6> send: numTemps 68 <E1> send: stackp: 69 <87> pop iLimit := method numTemps 70 <84 40 03> pushRcvr: 3 73 <D6> send: numTemps 74 <69> popIntoTemp: 1 i := method numArgs + 1 75 <84 40 03> pushRcvr: 3 78 <D2> send: numArgs 79 <76> pushConstant: 1 80 <B0> send: + 81 <81 40> storeIntoTemp: 0 (squeak) <69> popIntoTemp: 1 (pharo) 83 <10> pushTemp: 0 84 <11> pushTemp: 1 85 <B4> send: <= 86 <AC 0B> jumpFalse: 99 There is a second bug in the Squeak bytecode; storeIntoTemp: is used to load i whereas it should be popIntoTemp:. It was this second bug that alerted me to the order-of-evaluation bug. _,,,^..^,,,_ best, Eliot

3 3

Implementers code pane undo goes too far
by Ben Coman April 22, 2017

April 22, 2017

I hit some strange behaviour... Setup... 1. In playground, type... green 2. Open implementers on it 3. Select the second line "Color class(defaults) green" 4. Click in the code pane Observe that "green" is pre-selected and the cursor is flashing at end of first line 5. Start typing... self halt. Observe the method name is overwritten Problem... 6. Hit CTRL-Z three times. Observe the instance side #green is displayed rather than the class side. Auxiliary... Now save it and work out how to get out of the mess (pretending you didn't notice what had happened) https://pharo.fogbugz.com/f/cases/19972/Implementers-code-pane-undo-goes-to… cheers -ben

2 2

do we "how to use Announcements" somewhere
by Peter Uhnak April 21, 2017

April 21, 2017

I was just explaining how Announcer/Announcements work to somebody because I couldn't find any online resource, but I thought I saw it somewhere. Do we have it explained in some book? Peter

4 4