March 2019 - Pharo-users - lists.pharo.org

Pharo Days - anyone going on Wed night (3rd) and where are folks staying?

by Tim Mackinnon

Hi everyone - Iâve managed to sort out a family pass to attend Pharo Days, so keen to maximise my fun/learning/involvement. I was looking at trains on Wed afternoon - and leaving after lunch get me in Lille late afternoon - so I was wondering (if like a few years ago) any other are around earlier and going for supper (hacking code before supper) and generally socialising? Iâm also curious if others have thought about accommodation (there is lots of reasonable accommodation in Lille centre near the main station - which was pretty good last time I went) - anyone booked anything yet, and Iâll try and position myself in a similar vicinity to aid with the first question. Tim

March 12, 2019

Re: [Pharo-users] Hmmm sending at:put: to an undefined object (nil) gives a confusing error message

by Ben Coman

On Tue, 12 Mar 2019 at 21:56, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > Yes, I do not like itâ¦ I think it is there so that you can just make a variable subclass and at: / at:put: will work without > having to re-implement themâ¦ So we should consider... * how often are variable subclasses created ? by novices or experts ? * how much work is it to reimplement those methods ? how difficult to know what needs to be done ? * what is the balance cheers -ben > > Marcus > > On 12 Mar 2019, at 04:55, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > I understand #basicAt:[put:] being in Object, but I never understood #at:[put:] being there. > GNU Smalltalk: > st> nil at: 1 > Object: nil error: Invalid value nil: object not indexable > In my Smalltalk, you get a DNU. > In Squeak you get a debugger window with title > Error: instances of UndefinedObject are not indexable > The same for Boolean, Character, and Integer, > except Squeak where (20 factorial at: 1) answers 0 (oh dear oh dear oh dear). > In VW you get a "Subscript out of bounds" error, which is disappointing, > as do true and $a, but a LargePositiveinteger gets #shouldNotImplement. > > > On Tue, 12 Mar 2019 at 15:28, Tim Mackinnon <tim(a)testit.works> wrote: >> >> If you forget to initialise a variable which you thought was a Dictionary - you get a confusing error message: "Error: only integers should be used as indicesâ if you try an at:put: >> >> This is a consequence of having at:put: defined on Object (which is a bit nasty) >> >> Should UndefinedObject at least override this and signal something a bit more obvious? This is a common and easily done thing and we don't support it very well. >> >> I just did it in some code, and was scratching my head initially until I read the stack properly and realised it was something much simpler than I thought I had done. >> >> Any thoughts on this? > >

March 12, 2019

Re: [Pharo-users] [ANN] Minimal telepharo

by Ben Coman

On Tue, 12 Mar 2019 at 19:37, Norbert Hartl <norbert(a)hartl.name> wrote: > > Iâm working on having a telepharo image based on the pharo minimal image. With the help of pavel and Allex I prepared a usable artefact on github that can be used. Both images are based on Pharo8. > > The release file > > https://github.com/noha/pharo-minimal/releases/download/0.1/telepharo.zip > > contains a 32 bit minimal telepharo server image. It is 12,1 MB in size. And there is a 64 bit full pharo telepharo client image in the archive that can be used to connect to the minimal server one. I did not include the vms in the archive. These you need to install separately. > > To run the server do > > $ ./pharo server.image eval --no-quit "TlpRemoteUIManager registerOnPort: 40423â > > The client.image can be started as usual. In a playground do > > remotePharo := TlpRemoteIDE connectTo: (TCPAddress ip: #[127 0 0 1] port: 40423) > > remotePharo openPlayground. > > > To be connected to the minimal server image. Further details on telepharo you can find at > > https://github.com/pharo-ide/TelePharo > > Further relases of this will be made available at > > https://github.com/noha/pharo-minimal/releases > > Iâm planning to make a pharothings release available as well when the telepharo release is considered stable. > > Hope you like it. It will be a few weeks before I can try it, but its a really great initiative. Thanks Norbert for bringing such pieces together, as well as those providing the pieces. cheers -ben

March 12, 2019

Re: [Pharo-users] Hmmm sending at:put: to an undefined object (nil) gives a confusing error message

by Marcus Denker

