November 2018 - Pharo-users

Re: [Pharo-users] Loading Metacello with Seaside

by Cyril Ferlicot D.

Le 28/11/2018 Ã 00:08, Vitor Medina Cruz a Ã©critÂ : > 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> Hi, Personally I declare my Magritte dependency with the Seaside group this way: spec baseline: 'Magritte' with: [ spec loads: #('Seaside'); repository: 'github://magritte-metamodel/magritte:v3.5.3/source' ]. If it can help you, here is a recent guide to Baselines: https://github.com/pharo-tips-and-tricks/pharo-tips-and-tricks/blob/master/… -- Cyril Ferlicot https://ferlicot.fr

Nov. 27, 2018

Loading Metacello with Seaside

by Vitor Medina Cruz

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>

Nov. 27, 2018

Re: [Pharo-users] Playing with Pharo 7

by Vitor Medina Cruz

The documentation on the book has much more information than needed to use Metacello with Iceberg, it can confuse you more than help I am afraid, at least this happened to me. The guide provided by Cyril is what you want. <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> On Tue, Nov 27, 2018 at 8:01 AM Steffen MÃ¤rcker <merkste(a)web.de> wrote: > Great! > > Am .11.2018, 21:47 Uhr, schrieb Cyril Ferlicot D. > <cyril.ferlicot(a)gmail.com>: > > > Le 26/11/2018 Ã 16:57, Konrad Hinsen a Ã©crit : > >> > >> Thanks for the pointer! Unfortunately all the documentation there > >> assumes way more familiarity with Smalltalk than I have. And even a lot > >> of familiarity with Metacello itself, as the documentation only explains > >> the latest functionality. > >> > >> The good news is that it refers to "Deep into Pharo", so I will download > >> that book and see if answers my questions. > >> > >> Konrad. > >> > > > > Hello, > > > > There is also a recent guide here: > > > https://github.com/pharo-tips-and-tricks/pharo-tips-and-tricks/blob/master/… > > > > I don't know if it is more beginner friendly. Feedback is welcome. > > > > > >

Nov. 27, 2018

Re: [Pharo-users] Problems with Firmata & Arduino UNO Clone

by Ben Coman

On Tue, 27 Nov 2018 at 05:59, William L. Cleveland <wlc1(a)columbia.edu> wrote: > 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â. > Was the Arduino IDE closed before you started Pharo? Or further, try Pharo immediately after booting your PC. cheers -ben >

Nov. 27, 2018

Re: [Pharo-users] Problems with Firmata & Arduino UNO Clone

by Denis Kudriashov

Hi William. I think Serial port does not work in MacOS VM. Ð¿Ð½, 26 Ð½Ð¾ÑÐ±. 2018 Ð³. Ð² 21:59, William L. Cleveland <wlc1(a)columbia.edu>: > 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 >

Nov. 27, 2018

Re: [Pharo-users] how to write this without a if then

by Dale Henrichs

Roelof, One technique to eliminating the use of #ifTrue:ifFalse: is to use double dispatching. There are some good examples of using double dispatching in Ralph Johnson's paper "ARITHMETIC AND DOUBLE DISPATCHING IN SMALLTALK-80"[1].Â you should be able to get the basic idea by skimming the smalltalk code examples. I used double dispatching fairly extensively in Metacello ... In practice you may not eliminate all use of #ifTrue:ifFalse:, but double dispatching works quite well in places where you are tempted to do type checking... Dale [1] https://www.researchgate.net/publication/239578755_Arithmetic_and_double-_d… On 11/27/18 8:40 AM, Roelof Wobben wrote: > Hello, > > Yesterday I had a talk with luc frabresse about using if then. > He said if I understand it right, Its the best to not using a if then > or a ifTrue/ifFalse. > > Can anyone help me figure out how to rewrite this project so I will > not use the ifTrue in the basement function. > > my code so far can be found here : > https://github.com/RoelofWobben/AOC2015 > > Roelof > >

Nov. 27, 2018

Re: [Pharo-users] Pharo 7 - RFB

by Sanjay Minni

thanks all ----- cheers, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 27, 2018

how to write this without a if then

by Roelof Wobben

Hello, Yesterday I had a talk with luc frabresse about using if then. He said if I understand it right, Its the best to not using a if then or a ifTrue/ifFalse. Can anyone help me figure out how to rewrite this project so I will not use the ifTrue in the basement function. my code so far can be found here : https://github.com/RoelofWobben/AOC2015 Roelof

Nov. 27, 2018

Re: [Pharo-users] subpackages in P7

by Peter Uhnak

The main benefit of using separate packages instead of tags is that you can choose what to load. That's why MyPackage-Test is best kept separate, because when other project is loading your project, they don't need to load such package (which can speed up dependency loading and makes for smaller images). As changing it in either direction is usually simple, don't worry about not using the "right" style. Peter On Tue, Nov 27, 2018 at 3:36 PM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > On 27 Nov 2018, at 15:03, Roelof Wobben <r.wobben(a)home.nl> wrote: > > > > Thanks, > > > > So better is leave it this way. So three seperate packages as I > understand you well. > > I just said I would keep âtestsâ separated. The rest I do not have any > opinion :) > > Esteban > > > > > Roelof > > > > > > > > > > Op 27-11-2018 om 10:47 schreef Esteban Lorenzano: > >> Yes, you can :) > >> (But I would recommend it doing it with tests) > >> > >> Usually, what you do is to create your package âProjectâ and then > inside that package you can add the tags âtestâ and âActionsâ, > >> > >> But now you already have three packages, and you want to move, for > example âProject-Actionsâ into âProjectâ. To do this you need to select > âProject-Actionâ and with right click select the option âextrasâ in your > context menu. From there, you need to select âdemote to package with tagâ. > This will move all Project-Action package into âProjectâ package, âActionâ > tag. > >> > >> Cheers, > >> Esteban > >> > >> > >>> On 27 Nov 2018, at 09:33, Roelof Wobben <r.wobben(a)home.nl> wrote: > >>> > >>> 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, > >>> > >>> > >>> > >> > >> > > > > > > >

Nov. 27, 2018

Re: [Pharo-users] Problems with NeoCSV Package

by Peter Uhnak

Hi, > Instance of ByteString doesnât understand #atEnd. This is a very typical error when you have accidentally passed a String instead of a Stream. ... which you did here: > stream := workingDir/myFileName readStreamDo: [ :stream | stream contents]. You can either operate directly on the file stream, e.g. file := 'D:\tmp\rules.csv' asFileReference. result := file readStreamDo: [ :stream | |reader| reader := NeoCSVReader new. reader on: stream. reader upToEnd. ]. Or if you already have a string, then ask it for its readStream file := 'D:\tmp\rules.csv' asFileReference. contents := file contents. reader := NeoCSVReader new. reader on: contents readStream. reader upToEnd. On Mon, Nov 26, 2018 at 11:27 PM William L. Cleveland <wlc1(a)columbia.edu> wrote: > I need to manually tag a large number of sentences choosing between a > small, fixed number of short strings as tags for each sentence. I would > like to do this with a Pharo GUI that displays sentences one at a time and > permit choice of tags using radio buttons. The results need to be saved as > a CSV file on the hard drive for further manipulations with python. > > As a first step, I used Excel to create a test CSV file with two sentences > that was saved on the disk drive in the Pharo working directory. > > I have subsequently tried to import the sentences into Pharo 6.1 32 bit > stable. This was done as follows. > > |workingDir reader result| > > workingDir := FileSystem disk workingDirectory. > > myFileName := 'MoonCSV.csv'. > > stream := workingDir/myFileName readStreamDo: [ :stream | stream > contents]. > > > > reader := (NeoCSVReader new) separator: Character cr. The separator > was changed from a comma to a cr because the inspector showed a cr, not a > comma separating the two imported sentences. > > result := (reader on: stream). > > result upToEnd. > > This failed with the following error: > > Instance of ByteString doesnât understand #atEnd. > > > I donât see how to proceed further. Also I am not clear on the best way to > export the sentence and tags to the disk drive.. > > > Any help would be appreciated. > > Lou Cleveland >

Nov. 27, 2018