May 2018 - Pharo-users - lists.pharo.org

On UDP broadcast

by Hilaire

Hi, I try to figure out this matter. I am just new to this domain so excuse me for the obvious the errors. To broadcast an IP, this seems to work: | socket | socket := Socket newUDP. socket setOption: 'SO_BROADCAST' value: true. 10 timesRepeat: [ Â Â Â socket sendUDPData: '10.7.2.1'Â toHost: #[255 255 255 255] port: 9999. Â Â Â (Delay forSeconds: 1) wait. Â Â Â Â ]. socket closeAndDestroy. Then I can listen from the shell: with: nc -ulk 9999 Now for the listener part, I wrote something like: | socket data | socket := Socket newUDP. socket connectTo: NetNameResolver loopBackAddress port: 9999. socket waitForConnectionFor: 2. [data := socket receiveDataTimeout: 5. data crLog] ensure: [ socket closeAndDestroy] But I got an error when connecting the socket, the debugger message is: "InvalidSocketStatusException: Socket status must Unconnected before opening a new connection" So far I don't see understand this error. Port 9999 is not in use, and running again after this error the broadcast code does not lead to an error. Any idea? Thanks Hilaire -- Dr. Geo http://drgeo.eu

May 20, 2018

Re: [Pharo-users] [Ann] OSSubprocess 1.0.0

by Guillermo Polito

Hi Sean On Fri, May 18, 2018 at 9:49 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Guillermo Polito wrote > > If you have any issuesâ¦ > > IMHO the biggest issue is incompatibility with OSProcess. This seems not to > matter when one is loading Project A depending on OSSP in a clean image, > but > the second one tries to load Project A into an image where Project B > already > depends on OSP - KABOOM! Game over. > Well, I cannot say much about why this happens. I've seen it happening, but I try not to depend on projects using OSProcess in that case. Can we also say the same the other way around? If we have OSSubprocess loaded and I download a project using OSProcess, does it break the same? I understand that the incompatibilities bother, but putting all the fault in OSSubprocess and not in OSProcess seems not fair :). Maybe both should be modified to be compatible? Dunno... > On a more philosophical note, I never understood why OSSP was created in > the > first place since we have OSP; I cannot answer this, I'll let Mariano or somebody from the Pharo board on this one. > and especially why the API is different, > making switching more difficult. I found OSProcess API particularly bad. It's never clear to me whether to use OSProcess, PipeableSomething or CommandWhatever (I don't even remember the names of the things that **do work** and I have to look them every time). To be fair, to me even sometimes OSProcess is too verbose. Most people only want to do output := OSProcess executeCommand: 'ls'. Blocking. Recovering stdout. And that's all. So in that sense, I think that letting us move on and rethink the API is not bad at all... Then, we can think on providing some compatibility layer to help people in migrating. So, if anyone want to take action on this point... I'm sure there was a good reason to do > OSSP, but it might be helpful to clarify in the docs (so tradeoffs between > OSP and OSSP can be understood by prospective users). > Well from a technical point of view, if you want to choose from one or another today I'd say: - OSSP is written mostly in FFI, what means that it is easier to modify and ship. - I'm sure OSSP works: it has way more tests and we are using it for several projects ourselves. (Please notice I do not say that OSP does not work, I say I have no way to be sure that it works because tests do not run). So we are eating our own food: - we use them to run iceberg tests - pillar is using it to compile pdfs I've put myself quite some effort to have a working CI, with stress tests, 64bits. I've just tried to run OSP tests and they do not even run in Pharo because they use FileDirectory (and even latest version is updated to work on Cuis)... Having a compatibility layer to make such a project run on squeak, cuis and Pharo looks like a gigantic task for a project that seems so core to me. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

May 20, 2018

Re: [Pharo-users] [Pharo-dev] LibFFI/NB Cairo External Module Not Found debugging

by Ben Coman