Hi, Yes, I do not like itâ¦ I think it is there so that you can just make a variable subclass and at: / at:put: will work without having to re-implement themâ¦ Marcus > On 12 Mar 2019, at 04:55, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > I understand #basicAt:[put:] being in Object, but I never understood #at:[put:] being there. > GNU Smalltalk: > st> nil at: 1 > Object: nil error: Invalid value nil: object not indexable > In my Smalltalk, you get a DNU. > In Squeak you get a debugger window with title > Error: instances of UndefinedObject are not indexable > The same for Boolean, Character, and Integer, > except Squeak where (20 factorial at: 1) answers 0 (oh dear oh dear oh dear). > In VW you get a "Subscript out of bounds" error, which is disappointing, > as do true and $a, but a LargePositiveinteger gets #shouldNotImplement. > > > On Tue, 12 Mar 2019 at 15:28, Tim Mackinnon <tim(a)testit.works> wrote: > If you forget to initialise a variable which you thought was a Dictionary - you get a confusing error message: "Error: only integers should be used as indicesâ if you try an at:put: > > This is a consequence of having at:put: defined on Object (which is a bit nasty) > > Should UndefinedObject at least override this and signal something a bit more obvious? This is a common and easily done thing and we don't support it very well. > > I just did it in some code, and was scratching my head initially until I read the stack properly and realised it was something much simpler than I thought I had done. > > Any thoughts on this?

March 12, 2019

[ANN] Minimal telepharo

by Norbert Hartl

Iâm working on having a telepharo image based on the pharo minimal image. With the help of pavel and Allex I prepared a usable artefact on github that can be used. Both images are based on Pharo8. The release file https://github.com/noha/pharo-minimal/releases/download/0.1/telepharo.zip <https://github.com/noha/pharo-minimal/releases/download/0.1/telepharo.zip> contains a 32 bit minimal telepharo server image. It is 12,1 MB in size. And there is a 64 bit full pharo telepharo client image in the archive that can be used to connect to the minimal server one. I did not include the vms in the archive. These you need to install separately. To run the server do $ ./pharo server.image eval --no-quit "TlpRemoteUIManager registerOnPort: 40423â The client.image can be started as usual. In a playground do remotePharo := TlpRemoteIDE connectTo: (TCPAddress ip: #[127 0 0 1] port: 40423) remotePharo openPlayground. To be connected to the minimal server image. Further details on telepharo you can find at https://github.com/pharo-ide/TelePharo <https://github.com/pharo-ide/TelePharo> Further relases of this will be made available at https://github.com/noha/pharo-minimal/releases <https://github.com/noha/pharo-minimal/releases> Iâm planning to make a pharothings release available as well when the telepharo release is considered stable. Hope you like it, Norbert

March 12, 2019

Re: [Pharo-users] Pharo and FPGA

by CÃ©drick BÃ©ler

> Le 11 mars 2019 Ã 14:51, Noury Bouraqadi <bouraqadi(a)gmail.com> a Ã©crit : > > Hi Norbert, > > The PhD of Sang (in CC) was about FPGA and Smalltalk. > https://lxsang.me/ <https://lxsang.me/> Really cool, thanks a lot :) > > Noury > >> On 9 Mar 2019, at 15:31, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> Iâm trying to collect information about programming in pharo for FPGA. The only things I found are around PharoROS like this [1]. If anyone has more information or is willing to talk about Iâm open ears. >> >> The background is that we did little things with the PharoThings toolkit and want to research which other combinations like Arduino, ESP32, FPGAs are there to be a good extensions to a Pi. >> >> Any hint is welcomed! >> >> Thanks, >> >> Norbert >> >> [1] http://esug.org/data/ESUG2014/IWST/Papers/iwst2014_From%20Smalltalk%20to%20… > > I found this other reference (ESU15) and the associated youtube video: IWST A meta model supporting both hardware and smalltalk-based ... <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&uac…>https://www.youtube.com/watch?v=N0JNjZipcjY <https://www.youtube.com/watch?v=N0JNjZipcjY> http://esug.org/data/ESUG2015/IWST/Papers/IWST_2015_submission_6.pdf <http://esug.org/data/ESUG2015/IWST/Papers/IWST_2015_submission_6.pdf> And some other there: https://info.lxsang.me/#toc9 So busy, for the next couple hours ;-) (even more with the PhD https://tel.archives-ouvertes.fr/tel-01661569/document <https://tel.archives-ouvertes.fr/tel-01661569/document>) Thanks, CÃ©drick Ps: I was looking at this conference who might be interesting for such subject and applications (but end of this week). https://wiki.f-si.org/index.php/FSiC2019 <https://wiki.f-si.org/index.php/FSiC2019>

March 12, 2019

Re: [Pharo-users] Pharo OSX bundle in Mojave - how to sign ? (Was Re: OS X bundle, some progress)

by Christophe Demarey

