- Pharo-dev - lists.pharo.org

Final Reminder: Only 5 spots left for Camp Smalltalk! Raspberry PI kits to all who attend!
by Mariano Martinez Peck March 5, 2019

March 5, 2019

Hello All, There are 5 slots left for Camp Smalltalk Charlotte 2019 taking place at the end of this month. Now is the time to sign up if you are thinking of attending (see bottom for registration link). Camp Smalltalk is about community engagement and collaboration. There are a number of fantastic talks already lined up such as: Developing Smalltalk solutions running directly on ios / android mobile platforms (along with tooling) Live demo of @1MB remote-debuggable smalltalk images controlling peripherals attached to a Raspberry PI (ARM) In-depth look at large scale use of CMake/CTest/CDash for use with Smalltalk systems Smalltalk dialect portability solutions for the Smalltalk community (for use with GIT) We also have a fantastic Saturday evening social dinner planned on the boardwalk near the hotel. *As a special gift to attendees*, Instantiations will be providing everyone with their own Raspberry PI Zero Wifi devices with 8GB mini-sd card and power supply. Raspbian Linux with VA Smalltalk for ARM will be pre-installed. And if that isn't enough, each attendee will be receiving an open-source license for VA Smalltalk. This event is happening *March 29th â March 31st 2019* in Charlotte, North Carolina. Event details and registration info are available at the following link: Camp Smalltalk Charlotte 2019 <https://www.eventbrite.com/e/camp-smalltalk-charlotte-2019-tickets-52380940…> Hope to see you there! [image: IMG_0912.jpg] -- Mariano https://twitter.com/MartinezPeck http://marianopeck.wordpress.com

1 0

[Pharo 8.0] Build #114: 2736-Update-Epicea-to-Spec-changes
by ci-pharo-ci-jenkins2＠inria.fr March 5, 2019

March 5, 2019

There is a new Pharo build available! The status of the build #114 was: SUCCESS. The Pull Request #2747 was integrated: "2736-Update-Epicea-to-Spec-changes" Pull request url: https://github.com/pharo-project/pharo/pull/2747 Issue Url: https://pharo.fogbugz.com/f/cases/2736 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #152: 2699 - backport pharo-vcs/tonel bug fix
by ci-pharo-ci-jenkins2＠inria.fr March 5, 2019

March 5, 2019

There is a new Pharo build available! The status of the build #152 was: SUCCESS. The Pull Request #2700 was integrated: "2699 - backport pharo-vcs/tonel bug fix" Pull request url: https://github.com/pharo-project/pharo/pull/2700 Issue Url: https://pharo.fogbugz.com/f/cases/Pharo7.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

managing modification of class initialization methods
by Ben Coman March 5, 2019

March 5, 2019

In relation to developing sample solutions for an Exercism exercise, the following observation was made about class initialization... > class is initialized on load - and not when you modify it - so this can be very confusing for users My first thought was to wonder if Quality Assistant could track whether a class initialize method had been run after it was modified, and display alerts. Alternatively, I wonder if a reasonable pattern would be to couple class-side lazy initialization with a pragma to reset a variable when the method is saved... MyClass class >> referenceData <onSaveResetVariable: ReferenceData> ^ ReferenceData := ReferenceData ifNil: [ 'reference data' ] cheers -ben

6 11

[Pharo 7.0] Build #151: 2699 - backport pharo-vcs/tonel bug fix
by ci-pharo-ci-jenkins2＠inria.fr March 5, 2019

March 5, 2019

There is a new Pharo build available! The status of the build #151 was: SUCCESS. The Pull Request #2700 was integrated: "2699 - backport pharo-vcs/tonel bug fix" Pull request url: https://github.com/pharo-project/pharo/pull/2700 Issue Url: https://pharo.fogbugz.com/f/cases/Pharo7.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #150: 2699 - backport pharo-vcs/tonel bug fix
by ci-pharo-ci-jenkins2＠inria.fr March 5, 2019

March 5, 2019

There is a new Pharo build available! The status of the build #150 was: FAILURE. The Pull Request #2700 was integrated: "2699 - backport pharo-vcs/tonel bug fix" Pull request url: https://github.com/pharo-project/pharo/pull/2700 Issue Url: https://pharo.fogbugz.com/f/cases/Pharo7.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Weird FFI method redefinition in Pharo 6
by Eliot Miranda March 4, 2019

March 4, 2019