I've not used this, just found it poking around... https://blogs.msdn.microsoft.com/junfeng/2006/11/20/debugging-loadlibrary-f… cheers -ben On 19 May 2018 at 19:37, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi, > > some Windows users are repeatedly running into Pharo failing to load Cairo > library on Windows (see stack screenshot at the bottom). > > The problem is that I have no idea how to even start debugging this. > > Is there some documentation on how Pharo loads libraries via FFI on > Windows that I can start digging into? > > Note that the library is definitely present, as this happens only > occasionally -- it can be fixed by restarting PC. But I cannot reasonably > ask users to restart just because Pharo decided it doesn't feel like > loading a library. > > Any pointers / docs / ideas appreciated. > > Thanks, > Peter > > > >

May 20, 2018

LibFFI/NB Cairo External Module Not Found debugging

by Peter UhnÃ¡k

Hi, some Windows users are repeatedly running into Pharo failing to load Cairo library on Windows (see stack screenshot at the bottom). The problem is that I have no idea how to even start debugging this. Is there some documentation on how Pharo loads libraries via FFI on Windows that I can start digging into? Note that the library is definitely present, as this happens only occasionally -- it can be fixed by restarting PC. But I cannot reasonably ask users to restart just because Pharo decided it doesn't feel like loading a library. Any pointers / docs / ideas appreciated. Thanks, Peter

May 19, 2018

Re: [Pharo-users] [Errors] email on error?

by Peter UhnÃ¡k

On Fri, May 18, 2018 at 9:12 PM, Tim Mackinnon <tim(a)testit.works> wrote: Equally you could perhaps trap something in Pharo and write out a fuel file > to an s3 bucket - with s3 you can then trigger an event and they have tools > you can use to alert and or email I do this too -- fuel is really simple to use, and S3 can be as simple as a single PUT request (unless you want some constraints like content type and size limiting). I use combination of Sentry + S3: sentry contains the stack and bunch of other metadata, and I save fuel files to S3 named accordingly to the same sentry event... that way there's no mess in files. For self-setup, you can copy how ShoreLine operates to see how to hook it up to Pharo (some other tips are here http://forum.world.st/global-exception-handler-mechanism-td5065563.html#a50… , but I didn't yet have time to properly investigate them ) Peter

May 18, 2018

Re: [Pharo-users] How to LAN feature

by Hilaire

Oh, forget about my request, I miss some of the important comments in your package. I should have enought to play with it. Le 18/05/2018 Ã 11:33, Hilaire a Ã©critÂ : > > As I have very limited knowledge on network stuff, to get started, do > you have simple example code to show how to use your package? -- Dr. Geo http://drgeo.eu

May 18, 2018

Re: [Pharo-users] [Ann] OSSubprocess 1.0.0

by Sean P. DeNigris

Guillermo Polito wrote > If you have any issuesâ¦ IMHO the biggest issue is incompatibility with OSProcess. This seems not to matter when one is loading Project A depending on OSSP in a clean image, but the second one tries to load Project A into an image where Project B already depends on OSP - KABOOM! Game over. On a more philosophical note, I never understood why OSSP was created in the first place since we have OSP; and especially why the API is different, making switching more difficult. I'm sure there was a good reason to do OSSP, but it might be helpful to clarify in the docs (so tradeoffs between OSP and OSSP can be understood by prospective users). ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 18, 2018

Re: [Pharo-users] [Errors] email on error?

by Tim Mackinnon

