Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

On Wed, Aug 2, 2017 at 2:07 AM, TedVanGaalen wrote: > Hi, > I have now tried to run Pharo 6.1 32 bit with > setting the screen resolution in > macOS System Preferences to the following > what they call "scaled resolutions" (read "non-native resolutions"), > which are less that

Re: [Pharo-users] including Pillar in Pharo image by default

Of course, I/we recognise and appreciate all the work that's gone into docs in pillar - but I think it should be reasonably straightforward to write a converter as it is pretty closely related from what I have seen. So I don't make the suggestion flippantly, and would want to help write a

Re: [Pharo-users] including Pillar in Pharo image by default

A long time issue with Markdown was that there was no standardization (and when I used Pillar's MD export ~2 years ago it didn't work well). However CommonMark ( http://spec.commonmark.org/0.28/ ) has become the de-facto standard, so it would make sense to support it bidirectionally with

Re: [Pharo-users] including Pillar in Pharo image by default

Hi, I would go both suggestions of including both support for PetitParser (Esteban's ) and Markdown (Tim's) . Having our own syntax for documentation would make us more insular. In the same way that support for Git is strategical in wider acceptance and visibility (even if we use other DVCS like

Re: [Pharo-users] FLSerializer in Pharo 6.1

I'm using flserialiser in Pharo Lambda on 64 bit, and it's working writing a context to an s3 bucket which is pretty hardcore, so I'd say it is working. So there must be some difference you have found Tim Sent from my iPhone > On 11 Aug 2017, at 20:56, Johannes Brauer

Re: [Pharo-users] including Pillar in Pharo image by default

If we are considering this, might we take the hard decision to actually support proper markdown (or even kramdown if we need more control). Pillar is a weird variant that isn't like everyone else - so i always have to think about how to do formatting. I know it's not nice, and lots of things

Re: [Pharo-users] Thread-safe initialization of class state (was Re: Threads safety in Pharo)

I think that thread safety comes with a penalty - so the overarching question is are we trying to create thread safe browsers (or does a thread safe penalty even impact browsing as maybe it's negligible?) Monty - maybe you could measure the impact if you are interested in this? If it's not

Re: [Pharo-users] FLSerializer in Pharo 6.1

Hi Stephane, I take a fresh Pharo 6.1 image, put it on my desktop (macOs 10.12.6), and then I take the example from the FLSerializer class comment: | sourceArray loadedArray | sourceArray := Array with: 'a string' with: Transcript with: [

Re: [Pharo-users] including Pillar in Pharo image by default

On Fri, Aug 11, 2017 at 09:14:01PM +0200, Esteban Lorenzano wrote: > > > On 11 Aug 2017, at 21:10, Esteban Lorenzano wrote: > > > > hi, > > > >> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. >> > wrote: > >> >

Re: [Pharo-users] including Pillar in Pharo image by default

> On 11 Aug 2017, at 21:10, Esteban Lorenzano wrote: > > hi, > >> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. > > wrote: >> >> Another step would be to get a minimal parser not relying on >> PetitParser. > >

Re: [Pharo-users] including Pillar in Pharo image by default

hi, > On 11 Aug 2017, at 18:57, Cyril Ferlicot D. wrote: > > Another step would be to get a minimal parser not relying on > PetitParser. Let’s think differently: why not to include a tiny PetitParser? Then we can think on: - pillar sintax (better than just a

Re: [Pharo-users] Thread-safe initialization of class state (was Re: Threads safety in Pharo)

Suerly we can add a Critics Rule trying to detect the invalid pattern. On Fri, Aug 11, 2017 at 10:39 AM, monty wrote: > > Sent: Friday, August 11, 2017 at 6:36 AM > > From: "Denis Kudriashov" > > To: "Any question about pharo is welcome"

Re: [Pharo-users] including Pillar in Pharo image by default

The idea is neat! Usually, I write my README.md through the interface of GitHub. But indeed, if Git and inline documentation are central to Pharo, then having a mini-pillar in the base image would make sense. Anyway, Pillar definitely needs to be improved. Everything that goes in that

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

The screen is a Samsung U28D590 3840 x 2160 @ 30Hz (max reso on intel 4000 graphics) via a Thunderbolt->DisplayPort cable. Initially not directly supported, that is, the resolution was not recognized by the OS as-is, but has been enabled with the SwitchResx app here http://www.madrau.com/ which

Re: [Pharo-users] including Pillar in Pharo image by default

What I meant is that I have a readme, e.g. https://github.com/OpenPonk/xmi , which contains * Pharo code examples * images * References to Pharo code (class names, etc.) But if the code changes (renames, API changes, different UI), I have to manually update the README. There is also no way for

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

But I'm quite convinced is more related to the screen than the macmini. At least, I will like to test in that direction. > On 11 Aug 2017, at 19:23, Stephane Ducasse wrote: > > We do not have mac minis around to test if this is related to the hardware. > > Stef > >>

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

Well, I am in Speyer, Germany, probably too far away, Although not really good in low level debugging nevertheless, if I can help in some way, please let me know! Does it run OK then on other 4/5K screen macs? TedvG www.speyer.de -- View this message in context:

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

We do not have mac minis around to test if this is related to the hardware. Stef On Fri, Aug 11, 2017 at 5:05 PM, TedVanGaalen wrote: > .. hard to imagine I am the only one with this problem? > > > > -- > View this message in context: >

Re: [Pharo-users] including Pillar in Pharo image by default

Le 11/08/2017 à 19:19, Stephane Ducasse a écrit : > Cyril > > the ** can be used to point to another class for example acting as a ref. > > Stef > > I though it would be kept for real links to web urls. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques Prévert

Re: [Pharo-users] VM dev and compilation

Hi bruno Welcome. Do not hesitate to ask questions. Stef On Fri, Aug 11, 2017 at 4:49 PM, Esteban Lorenzano wrote: > > On 11 Aug 2017, at 12:08, Bruno Durin wrote: > > Hi, > > I have been tinkering with Pharo and Squeak for a few weeks and I am very

Re: [Pharo-users] including Pillar in Pharo image by default

Cyril the ** can be used to point to another class for example acting as a ref. Stef On Fri, Aug 11, 2017 at 7:15 PM, Cyril Ferlicot D. wrote: > Le 11/08/2017 à 19:12, Cyril Ferlicot D. a écrit : >> >> We might want to add some syntax only for class comment and not

Re: [Pharo-users] FLSerializer in Pharo 6.1

Hi johannes do you have an example so that we can try here? Tx On Fri, Aug 11, 2017 at 4:06 PM, Johannes Brauer wrote: > Hi everyone, > > the FLSerializer in Pharo 6.1 doesn’t work. I tried the example from the > class comment and I always get > > FileException:

Re: [Pharo-users] including Pillar in Pharo image by default

Le 11/08/2017 à 19:12, Cyril Ferlicot D. a écrit : > > We might want to add some syntax only for class comment and not Pillar > itself. For example to be able to reference a class in Pharo and get a > link to the class during the rendering. > > I think that we might also want the formats (bold,

Re: [Pharo-users] including Pillar in Pharo image by default

Le 11/08/2017 à 19:09, Stephane Ducasse a écrit : > Tx cyril > > For class comment I image that we want > > ! > > - > - > *url* > and bold > [[[ > > ]]] > > Did I miss something. > > Stef > > > We might want to add some syntax only for class comment and not Pillar itself. For example to

Re: [Pharo-users] including Pillar in Pharo image by default

Tx cyril For class comment I image that we want ! - - *url* and bold [[[ ]]] Did I miss something. Stef On Fri, Aug 11, 2017 at 6:57 PM, Cyril Ferlicot D. wrote: > Le 11/08/2017 à 18:52, Peter Uhnak a écrit : >> Hi, >> >> I would like to propose including Pillar

Re: [Pharo-users] including Pillar in Pharo image by default

Let us rephrase it: - I would like to have a mini pillar with a simplified model and visitor to display class comments. - then think about Pharo 70 as the core and birth of a new generation of imageS I will restart to revisit Pillar once I'm done with the Lecture at Prague. Stef On Fri, Aug

Re: [Pharo-users] including Pillar in Pharo image by default

Le 11/08/2017 à 18:52, Peter Uhnak a écrit : > Hi, > > I would like to propose including Pillar in the Pharo image by default. > > My reasoning: > > Since we are moving to git, and most people will use github, gitlab, and the > likes, it is expected to include a README.md file (or possibly

[Pharo-users] including Pillar in Pharo image by default

Hi, I would like to propose including Pillar in the Pharo image by default. My reasoning: Since we are moving to git, and most people will use github, gitlab, and the likes, it is expected to include a README.md file (or possibly more extensive documentation) alongside the code. Which means

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

.. hard to imagine I am the only one with this problem? -- View this message in context: http://forum.world.st/Pharo-6-0-and-6-1-64-bit-freeze-on-MacMini-tp4957969p4960027.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

thanks for you reply, Esteban well, I can still use Pharo 5 in the mean time, no problem. how/where should I forward this to vm-dev? Regards, have a nice holiday! Ted -- View this message in context: http://forum.world.st/Pharo-6-0-and-6-1-64-bit-freeze-on-MacMini-tp4957969p4960023.html

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

> On 11 Aug 2017, at 13:48, TedVanGaalen wrote: > > since 1.8.2017 there was no response, did already anyone thought/worked to > solve this problem? > Thank you, > Ted not yet. I’m on holidays so I cannot test anything. in a couple of weeks, maybe… but I’m guessing this is

Re: [Pharo-users] VM dev and compilation

> On 11 Aug 2017, at 12:08, Bruno Durin wrote: > > Hi, > > I have been tinkering with Pharo and Squeak for a few weeks and I am very > enthusiastic with these great pieces of software! I would like to ask > questions to check my understanding. I am refering from time

Re: [Pharo-users] FLSerializer in Pharo 6.1

No, that cannot be the problem. The following works without problems: | working stream | working := FileSystem disk workingDirectory. stream := (working / 'foo.txt') writeStream. stream nextPutAll: 'Hello World'. stream close. -- View this message in context:

Re: [Pharo-users] FLSerializer in Pharo 6.1

jb wrote > Hi everyone, > > the FLSerializer in Pharo 6.1 doesn’t work. I tried the example from the > class comment and I always get > > FileException: cannot open file: example.FL. > > Is that a known problem? > > Johannes Probably that's because you don't have write permission in working

[Pharo-users] FLSerializer in Pharo 6.1

Hi everyone, the FLSerializer in Pharo 6.1 doesn’t work. I tried the example from the class comment and I always get FileException: cannot open file: example.FL. Is that a known problem? Johannes

Re: [Pharo-users] Thread-safe initialization of class state (was Re: Threads safety in Pharo)

> Sent: Friday, August 11, 2017 at 6:36 AM > From: "Denis Kudriashov" > To: "Any question about pharo is welcome" > Subject: Re: [Pharo-users] Thread-safe initialization of class state (was Re: > Threads safety in Pharo) > > What package you

Re: [Pharo-users] Thread-safe initialization of class state (was Re: Threads safety in Pharo)

> Sent: Friday, August 11, 2017 at 5:51 AM > From: "Tim Mackinnon" > To: "Any question about pharo is welcome" > Subject: Re: [Pharo-users] Thread-safe initialization of class state (was Re: > Threads safety in Pharo) > > Interesting, your example

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

since 1.8.2017 there was no response, did already anyone thought/worked to solve this problem? Thank you, Ted TedVanGaalen wrote > Very very wild guess: it could have to do with GPU<-> Open GL? <-> Pharo > call time out issues because the Intel HD 4000 GPU is working at its > (officially allowed)

Re: [Pharo-users] Thread-safe initialization of class state (was Re: Threads safety in Pharo)

What package you explore? I not find fileTypes method in Pharo 7. 2017-08-11 8:53 GMT+02:00 monty : > Here's a hypothetical broken class method that does lazy initialization of > a class inst var: > > fileTypes > fileTypes ifNil: [ > fileTypes :=

[Pharo-users] VM dev and compilation

Hi, I have been tinkering with Pharo and Squeak for a few weeks and I am very enthusiastic with these great pieces of software! I would like to ask questions to check my understanding. I am refering from time to time to Squeak as it runs on the same VM as Pharo but my questions are focused on

Re: [Pharo-users] Thread-safe initialization of class state (was Re: Threads safety in Pharo)

Interesting, your example was subtle enough that I had to read it a few times to understand the issue. (I was caught up on the ifNil and not the contents). Actually, thinking about it - isn't the real issue the #ifNil - you want an atomic version. It strikes me you could wrap the whole concept

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

This is cool Tim. So what image size you deployed at the end? 2017-08-10 15:47 GMT+02:00 Tim Mackinnon : > I just wanted to thank everyone for their help in getting my pet project > further along, so that now I can announce that PharoLambda is now working > with the V7 minimal

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

+1 Doru > On Aug 10, 2017, at 11:34 PM, Stephane Ducasse > wrote: > > Tim > > I definitively think that we could turn it into a Pharo success story > or something that we can keep on the web site > because it is really nice. > > Stef > > On Thu, Aug 10, 2017 at

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Very nice work, Tim! It is quite impressive what you could do within a short amount of time (essentially since PharoDays). Please do keep this up. Cheers, Doru > On Aug 10, 2017, at 3:47 PM, Tim Mackinnon wrote: > > I just wanted to thank everyone for their help in getting

[Pharo-users] Thread-safe initialization of class state (was Re: Threads safety in Pharo)

Here's a hypothetical broken class method that does lazy initialization of a class inst var: fileTypes fileTypes ifNil: [ fileTypes := Dictionary new. fileTypes at: 'txt' put: 'Text File'; at: 'html' put: