Re: [Pharo-users] A strange iceberg/Monticello loading issue that has appeared in 7.0.2?

Reported as https://github.com/pharo-project/pharo/issues/2854 (although there was a similar issue already from P6, but I don’t think it made it clear enough the seriousness of this problem). > On 16 Mar 2019, at 22:08, Tim Mackinnon

Re: [Pharo-users] A strange iceberg/Monticello loading issue that has appeared in 7.0.2?

ARRRGG - its the damn settings file! I recall now, I changed some of the code formatter settings in the 7.0.2, and was using the blue-ink preview in settings, and must have pressed save. Even thought, it was only formatter settings that I changed - the damn file causes iceberg to break

Re: [Pharo-users] json parse problem

Op 16-3-2019 om 22:24 schreef Sven Van Caekenberghe: imageUrl1 := levelsJson detect: [ :item | item name = 'z4' ]. imageUrl := imageUrl1 tiles first url. Thanks I used NeoJsonReader. After chancing it to NeoJsonObject It worked. I think I can do the same here : json := NeoJSONReader

Re: [Pharo-users] A strange iceberg/Monticello loading issue that has appeared in 7.0.2?

Hmmm - hang on a second, something very weird is going on - looking at how to track where files get written on OSX and using: touch ~/timestamp find -x / -newer ~/timestamp >~/changedfiles.txt The result is that when I do my zero conf install - my files now seem to be going to the 7.0.2 install

Re: [Pharo-users] A strange iceberg/Monticello loading issue that has appeared in 7.0.2?

Hi Sean - thanks for chipping in: Yes - the correct packages are loading, the baseline is fine (and its a baseline I’ve been using without issues for a while) - its simply just not loading the same source as if I do a clone by hand via git in a separate directory? It’s like iceberg just

Re: [Pharo-users] json parse problem

> On 16 Mar 2019, at 21:17, Roelof Wobben wrote: > > Op 16-3-2019 om 18:16 schreef Sven Van Caekenberghe: >> imageUrl1 := levelsJson detect: [ :item | item name = 'z4' ]. >> imageUrl := imageUrl1 tiles first url. >> > > > nope, > > when I do this I see this error messsage : > >

Re: [Pharo-users] json parse problem

Op 16-3-2019 om 18:16 schreef Sven Van Caekenberghe: imageUrl1 := levelsJson detect: [ :item | item name = 'z4' ]. imageUrl := imageUrl1 tiles first url. nope, when I do this I see this error messsage :

Re: [Pharo-users] Calypso question: adding a context menu item

Juraj Kubelka wrote > To implement a context menu item Just in case someone stumbles on this thread with a similar problem… Much has changed in Calypso and dependencies, making this snippet obsolete. After struggling to port to latest, API, the easiest way to find out how to do this seems to be

Re: [Pharo-users] A strange iceberg/Monticello loading issue that has appeared in 7.0.2?

Tim Mackinnon wrote > Can anyone think of what might cause this? I’m really confused. Am I understanding correctly that your load script is loading the correct packages, but not the latest versions? If so, just a few initial thoughts: - What does the local clone look like after the load (i.e.

Re: [Pharo-users] 7.0.2 and the font glitch - seems far worse than 7.0.1

Tim Mackinnon wrote > it seems that this smallish combination of projects really triggers it > quickly and reliably Can you share the load script? - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] json parse problem

> On 16 Mar 2019, at 16:32, Ben Coman wrote: > > > > On Sat, 16 Mar 2019 at 23:29, Roelof Wobben wrote: > oke, > > how do I then get the url of the line where the name is z4. > > I haven't directly tested, but probably... > imageUrl1 := levelsJson detect: [ :item | (item at: #name) =

Re: [Pharo-users] A strange iceberg/Monticello loading issue that has appeared

OK - I can rule out 7.0.2 for the iceberg loading, as doing it in a 7.0.1 image has the same issue - it doesn’t load the full repo that is showing in GitHub - and leaves me needing to do an extra pull? I don’t understand why I need the extra pull step? I think there is something obvious that

Re: [Pharo-users] json parse problem

oke, then I misunderstood you. I thought it could be done in one step. but detect instead of select works. Roelof Op 16-3-2019 om 16:32 schreef Ben Coman:

Re: [Pharo-users] json parse problem

On Sat, 16 Mar 2019 at 23:29, Roelof Wobben wrote: > oke, > > how do I then get the url of the line where the name is z4. > I haven't directly tested, but probably... imageUrl1 := levelsJson detect: [ :item | (item at: #name) = 'z4' ]. imageUrl := ((imageUrl1 at: #tiles) at: 1) at: #url cheers

Re: [Pharo-users] json parse problem