Rather than email you could possibly hook in something like datadog or Pingdom if you expose some metric - to get a timely alert. Equally you could perhaps trap something in Pharo and write out a fuel file to an s3 bucket - with s3 you can then trigger an event and they have tools you can use to alert and or email (Ive not tried this - other than write to an s3 bucket - but I saw an AWS presentation on all there cloud tools and it looked straight forward) . Tim Sent from my iPhone > On 18 May 2018, at 18:33, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi Sergio, > > I highly recommend using a more sophisticated solution such as Sentry ( https://github.com/peteruhnak/pharo-sentry , https://peteruhnak.github.io/pharo-sentry/ ). > > If you want something really simple, then ShoreLine can be of assistance (assuming you use Pharo 6; it was removed in P7) > You can enable automatic reporting in settings, and if you want to send email instead of a API request, then look at (and change) SlReporter>>send: > > But I have to strongly discourage you from using simple stack traces in mail... it is a nightmare to manage; especially if you have multiple servers/versions/errors occur in a loop, etc. > (I've tried using SL for about 2 months, and I've failed miserably. That's why I wrote pharo-sentry). > > Peter > >> On Fri, May 18, 2018 at 5:51 PM, sergio ruiz <sergio.rrd(a)gmail.com> wrote: >> Is there a way to send an email on an error or exception? >> >> I have an app that runs live on a remote server, and I am finding that every now and then, the server will lock up, and I wonât know whatâs going on with it. >> >> Currently, i pull the image and run it local, but an email with a stack trace would be SUPER helpful. >> >> Thanks! >> >> >> >> ---- >> peace, >> sergio >> photographer, journalist, visionary >> >> Public Key: http://bit.ly/29z9fG0 >> #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV >> http://www.codeandmusic.com >> http://www.twitter.com/sergio_101 >> http://www.facebook.com/sergio101 >

May 18, 2018

UK Smalltalk User Group meeting - Monday May 21st

by Giovanni Corriga

The next meeting of the UK Smalltalk User Group Meeting will be on Monday, 21st May. We'll meet at our now usual venue The City Pride ( http://www.cityprideclerkenwell.co.uk/ ) at 7pm. For this monthâs meeting, weâll do a session of bug hunting: fix a few things in our favourite Smalltalk frameworks and tools. If you'd like to join us, you can just show up at the pub. You can also sign up in advance at the meeting's Meetup page: http://www.uksmalltalk.org/2018/05/bug-hunting-monday-may-25th.html . See you there!

May 18, 2018

Re: [Pharo-users] [Errors] email on error?

by Peter UhnÃ¡k

Hi Sergio, I highly recommend using a more sophisticated solution such as Sentry ( https://github.com/peteruhnak/pharo-sentry , https://peteruhnak.github.io/pharo-sentry/ ). If you want something really simple, then ShoreLine can be of assistance (assuming you use Pharo 6; it was removed in P7) You can enable automatic reporting in settings, and if you want to send email instead of a API request, then look at (and change) SlReporter>>send: But I have to strongly discourage you from using simple stack traces in mail... it is a nightmare to manage; especially if you have multiple servers/versions/errors occur in a loop, etc. (I've tried using SL for about 2 months, and I've failed miserably. That's why I wrote pharo-sentry). Peter On Fri, May 18, 2018 at 5:51 PM, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > Is there a way to send an email on an error or exception? > > I have an app that runs live on a remote server, and I am finding that > every now and then, the server will lock up, and I wonât know whatâs going > on with it. > > Currently, i pull the image and run it local, but an email with a stack > trace would be SUPER helpful. > > Thanks! > > > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 >

May 18, 2018

[Ann] OSSubprocess 1.0.0

by Guillermo Polito

Hi all, News from the OSSubprocess side. For those who do not know it, OSSubprocess is the library to call external processes from Pharo. These are the main points of this release. - 64bits support - Issues Working on both Pharo 6 and 7 - Issue #34: Adding tests to validate that the return code is correctly handled - Issue #27: Cleanup: remove OSSubprocess-Tests package - PR #26: Add stress tests This version works for Pharo >=6. Users of Pharo5 will need to stick with v0.2.5, because of non compatible changes in uFFI (required mostly for 64 bits). Additionally: - We moved the repository to pharo-contribution to remove pressure from Mariano for releases and integrations - We updated the configuration in the catalog - We decided to move to a 1.0.0 versioning schema because 0.* does look like the library is not stable and it actually is (We have been using it in pillar and iceberg for quite some time). You can load this version from the catalog or using with: Metacello new baseline: 'OSSubprocess'; repository: 'github://pharo-contributions/OSSubprocess:v1.0.0/repository'; load. Detailed changes log in - https://github.com/pharo-contributions/OSSubprocess/releases/tag/v1.0.0 - https://github.com/pharo-contributions/OSSubprocess/compare/v0.2.5...v1.0.0 If you have any issues (or PR!), we wait for your issue entry in https://github.com/pharo-contributions/OSSubprocess/issues Have a nice weekend, -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

May 18, 2018

[Errors] email on error?

by sergio ruiz

Is there Â a way to send an email on an error or exception? I have an app that runs live on a remote server, and I am finding that every now and then, the server will lock up, and I wonât know whatâs going on with it. Currently, i pull the image and run it local, but an email with a stack trace would be SUPER helpful. Thanks! ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

May 18, 2018

Re: [Pharo-users] Showing Keyboard events as Pharo goes weird when using an RD client for OSX

by Tim Mackinnon

Actually - I installed VNC on Linux server and itâs much faster and doesnât have this issue . I think for keyboard events I would have had to create a morph and then override some handle key events to print them out ? As it stands, Iâll forge on with other stuff (unless anyone happens to know) Tim Sent from my iPhone > On 18 May 2018, at 12:00, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - Iâm wondering if anyone has any experience using Pharo in a Remote Desktop environment? > > Ive been experimenting with MacInCloud.com and running Pharo there - however Iâve noticed that while it appears to run (and it reasonably performant) after a few seconds/minutes (I canât quite work out what causes it) certain keeps stop working - most importantly the Enter key (but also Cmd-P etc). > > It looks like its dishing out some kind of tab key (its invisible in the playground - the cursor just jumps forward a few characters) but Iâm not sure, and I wondered if I could print out key codes in Pharo to maybe spot what it is. But keyboard handling is not something Iâve dug into - and Iâm looking for a few pointers (or maybe someone has seen this problem before and might be able to suggest a solution). > > As I said, It starts out ok but then suddenly swaps to this behaviour (which makes coding then impractical). Restating the RD client doesnât make a difference (and Iâve tried 2 different ones now). Other remote mac apps like Notes donât seem to be affected and I have to exit the image and come back in to correct it. (I havneât tried saving in between to see if it then preserves this behaviour). > > Ulimately I was hoping to have an easy portable Pharo environment to sneakily take on holiday via an iPad. > > The approach is to try and compile Pharo for iOS (I did it a long time ago, but it was a pain - whereas a remote server seemed like a neat solution). > > Tim > > > Sent from my iPhone

May 18, 2018

Re: [Pharo-users] [Pharo-dev] [ANN] Alternative Pharo-contributor tool now explained with videos

by Sven Van Caekenberghe

> On 18 May 2018, at 12:41, Torsten Bergmann <astares(a)gmx.de> wrote: > > https://github.com/astares/pharo-contributor > > now provides two videos demonstrating how this tool can be used as an alternative to easily contribute to latest Pharo 7 > > > VIDEO 1 > https://www.youtube.com/watch?v=z4PWGxihdxU > > VIDEO 2 > https://www.youtube.com/watch?v=24ERozCePME Nice, very detailed, step by step explanation, well done and thank you for sharing this. With the latest Iceberg (with the 'Repair ...' technology), you get a similar experience (I know you wrote your tool earlier). You can also do the PR in Pharo itself now (but doing in the Github web UI is OK too). Sven

May 18, 2018

[ANN] Alternative Pharo-contributor tool now explained with videos

by Torsten Bergmann

https://github.com/astares/pharo-contributor now provides two videos demonstrating how this tool can be used as an alternative to easily contribute to latest Pharo 7 VIDEO 1 https://www.youtube.com/watch?v=z4PWGxihdxU VIDEO 2 https://www.youtube.com/watch?v=24ERozCePME

May 18, 2018

Showing Keyboard events as Pharo goes weird when using an RD client for OSX

by Tim Mackinnon

Hi - Iâm wondering if anyone has any experience using Pharo in a Remote Desktop environment? Ive been experimenting with MacInCloud.com and running Pharo there - however Iâve noticed that while it appears to run (and it reasonably performant) after a few seconds/minutes (I canât quite work out what causes it) certain keeps stop working - most importantly the Enter key (but also Cmd-P etc). It looks like its dishing out some kind of tab key (its invisible in the playground - the cursor just jumps forward a few characters) but Iâm not sure, and I wondered if I could print out key codes in Pharo to maybe spot what it is. But keyboard handling is not something Iâve dug into - and Iâm looking for a few pointers (or maybe someone has seen this problem before and might be able to suggest a solution). As I said, It starts out ok but then suddenly swaps to this behaviour (which makes coding then impractical). Restating the RD client doesnât make a difference (and Iâve tried 2 different ones now). Other remote mac apps like Notes donât seem to be affected and I have to exit the image and come back in to correct it. (I havneât tried saving in between to see if it then preserves this behaviour). Ulimately I was hoping to have an easy portable Pharo environment to sneakily take on holiday via an iPad. The approach is to try and compile Pharo for iOS (I did it a long time ago, but it was a pain - whereas a remote server seemed like a neat solution). Tim Sent from my iPhone

May 18, 2018

Re: [Pharo-users] How to LAN feature

by Hilaire

Hi Henrik, As I have very limited knowledge on network stuff, to get started, do you have simple example code to show how to use your package? Thanks Hilaire Le 08/05/2018 Ã 08:28, Henrik Sperre Johansen a Ã©critÂ : > No, but it does involve setting certain options on the socket, etc. > You could check ifhttp://smalltalkhub.com/#!/~henriksp/SSDP is > appropriate/works for you. -- Dr. Geo http://drgeo.eu

May 18, 2018

Re: [Pharo-users] [TechTalk] TODAY, 17h: Pillar

by Marcus Denker

> On 17 May 2018, at 15:44, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > Today, 17h europe time. > > Pharo TechTalk: Pillar > https://association.pharo.org/event-2797069 > > Sorry for the late announcement (we did not know if we could make it today) > https://www.youtube.com/c/EstebanLorenzano/live

May 17, 2018

[TechTalk] TODAY, 17h: Pillar

by Marcus Denker

Hi, Today, 17h europe time. Pharo TechTalk: Pillar https://association.pharo.org/event-2797069 Sorry for the late announcement (we did not know if we could make it today) Marcus

May 17, 2018

Re: [Pharo-users] Restoring a class via Epicea didn't recompile a reference?

by Marcus Denker

> On 3 May 2018, at 10:15, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 2 May 2018, at 14:09, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >> >>> On 26 Apr 2018, at 09:28, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >>> >>> Hi, >>> >>> It looks you got bit by this issue: >>> >>> https://pharo.fogbugz.com/f/cases/21519/RemoveFromSystem-does-not-work-well… >>> >>> It's not particular to Epicea. There should be a better management of Undeclareds in general in all Pharo. >>> >> >> It can be fixed by moving the binding to undeclared in #removeFromSystem: >> >> This is done by adding >> >> Undeclared declare: self name asSymbol from: Smalltalk globals. >> >> before the "forgetClass: self logged:" line. >> >> What we need to do in addition: Only do that when the class is referenced. #isUsedClass: does that, but it does integrate over all methods in the system. >> > > I did a PR: > > https://github.com/pharo-project/pharo/pull/1281 > In the end I split the PR in two: #isReferenced first (already in) and now the one liner to put classes that are still referenced into Undeclared: https://github.com/pharo-project/pharo/pull/1374 This just adds self isReferenced ifTrue: [Undeclared declare: self name asSymbol from: Smalltalk globals]. And it seems to workâ¦ Marcus

May 17, 2018

Re: [Pharo-users] Smalltalk CI on Gitlab

by Tim Mackinnon

Hi Sean - I stand corrected, #remoteTypeSelector: doesnât seem to be needed (a case of getting all the other stuff right - and Docker is such a huge help for this). For SmalltalkCI the automatic Test side might win me over. Does it also spot load load failures (like Undeclared class) and do a nice test report? I just spotted Seaside isnât loading cleanly with my RegEx setup - but its crude. This has been very fruitful BTW , thanks Tim Sent from my iPhone Sent from my iPhone > On 16 May 2018, at 19:54, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Tim Mackinnon wrote >> the use of Iceberg and projects using github:// (which needs them by >> default) causes quite a lot of pain (even if they arenât private repos). >> â¦ >> Iceberg >> enableMetacelloIntegration: true; >> remoteTypeSelector: #httpsUrl. > > This is part of my standard workflow and I didn't experience it as a pain > point. It seems I uploaded my public GH key, but after that it "just > worked". IIRC it seemed to automatically fallback to https when ssh failed, > but it's been a while and I'm not in front of a pipeline. The first message > is needed, especially to use `gitlab://` URLs, but I never used the second. > > > Tim Mackinnon wrote >> the reality is all you are really plugging into Gitlab is: >> â¦loadProject.stâ¦ testProject.st > > I guess you could say that, except smalltalkCI also handles any needed > setup, like Linux 32-bit libs (which I handle with Docker instead). Also, it > saves you from having to construct the .st files in your example because: > - there is a configuration model that allows you to specify the baseline > name, target platforms, etc instead of manually writing load scripts > - smalltalkCI remembers which tests it loaded and runs those automatically, > so by default no extra work is needed to enable testing > > > Tim Mackinnon wrote >> by no means is this a citicismâ¦ > > All good :) > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

May 16, 2018

Re: [Pharo-users] Morphic, Canvas, and Drawing Polygon Borders

by Nicolai Hess

Hi Eric, I don't know exactly how Borders (BorderdMorphs) are drawn, but a simple way to create that kind of 1px border with 2px round edges may be using the a borderd morph: BorderedMorph new fillStyle: Color transparent; borderStyle: (RoundedBorder new cornerRadius: 2; width: 1; baseColor: Color red) Combining this with a Complex border to create that button with different colors for left-up/right-bottom edges is maybe more difficult. 2018-05-16 20:48 GMT+02:00 Eric Gade <eric.gade(a)gmail.com>: > I am having some trouble accurately drawing polygons using Morphic and the > various Canvas types. > > My task is to recreate the Mac OS Platinum style buttons, and do be as > pixel-accurate as I can. For the basic button, this involves creating a > rectangle whose corners are always fattened by 2px on each side, no matter > the extent of the underlying morph: > > > â > I can achieve this kind of outline when drawing individual lines one at a > time with a Canvas: > > ```smalltalk > > canvas := FormCanvas extent: 150@30. > > rect := Rectangle point: (0@0) point: (150@30). > > vertices := { > (rect left)@(rect top + 2). > (rect left + 2)@(rect top). > (rect right - 3)@(rect top). > (rect right - 1)@(rect top + 2). > (rect right -1)@(rect bottom - 3). > (rect right - 3)@(rect bottom -1). > (rect left + 2)@(rect bottom - 1). > (rect left)@(rect bottom - 3). > "(rect left)@(rect top + 2)" }. > > canvas > line: (vertices at: 1) to: (vertices at: 2) color: Color black; > line: (vertices at: 2) to: (vertices at: 3) color: Color black; > line: (vertices at: 3) to: (vertices at: 4) color: Color black; > line: (vertices at: 4) to: (vertices at: 5) color: Color black; > line: (vertices at: 5) to: (vertices at: 6) color: Color black; > line: (vertices at: 6) to: (vertices at: 7) color: Color black; > line: (vertices at: 7) to: (vertices at: 8) color: Color black; > line: (vertices at: 8) to: (vertices at: 1) color: Color black. > > canvas form asMorph openInWindow. > > ``` > > Which gives me: > > â > But using the native Polygon drawing features of Canvas yield a different, > and incorrect, result: > > ```smalltalk > > canvas := FormCanvas extent: 150@30. > > rect := Rectangle point: (0@0) point: (150@30). > > vertices := { > (rect left)@(rect top + 2). > (rect left + 2)@(rect top). > (rect right - 3)@(rect top). > (rect right - 1)@(rect top + 2). > (rect right -1)@(rect bottom - 3). > (rect right - 3)@(rect bottom -1). > (rect left + 2)@(rect bottom - 1). > (rect left)@(rect bottom - 3). > "(rect left)@(rect top + 2)" }. > > canvas drawPolygon: vertices fillStyle: Color transparent borderWidth: 1 borderColor: Color black. > > canvas form asMorph openInHand. > > ``` > > > > â > Either this is some kind of limitation in BalloonCanvas/BalloonEngine > (which "becomes" the canvas for polygon draw operations) or I am doing > something terribly wrong. > > Ideally I can trace this shape as a border, since I'll need to trace yet > more additional borders around it (like the "default" button in Platinum, > which has a fat complex border). > > Borders are already kind of complicated, so any help you all can provide > would be much appreciated. > > FYI this same behavior is present in Squeak. > > -- > Eric >

May 16, 2018

Re: [Pharo-users] Smalltalk CI on Gitlab

by Sean P. DeNigris

Tim Mackinnon wrote > the use of Iceberg and projects using github:// (which needs them by > default) causes quite a lot of pain (even if they arenât private repos). > â¦ > Iceberg > enableMetacelloIntegration: true; > remoteTypeSelector: #httpsUrl. This is part of my standard workflow and I didn't experience it as a pain point. It seems I uploaded my public GH key, but after that it "just worked". IIRC it seemed to automatically fallback to https when ssh failed, but it's been a while and I'm not in front of a pipeline. The first message is needed, especially to use `gitlab://` URLs, but I never used the second. Tim Mackinnon wrote > the reality is all you are really plugging into Gitlab is: > â¦loadProject.stâ¦ testProject.st I guess you could say that, except smalltalkCI also handles any needed setup, like Linux 32-bit libs (which I handle with Docker instead). Also, it saves you from having to construct the .st files in your example because: - there is a configuration model that allows you to specify the baseline name, target platforms, etc instead of manually writing load scripts - smalltalkCI remembers which tests it loaded and runs those automatically, so by default no extra work is needed to enable testing Tim Mackinnon wrote > by no means is this a citicismâ¦ All good :) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 16, 2018

Morphic, Canvas, and Drawing Polygon Borders

by Eric Gade

I am having some trouble accurately drawing polygons using Morphic and the various Canvas types. My task is to recreate the Mac OS Platinum style buttons, and do be as pixel-accurate as I can. For the basic button, this involves creating a rectangle whose corners are always fattened by 2px on each side, no matter the extent of the underlying morph: â I can achieve this kind of outline when drawing individual lines one at a time with a Canvas: ```smalltalk canvas := FormCanvas extent: 150@30. rect := Rectangle point: (0@0) point: (150@30). vertices := { (rect left)@(rect top + 2). (rect left + 2)@(rect top). (rect right - 3)@(rect top). (rect right - 1)@(rect top + 2). (rect right -1)@(rect bottom - 3). (rect right - 3)@(rect bottom -1). (rect left + 2)@(rect bottom - 1). (rect left)@(rect bottom - 3). "(rect left)@(rect top + 2)" }. canvas line: (vertices at: 1) to: (vertices at: 2) color: Color black; line: (vertices at: 2) to: (vertices at: 3) color: Color black; line: (vertices at: 3) to: (vertices at: 4) color: Color black; line: (vertices at: 4) to: (vertices at: 5) color: Color black; line: (vertices at: 5) to: (vertices at: 6) color: Color black; line: (vertices at: 6) to: (vertices at: 7) color: Color black; line: (vertices at: 7) to: (vertices at: 8) color: Color black; line: (vertices at: 8) to: (vertices at: 1) color: Color black. canvas form asMorph openInWindow. ``` Which gives me: â But using the native Polygon drawing features of Canvas yield a different, and incorrect, result: ```smalltalk canvas := FormCanvas extent: 150@30. rect := Rectangle point: (0@0) point: (150@30). vertices := { (rect left)@(rect top + 2). (rect left + 2)@(rect top). (rect right - 3)@(rect top). (rect right - 1)@(rect top + 2). (rect right -1)@(rect bottom - 3). (rect right - 3)@(rect bottom -1). (rect left + 2)@(rect bottom - 1). (rect left)@(rect bottom - 3). "(rect left)@(rect top + 2)" }. canvas drawPolygon: vertices fillStyle: Color transparent borderWidth: 1 borderColor: Color black. canvas form asMorph openInHand. ``` â Either this is some kind of limitation in BalloonCanvas/BalloonEngine (which "becomes" the canvas for polygon draw operations) or I am doing something terribly wrong. Ideally I can trace this shape as a border, since I'll need to trace yet more additional borders around it (like the "default" button in Platinum, which has a fat complex border). Borders are already kind of complicated, so any help you all can provide would be much appreciated. FYI this same behavior is present in Squeak. -- Eric

May 16, 2018

Re: [Pharo-users] Smalltalk CI on Gitlab

by Tim Mackinnon

Hi Sean/Fabio - Iâm still mulling over which direction to jump. When experimenting with PharoLambda and a minimal image it was all very custom and so I just used GitLab ânativelyâ - and as you have noted - Gitlab has got a lot of built in CI stuff. Now my need has expanded to something a bit more normal - I was a bit caught out that the above didnât just work the same. As its turned out - what has been the hiccup has been not having a good stable Linux image to build on (Iâve now learned Docker to sort that bit out - and really must +++ the need to have some pharo.org <http://pharo.org/> docker containers just sitting there for people to use). The other issue has been what you have said - in a clean build environment you donât have ssh keys normally defined and and the use of Iceberg and projects using github:// (which needs them by default) causes quite a lot of pain (even if they arenât private repos). I mention this as Herby spotted it a while ago as he doesnât use GitHub - however he also spotted a solution that I donât think you are aware of (judging from your gitlab project) - in your preload script add the following: Iceberg enableMetacelloIntegration: true; remoteTypeSelector: #httpsUrl. This was the piece I was missing - and now my project is loading fine (in its fresh docker environment). You of course probably still have Private repos and in that case I think you still need the ssh keys sorted - but for a more general case I donât think its needed. This long path (which has usefully solidified lots of things for me) still leaves me unsure as to whether I personally need SmalltalkCI for simple single vendor projects (as when used in GitLab - its not really doing any CI - it seems more useful for muli-dialect building I think). Maybe you guys might set me straight on thisâ¦ the reality is all you are really plugging into Gitlab is: pharo Pharo.image --no-default-preferences --save --quit st loadProject.st \ "{'$PROJECT_NAME'. '$PROJECT_API_KEY'}" 2>&1 | tee LoadProject.log And if you are also doing some testing a second invocation (ideally in a separate build stage) of: pharo Pharo.image --no-default-preferences --save --quit st testProject.st \ "{'$PROJECT_NAME'. '$PROJECT_API_KEY'}" 2>&1 | tee TestProject.log And with a good docker image it seems pretty straight forward. Possibly there are components in SmalltalkCI that could be extracted - maybe to interpret test results? Or I am wondering if its useful to pump stats into something like DataDog to track image size and test run times etc? Iâm still interested in both your thoughts though - and by no means is this a citicism of SmalltalkCI or Gitlab-Smalltalk-CI - both of which help the community (and me) immensely through providing great examples and knowledgable people in this stuff. Tim > On 16 May 2018, at 02:50, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Tim Mackinnon wrote >> Have you written anything else up about it - or is this the âuser manualâ >> for now? > > The latter :) It was an itch I scratched because GL offers unlimited private > projects and significant CI build time for free and then shared just in case > others were struggling with the same thing, but I'm happy to answer > questions and add to the docs. > > > Tim Mackinnon wrote >> Presumable a lot of the below could go in the readme.md for the project >> itself. > > Already done! > > > Tim Mackinnon wrote >> So to get started with it > > In your project's root folder, if you copy `.gitlab-ci.yml` verbatim and > modify `.smalltalk.ston` as needed, it should start building your project on > top of Pharo 6 & 7 on 32-bit Ubuntu LTS. The Smalltalk image versions can be > changed to anything accepted by smalltalkCI, and I think to support other > OS'es we'd just need to build alternate Docker images [1]. You would only > need to fork gitlab-smalltalk-ci if you want to modify the internals of the > library itself. If you just want to customize any of the scripts in > ./scripts [2] on a per-project basis, you can just save overridden copies in > ./scripts in your project. The library will not overwrite existing script > files in that location. > > FYI I did not explore deploy steps yet. I was actually waiting to develop > further because the next thing I want is separate build and test steps so > one can immediately know whether the installation or testing failed, and it > seemed that might be added to smalltalkCI in the near future. > > 1. There is also a related library which enables you to generate docker > files from Pharo. See > https://github.com/seandenigris/smalltalkCI/tree/docker/repository/Smalltal… > 2. https://gitlab.com/SeanDeNigris/gitlab-smalltalk-ci/tree/master/scripts > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

May 16, 2018