November 2018 - Pharo-users

Spec + Graphics?
by Dan Wilczak Dec. 1, 2018

Dec. 1, 2018

Hi, I'm interested in using Pharo to create a simulation with animated 2-D graphical output. The user can start/stop the simulation, change display modes, zoom in and out, and change various settings during operation. That means that, in addition to a graphical pane, I need a menu bar or maybe a panel of buttons which create popup windows. Can I use Spec for such a thing? I don't see any way to embed a graphical pane in a Spec application. The Spec examples don't include one either. Secondly, if it is possible to use Spec, what would you recommend for the graphics? Bloc and Sparta look very appealing but aren't officially released yet. The long-term futures of the other options aren't clear to me. Thanks, Dan Wilczak -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

2 1

subpackages in P7
by Roelof Wobben Dec. 1, 2018

Dec. 1, 2018

Hello, Right now I have three seperate packages. Project Project-test Project-Actions Is it possible in P7 to have something like this Project ---Â Â Tests ----Â Actions and if so, how to I make it work,

4 5

Loading Metacello with Seaside
by Vitor Medina Cruz Nov. 30, 2018

Nov. 30, 2018

Hello! WIndows 10 here with Pharo 7 32 bits. Here is my baseline: baseline: spec > > <baseline> > > spec for: #'common' do: [ > spec blessing: #'baseline'; > repository: 'gitlab://vitormcruz/employees:master/pharo/'; > > project: 'Magritte3' with: [ spec repository: > 'github://magritte-metamodel/magritte:v3.5.3/source'; > className: > 'ConfigurationOfMagritte3'; > loads: #(Seaside Core) > ]; > > package: 'Employees' with: [ spec requires: #('Magritte3'). > ]; > > group: 'default' with: #('core'); > group: 'core' with: #('Employees') When I execute: Metacello new baseline: #Employees; > repository: > 'gitlab://vitormcruz/employees:master/pharo/'; load: #(core) > I got: "project group, or package named: 'Seaside-Pharo-Development' not found > when used in requires: or includes: field of package: > 'Seaside-Tests-Pharo-Development' for version: baseline of > BaselineOfSeaside3." > It seems there is a problem with Magrite ConfigurationOf, am I correct? Some general information: 1- Using https://github.com/magritte-metamodel/magritte instead /magritte:v3.5.3/ of 'github://magritte-metamodel/magritte:v3.5.3/source don't work; 2- You must provide className otherwise it does no work, even if docs says itis not needed; 3- Metacello fail in ways it is hard to understand what happened; 4- On Pharo 64bits, Iceberg commit fails. <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Livre de vÃrus. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…>. <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2 6

Re: [Pharo-users] [squeak-dev] Named serial port bug and how to contribute
by Nicolai Hess Nov. 30, 2018

Nov. 30, 2018

Good to know! Am Fr., 30. Nov. 2018 um 02:25 Uhr schrieb Ricardo Moran < richi.moran(a)gmail.com>: > Hi, > > I think I found a bug with the named serial ports in windows. > I can open a named port without problem the first time but if I close it > and try to open it again it fails until I restart the image. This doesn't > happen with numeric ports. I could reproduce this bug in both Squeak5.2 and > Pharo6.1 (both using windows 8.1). > > I think the problem is that SerialPort>>#primClosePortByName: calls the > "primitiveSerialPortCloseByName" but I couldn't find this primitive > anywhere in the SerialPlugin source ( > https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/src/plugins/Seri…) > So I'm guessing that the port is never properly closed. > > I added the missing primitive (find attached) and recompiled the vm, and > now it seems to work. So my question is: how can I contribute this small > fix? Should I commit to the VM Maker Inbox repository? > > Thanks, > Richo > >

2 1

UFFI and opaque(ish) types
by Alistair Grant Nov. 30, 2018

Nov. 30, 2018

How are opaque(ish) types normally handled in UFFI (or FFI)? E.g. if I want to use libstuff which defines the following structure: struct stuffstruct { typeA a; typeB b; } stufftype; I might know they're integers, but not the size, signed vs. unsigned, etc. The definitions of typeA and typeB are buried in multiple layers of header files, dependent on #if tests, can be different sizes on different platforms (e.g. Linux vs. MacOS), etc.? Is this documented somewhere? Thanks, Alistair

2 1

Lambda World 2018 - What FP can learn from Smalltalk by Aditya Siram
by Jimmie Houchin Nov. 30, 2018

Nov. 30, 2018

Hello, Interesting video using Pharo for presenting its points. https://www.youtube.com/watch?v=baxtyeFVn3w Wondering if anybody else has seen this video. What can be learned from this outside perspective. He is mostly positive about Pharo and is using it as an example of things he would like to see in his world. He does say that Pharo's GC is not good. Thoughts. Jimmie

7 6

Problems with Firmata & Arduino UNO Clone
by William L. Cleveland Nov. 29, 2018

Nov. 29, 2018

