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

Hi Cedrick, > Le 9 mars 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. > > Ga

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

Hi Hilaire, > Le 11 mars 2019 à 21:27, Hilaire 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 p

Re: [Pharo-users] Pharo and FPGA

> Le 11 mars 2019 à 14:51, Noury Bouraqadi a écrit : > > Hi Norbert, > > The PhD of Sang (in CC) was about FPGA and Smalltalk. > https://lxsang.me/ Really cool, thanks a lot :) > > Noury > >> On 9 Mar 2019, at 15:31, Norbert Hartl wrote: >> >> I’m trying to collect i

[Pharo-users] [ANN] Minimal telepharo

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

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

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 wrote: > > I understand #basicAt:[put:] being in Object, but I never underst

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

On Tue, 12 Mar 2019 at 19:37, Norbert Hartl 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.

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

On Tue, 12 Mar 2019 at 21:56, Marcus Denker 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

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

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 earli

[Pharo-users] doWithIndex: or withIndexDo: ?

Hello, I am working on a new collection and this question caught my interest. Between doWithIndex: or withIndexDo:, which do you find more logical and why? Oleks

Re: [Pharo-users] doWithIndex: or withIndexDo: ?

I don't like either of those and use #keysAndValuesDo: as it is polymorphic with other collection classes. That said, I'd prefer #withIndexDo: [:each :index | ... ] because it preserves the #with:do: structure. e.g. #($a $b $c) with: (1 2 3) do: [:char :number | ... ] Regards, Esteban A. Maring

Re: [Pharo-users] complex json parsing.

Op 11-3-2019 om 00:03 schreef Ben Coman: On Mon, 11 Mar 2019 at 01:09, Roelof Wobben wrote:

Re: [Pharo-users] doWithIndex: or withIndexDo: ?

#doWithIndex: for me. Both because it's the selector I'm used to from other dialects, and the parameter order [:element :index | ] makes more sense to me. Cheers, Henry -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] doWithIndex: or withIndexDo: ?

Yes - I like the prefix doXXX too, as I often think first of do: for normal iteration, with suffixed selectors for other variations. > On 12 Mar 2019, at 16:54, Henrik Sperre Johansen > wrote: > > #doWithIndex: for me. > > Both because it's the selector I'm used to from other dialects, and th

Re: [Pharo-users] Smalltalk CI - anyone have any luck excluding tests?

FYI: Just bumping this - but on investigation it looks like the Pharo support for Tags breaks in Smalltalk CI - so top level packages with similar names (e.g. Exercism and ExercismWIP) all seem to get included by the include directive of ‘Exercism’ (with no wildcard). This is in an issue: https

[Pharo-users] UI Frameworks

Hi, What is the state of the various UI frameworks. I did play with Squeak many moons ago and used Morphic but I wanted something a bit higher up the food chain. I see in Pharo, Spec seems to be the built in framework for widgets but I don't see any graphics capability in there. There does

Re: [Pharo-users] Pharo 7.0 image size

Ciao, About Hilaire: > Beside the browser windows, did you close all Transcript windows? Yes. > Hi, > > I am confused by what you are reporting. I apologize, i'm trying to understand better. > > If you add 10.000 entries to the Transcript, then I don't see how

Re: [Pharo-users] complex json parsing.

On Wed, 13 Mar 2019 at 00:43, Roelof Wobben wrote: > I did try to make this idea work but now im complete lost. > > Right now the collection that should contain the objectNumbers is total empty > anyone who can see where I went wrong. > > I included my code so far. A few things... !Paintings cla

Re: [Pharo-users] complex json parsing.

Op 12-3-2019 om 18:46 schreef Ben Coman: On Wed, 13 Mar 2019 at 00:43, Roelof Wobben wrote:

Re: [Pharo-users] doWithIndex: or withIndexDo: ?

Neither. No two ways about it. #keysAndValuesDo: However, seq with: seq keys do: aBlock and seq withIndexDo: aBlock do the same thing, so #withIndexDo: makes some sense. This is not my opinion alone. I'm typing this on a machine that has Squeak but not Pharo. In Squeak we find doWithIndex

[Pharo-users] TelePharo in Tonel

Hi Denis, would it be possible to convert TelePharo to Tonel? https://github.com/pharo-ide/TelePharo Currently one gets load problem on Windows due to long file names and Tonel would solve that. Thanks T.

Re: [Pharo-users] complex json parsing.

Op 11-3-2019 om 00:03 schreef Ben Coman: getMoreData  "or a better name of your own"             | url json artObjectJson |              url := 'https://www.rijksmuseum.nl/api/nl/collection/' , objectNumber , '?key=[API_KEY]&format=json'

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

Putting public methods in Object that it cannot honestly support makes #respondsTo: pretty unreliable. It is an obsolete practice, because having Traits means that those methods can be mixed in with (part of) a single line. On Wed, 13 Mar 2019 at 03:20, Ben Coman wrote: > On Tue, 12 Mar 2019 at

Re: [Pharo-users] complex json parsing.

On Wed, 13 Mar 2019 at 02:10, Roelof Wobben wrote: > Op 12-3-2019 om 18:46 schreef Ben Coman: > > Then in Playground do... > collectionUrl := ' > https://www.rijksmuseum.nl/api/nl/collection?key=14OGzuak&format=json&type=schilderij&toppieces=True > '. > json := NeoJSONReader fromString:

Re: [Pharo-users] complex json parsing.

On Wed, 13 Mar 2019 at 04:59, Roelof Wobben wrote: > Op 11-3-2019 om 00:03 schreef Ben Coman: > > getMoreData "or a better name of your own" > | url json artObjectJson | > url := 'https://www.rijksmuseum.nl/api/nl/collection/' , > objectNumber , '?key=[API_KEY]&format=jso

[Pharo-users] [ANN] CouchDB Client for Pharo

Hello all, I finished polishing the repository a CouchDB client for Pharo that I forked from an old, and seemingly abandoned, client for VisualWorks. I took that code and refactored heavily to use Pharo and Zinc core classes, and that included renaming the client classes, methods and the strategy

[Pharo-users] PharoLauncher Baseline Templates

Recently I was asked about moving personal projects between images to keep up with latest Pharo 8 development version. My suggestion was of course creating a Baseline to load into each fresh Image. This morning I was contemplating that further and what would be cool is in PharoLauncher being able

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

On 12/03/19 9:25 AM, Richard O'Keefe wrote: Squeak where (20 factorial at: 1) answers 0 (oh dear oh dear oh dear). Richard, Could you please elaborate on why this is an error? Large integers are place value encoded (base 256 little endian) and stored in byte arrays, so they need #at:/#at:put

Re: [Pharo-users] UI Frameworks

Bob Cowdery writes: > I also found Block and Brick which say they are next generation, Block > being for graphics and  Brick for widgets. These are not yet in Pharo > and again I couldn't find any info although there is a tutorial for > Block but not for Brick. Having forgotten most everything