oke, how do I then get the url of the line where the name is z4. I need that because I need that line and then the tiles part which is also a collection and then the url part which also is a part of a collection Roelof

Re: [Pharo-users] json parse problem

On Sat, 16 Mar 2019 at 17:05, Roelof Wobben wrote: > Thanks, > > With your hint I solved it this way : > > imageUrl1 := levelsJson select: [ :item | (item at: #name) = 'z4' ]. > imageUrl := (((imageUrl1 at: 1) at: #tiles) at: 1) at: #url > Cool. Minor tweak... if you use #detect: instead of

Re: [Pharo-users] Why doesn't collection have #excludes (the mirror of includes)?

On Sat, 16 Mar 2019 at 17:05, Tim Mackinnon wrote: > These are all good suggestions guys - but don’t you find it odd that there > isn’t the mirror function #excludes: which would make all of them read more > naturally? > > I know we can’t have all combinations- but this one really struck me as >

Re: [Pharo-users] LibC experiments in Pharo 7

--- Begin Message --- Excellent! How does it compare with OSSubProcess? LibC looks much lighter. Alexandre Envoyé de mon iPad > Le 16 mars 2019 à 08:50, Christopher Fuhrman > a écrit : > > I wrote a blog entry about how I've used LibC in Pharo 7. > >

Re: [Pharo-users] LibC experiments in Pharo 7

This is useful, thank you! > On 16 Mar 2019, at 12:50, Christopher Fuhrman > wrote: > > I wrote a blog entry about how I've used LibC in Pharo 7. > > https://fuhrmanator.github.io/LibC-Pharo-experiments/ > > Cheers! > > Christopher

Re: [Pharo-users] A strange iceberg/Monticello loading issue that has appeared in 7.0.2?

Mulling this over - I have a few more experiments to try 1 - try loading from the playground and not the cmd line 2 - dig out a previous 7.0.1 zero conf image (that previously worked with an older master branch), clean out iceberg-local and see if it’s something in the new master that causes

[Pharo-users] LibC experiments in Pharo 7

I wrote a blog entry about how I've used LibC in Pharo 7. https://fuhrmanator.github.io/LibC-Pharo-experiments/ Cheers! Christopher

Re: [Pharo-users] 7.0.2 and the font glitch - seems far worse than 7.0.1

Hi Hilaire - I'm not changing any font settings at all - this is a clean zero conf image, load my project, open a system browser and start typing some code and it starts happening quite quickly. The only thing that might exasperate this is me loading in mirage after my project (I need to test

Re: [Pharo-users] 7.0.2 and the font glitch - seems far worse than 7.0.1

This problem also randomly shows up in Dr.Geo/Linux. I think I saw it recently in DrGeo build with P7.0.1 or P7.0.2. Tim, did you use an alternate true type font for your Pharo GUI? Until know I though the issue was related to the FreeType plugin and the use of true type font in the UI.

[Pharo-users] A strange iceberg/Monticello loading issue that has appeared in 7.0.2?

I’m really struggling a bit with new images in 7.0.2. Now it may be that it’s not .2’s fault - but as I’ve been doing lots of repeatable things in Pharo 6 and 7a and 7.0.1, you notice when things change. I’d really appreciate some thoughts on an iceberg/Monticello issue i suddenly hit last

Re: [Pharo-users] Why doesn't collection have #excludes (the mirror of includes)?

These are all good suggestions guys - but don’t you find it odd that there isn’t the mirror function #excludes: which would make all of them read more naturally? I know we can’t have all combinations- but this one really struck me as odd by its absence (particularly when I was comparing the

Re: [Pharo-users] 7.0.2 and the font glitch - seems far worse than 7.0.1

Thanks for a confirmation - I’m not sure if Mirage uses any native code, I’ll look - and will load up an image without it (possibly it is triggering something - as I know it has a background process that updates thumbnails to use for window switching). My other package is OSProcess (that I

Re: [Pharo-users] Why doesn't collection have #excludes (the mirror of includes)?

> On 15 Mar 2019, at 23:06, Tim Mackinnon wrote: > > aString detect: [:c | ($0 to: $1) excludes: c] ifFound: aBlock. (Evaluate a > block if the string isn’t all 0 and 1’s) (aString allSatisfy: [ :each | '01' includes: each ]) not.

Re: [Pharo-users] 7.0.2 and the font glitch - seems far worse than 7.0.1

I am on the latest macOS, my 64-bit 7.0.2 image with lots of code (Bootstrap/Seaside/...) is running fine. I did not fiddle with the fonts, just switched to Dark look. I avoid loading any packages that use native code, unless it is very well proven and/or part of the standard image (IceBerg