I have been unsuccessful in using an Arduino board with Pharo 6.1(32bit) and the Firmata package. The board is an Arduino Uno clone (ELEGOO UNO R3). The board appears to work fine with the Arduino IDE, which was tested with the BLINK program. The Standard Firmata Library appears to have been successfully uploaded to the board using the Arduino IDE. COM ports have been closed using SerialPort allInstancesDo: [:port|port close]. On Windows 10, SerialPort inspect shows that ports are closed. However, firmata := Firmata onPort: âCOM3â baudRate: 576000 failed due to failure to open COM3. The serial port name was obtained from the Arduino IDE Tools menu. The board choice was âArduino Unoâ. In MacOS 10.11.6, the same code generated a Cannot open comport message. Independently of Firmata, the following line of code SerialPort allInstancesDo: [:port| port close] generated the following error message: âInstance of BlockClosure did not understand #SerialPort. The same code worked fine in Windows. I am wondering if the SerialPort code in Pharo6.1 is sufficiently robust for a nonexpert programmer like myself, who only occasionally writes code for his own use. Previously, I wrote an application for a robotics project in 2008 using VisualWorks and the DLL&CConnect tool, which was quite successful. No more coding until just recently, when I started using Python. Would like to go back to Smalltalk if it is sufficiently robust. Any help would be appreciated. Lou Cleveland

4 3

[ANN] Teapot was moved to GitHub
by Attila Magyar Nov. 29, 2018

Nov. 29, 2018

Hi, I just want to let you know that the source code of Teapot was moved from Smalltalkhub to GitHub. The new repository is located at: https://github.com/zeroflag/teapot <https://github.com/zeroflag/teapot> Attila -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

5 6

Re: [Pharo-users] [Pharo-dev] [Ann] TaskIt v1.0
by Santiago Bragagnolo Nov. 29, 2018

Nov. 29, 2018

Hi Norbert! We don't have yet implemented any nor all combinations. I will add it to the list of things to do for next release. Looks like a simple and useful thing to have. (Or if you have already something I wouldn't mind to integrate it) Thanks. Santiago El jue., 29 de nov. de 2018 17:36, Norbert Hartl via Pharo-users < pharo-users(a)lists.pharo.org> escribiÃ³: > Great, thanks! > > Does TaskIt include implementations for combining futures such as the ALL > and the ANY futures which resolve either when all or one future resolves? > From the documentation it looks that rather not. > > Norbert > > > Am 29.11.2018 um 15:29 schrieb Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com>: > > Hi everybody :). > > I am happy to announce TaskIt v1.0. > > In this version we add some new features, passed over the red tests and > clean up some dead code. And did a pass in the documentation > > A bit from the DOC > Downloading > > Current stable version of taskit can be downloaded using metacello as > follows: > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit'; > load. > > If you want a specific release such as v1.0, you can load the associated > tag as follows > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit:v1.0'; > load. > > Otherwise, if you want the latest development version, take a look at the > development branchs and load the latest: > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit:dev-1.1'; > load. > > > <https://github.com/sbragagnolo/taskit/blob/master/README.md#major-features>Major > Features > > - Actors (ActIt) > - Configuration Profiles > - Service > > > Check specially the configuration profiles. The default profile usage is > #development, which sets up the environment for debugging exceptions in a > process. > > I want to thank a lot to the contributors, Guillermo Polito Max Leske > and Daniel Sasu. > I want as well to thanks the users, specially to those that bring me > feedback (blames and ideas) in person (Esteban, Pablo) or through the > different channels (Holger Freyther, Juraj Kubelka, Philippe Back). > > > I want also to apologise the delay of my responses on the issue board :) > (Really, sorry). I am constantly using TaskIt in other projects, but much > times I cannot do it my priority. > > > thanks a lot, > > Santiago Bragagnolo. > > > > > > > > > > >

2 2

[Ann] TaskIt v1.0
by Santiago Bragagnolo Nov. 29, 2018

Nov. 29, 2018

Hi everybody :). I am happy to announce TaskIt v1.0. In this version we add some new features, passed over the red tests and clean up some dead code. And did a pass in the documentation A bit from the DOC Downloading Current stable version of taskit can be downloaded using metacello as follows: Metacello new baseline: 'TaskIt'; repository: 'github://sbragagnolo/taskit'; load. If you want a specific release such as v1.0, you can load the associated tag as follows Metacello new baseline: 'TaskIt'; repository: 'github://sbragagnolo/taskit:v1.0'; load. Otherwise, if you want the latest development version, take a look at the development branchs and load the latest: Metacello new baseline: 'TaskIt'; repository: 'github://sbragagnolo/taskit:dev-1.1'; load. <https://github.com/sbragagnolo/taskit/blob/master/README.md#major-features>Major Features - Actors (ActIt) - Configuration Profiles - Service Check specially the configuration profiles. The default profile usage is #development, which sets up the environment for debugging exceptions in a process. I want to thank a lot to the contributors, Guillermo Polito Max Leske and Daniel Sasu. I want as well to thanks the users, specially to those that bring me feedback (blames and ideas) in person (Esteban, Pablo) or through the different channels (Holger Freyther, Juraj Kubelka, Philippe Back). I want also to apologise the delay of my responses on the issue board :) (Really, sorry). I am constantly using TaskIt in other projects, but much times I cannot do it my priority. thanks a lot, Santiago Bragagnolo.

2 1