Hi Hilaire, > Le 11 mars 2019 Ã 21:27, Hilaire <hilaire(a)drgeo.eu> a Ã©crit : > > Hi, > > Today I realized another problem on some Mac OSX. It looks like when you > download an app on the net, whenever your run it, OS X re-localizes it > on a read only location. A guess a protection measure. It leads to > obvious problem. > > For example, once I download DrGeo and run it, the image location > resolve to this place: > > /private/var/folders/bb/spq6th0s7814jgk9nybbqjrw45hrqn/T/AppTranslocation/D0FEC575-60D6-4F2B-A1C3-3259271B9C92/d/DrGeo.app/Contents/Resources Maybe (I did not do the original packaging) it is the reason why PharoLauncher is delivered as a dmg bundle. The dmg is first decompressed (in a read only location). You the have to copy the app to /Applications (or any other location). Doing that should solve your problems. Regards, Christophe > > I don't have the global picture and it is hard to understand what's > going on. > > Moving to the Application place seems to resolve the issue. But some > users told me they have to move DrGeo from Download, then Application, > then back to Download to get it running without RW error. > > What a strange world. > > Guys, what about throwing away these Mac, the promise of freedom[1] is > longtime twisted :-) > > Ok just kidding, well half-kidding. > > Hilaire > > [1] https://www.youtube.com/watch?v=2zfqw8nhUwA > > Le 09/03/2019 Ã 10:10, CÃ©drick BÃ©ler a Ã©crit : >> Hi, >> >> I tried a bit more to make DrGeo bundle works. >> >> I have Mojave (10.14) and the problem of corrupted files seems to come from Gatekeeper with prevent unsigned applications (from unknot developper) to open. >> >> Gatekeeper can be temporary stopped and then the bundle work, even when Gatekeeper is reactivated. But clearly, this is not a friendly user way of installing DrGeo. >> >> So I guess the actual (old ?) bundle procedure doesnât fit Apple politic on application security. I'm pretty sure PharoLauncher faced this already. >> >> So my question is: >> - how to make a signed bundle for OSX ? >> â do we need a real developer account ? Iâve a free one and access to a paid one. Can we do it with a general Â« pharaoh Â» account like for Pharo-Launcher ? >> >> >> Cheers, >> >> CÃ©drick > > -- > Dr. Geo > http://drgeo.eu > > >

March 12, 2019

Re: [Pharo-users] Pharo OSX bundle in Mojave - how to sign ? (Was Re: OS X bundle, some progress)

by Christophe Demarey

Hi Cedrick, > Le 9 mars 2019 Ã 10:10, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> a Ã©crit : > > Hi, > > I tried a bit more to make DrGeo bundle works. > > I have Mojave (10.14) and the problem of corrupted files seems to come from Gatekeeper with prevent unsigned applications (from unknot developper) to open. > > Gatekeeper can be temporary stopped and then the bundle work, even when Gatekeeper is reactivated. But clearly, this is not a friendly user way of installing DrGeo. > > So I guess the actual (old ?) bundle procedure doesnât fit Apple politic on application security. I'm pretty sure PharoLauncher faced this already. Yes. > So my question is: > - how to make a signed bundle for OSX ? https://github.com/demarey/pharo-launcher/tree/development/signing#how-to-s… > â do we need a real developer account ? Iâve a free one and access to a paid one. Can we do it with a general Â« pharaoh Â» account like for Pharo-Launcher ? yes, you need a (paid) developper account. See https://successfulsoftware.net/2012/08/30/how-to-sign-your-mac-os-x-app-for… I do not know if a general account for apps developed in Pharo is a good idea because it means that the reputation of all apps signed with the same certificate is shared, i.e. a security problem in one app will impact all other apps signed with the same certificate. It has to be discussed with people interested in it. Regards, Christophe.

March 12, 2019

Re: [Pharo-users] Hmmm sending at:put: to an undefined object (nil) gives a confusing error message

by Richard O'Keefe

I understand #basicAt:[put:] being in Object, but I never understood #at:[put:] being there. GNU Smalltalk: st> nil at: 1 Object: nil error: Invalid value nil: object not indexable In my Smalltalk, you get a DNU. In Squeak you get a debugger window with title Error: instances of UndefinedObject are not indexable The same for Boolean, Character, and Integer, except Squeak where (20 factorial at: 1) answers 0 (oh dear oh dear oh dear). In VW you get a "Subscript out of bounds" error, which is disappointing, as do true and $a, but a LargePositiveinteger gets #shouldNotImplement. On Tue, 12 Mar 2019 at 15:28, Tim Mackinnon <tim(a)testit.works> wrote: > If you forget to initialise a variable which you thought was a Dictionary > - you get a confusing error message: "Error: only integers should be used > as indicesâ if you try an at:put: > > This is a consequence of having at:put: defined on Object (which is a bit > nasty) > > Should UndefinedObject at least override this and signal something a bit > more obvious? This is a common and easily done thing and we don't support > it very well. > I just did it in some code, and was scratching my head initially until I > read the stack properly and realised it was something much simpler than I > thought I had done. > > Any thoughts on this? >

March 12, 2019

Calypso openOnGroup?

by HernÃ¡n Morales Durand

Hi, Is there any way to open a browser on a method group in Claypso? This was possible in Nautilus: Smalltalk tools browser openOnCategory: #compiling ofClass: Class Cheers, HernÃ¡n

March 12, 2019