Hi All, I'm trying to debug remaining limitations in Image Segment support in Spur using a case provided by Max Leske. This is a pair of Pharo 6 images, one of which saves an image segment the other which loads it. Both use OSEnvironment>>getEnv: to access environment variables. The base definition of OSEnvironment>>getEnv: is !OSEnvironment methodsFor: 'accessing' stamp: 'auto 5/3/2016 10:31'! getEnv: arg1 "This method calls the Standard C Library getenv() function. The name of the argument (arg1) should fit decompiled version." ^ self ffiCall: #( String getenv (String arg1) ) module: LibC! ! but as I'm using the VM Simulator to debug the image segment issues I need to avoid the FFI, which isn't yet simulateable. So I redefine OSEnvironment>>getEnv: as follows, and then save and exit. !OSEnvironment methodsFor: 'accessing' stamp: 'EliotMiranda 02/27/2019 17:09'! getEnv: aByteStringOrByteArray "This method calls the Standard C Library getenv() function. The name of the argument (arg1) should fit decompiled version." <primitive: 'primitiveGetenv' module: '' error: ec> ec == #'bad argument' ifTrue: [aByteStringOrByteArray isString ifFalse: [^self getEnv: aByteStringOrByteArray asString]]. self primitiveFail! ! But, and here's the weird bit, when I start up the image, the new definition has been discarded and replaced by the original. WTF?!?! Why is this happening? How can I disable this? The only way that I've found I am able to save with a new version is by doing a Save As... to a new name. This is fine, but I find the current behavior extremely unhelpful. Is it a bug? If it is intended, whats the rationale? _,,,^..^,,,_ best, Eliot

2 4

GT FileReference inspector menu items
by Alistair Grant March 4, 2019

March 4, 2019

Hi Doru, I've been adding menu items to the AbstractFileReference Items tab by modifying AbstractFileReference>>gtInspectorItemsIn: This obviously isn't a good way to add menu items as different packages will over-write each other and was wondering if an extensible framework had been included in the new GT toolkit (e.g. using pragmas to define the menu items)? (or am I missing something in Pharo 8)? If not - consider this a feature request :-) P.S. The new String inspector as demoed in https://twitter.com/feenkcom/status/1102159122571710465 looks great! Being able to see the character easily is something I've wanted many times. Thanks! Alistair

2 2

[ANN] Pharo Consortium New Academic Member: USTH University of Science and Technology of Hanoi
by Marcus Denker March 4, 2019

March 4, 2019

The Pharo Consortium is very happy to announce that the USTH University of Science and Technology of Hanoi has joined the Consortium as an Academic Member. About - USTH University of Science and Technology of Hanoi: https://usth.edu.vn - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

1 0

Esteban's ChangeLog week of 25 February 2019
by estebanlm＠gmail.com March 4, 2019

March 4, 2019

Hello! This is my weekly ChangeLog, from 25 February 2019 to 3 March 2019. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=25/2/2019&to=3/3/2019 ChangeLog ========= 1 March 2019: ------------- * I have been working on introducing the concept of +Application+ to Spec2. An application is the entry point of... well, any application you will do with Spec2. It will contain information needed to make the application works in different contexts: 1) a theme 2) shared resources 3) the backend to use (Morphic) 4) access to standard dialogs, etc. (what now is found in UIManager). It is hard because it implies a lot of other refactors: * open/close of windows needs to pass through an application (to keep navigation working) * An application needs to be present on each window opened. * Windows needs to be the root of a presenter (and not just a holded variable in a ComposablePresenter) * Initialization of windows now is made by calling a method: #initializeWindow:, this was already added, but now we need to generalise it. * ... Anyway, this is a lot of work and is taking more than desirable :( 26 February 2019: ----------------- * Spec 2 day: 1) fix a bug in GridLayout: calculous of column width when columns is not homogeneous was bad because some morphs (labels, strings) needs to fit to contents (and it was not doing it). 2) Starting to introduce the concept of "Application": A window is not a good enough abstraction, we need to use also the concept of application (several windows interacting, sharing resources, theme, etc.). 25 February 2019: ----------------- * Today I made some advances in Spec2: 1) I worked on the transmissions mini-framework. The ability to make easy transmissions between components in Glamour was always something I liked it. So I did not want to lose it in the transition from Glamour to Spec2. I implemented a small layer on Spec presenters to be able to define input ports and output ports. That way you can define transmissions "glamour style", with full power of Spec behind. Someting like this is now possible: ---- packages := self newList displayBlock: #name. classes := self newList displayBlock: #name. self transmit from: packages; to: classes; transform: #definedClasses. ---- 2) Also, I added some functionality to allow to add arbitrary presenters to the new layouts. This is useful when doing forms, for example: you do not want to instantiate all the time a LabelPresenter to add a label. That way, you can now define things like this: ---- SpecGridLayout new columnHomogeneous: false; add: 'Name' at: 1@1; add: #nameTextInput at: 2@1; add: 'Host' at: 1@2; add: #hostTextInput at: 2@2; add: 'Port' at: 1@3; add: #portNumberInput at: 2@3; yourself ---- This will probably deserve a re-work later, but is already a lot better :) 3) I implementer a new type of presenter: +ActionBarPresenter+. This is similar to a toolbar, but its purpose is to add some actions (something like the small button pad you see in macOS and others). Since they do not serve same purpose, usability is not always the same and then they need to be separated. cheers! Esteban

2 1