Smalltalk › Pharo › Pharo Smalltalk Developers

PharoLauncher feedback

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

Stephane Ducasse-3

PharoLauncher feedback

Hi christophe

I took the bleeding edge and here are my report.

- We need a signed VM because the security on mac is getting in our way.

- I got PrimitiveFailed: CreatedDirectory in MacStore failed.
So I do not know what to do :(

I do not get why I cannot write on my download folder ;( but this
error should be caught.

- Pharo.app should be renamed PharoLauncher

- the Quit menu is showing SqueakOSXApp and the about too.

- There is a template 7.0 (beta) but it does not exist below Pharo60
We should not have Pharo 60 but Pharo 6.1

else it seems to work.

well no :)
I downloaded Pharo70 alpha and I got a problem with FT2Error primitive failed.
May be this is normal. I do not know.

Stef

Peter Uhnak

Re: PharoLauncher feedback

We should not have Pharo 60 but Pharo 6.1

It says 60, but it does download 61 (and 61 VM)... and in the end there's no official version 61; the image still says 60.

Peter

Sean P. DeNigris

Re: PharoLauncher feedback

Administrator

In reply to this post by Stephane Ducasse-3

Stephane Ducasse-3 wrote
> - We need a signed VM because the security on mac is getting in our way.
>
> - I got PrimitiveFailed: CreatedDirectory in MacStore failed.

IIRC they are related and you have to move the app into your Applications
folder

-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Cheers,
Sean

demarey

Re: PharoLauncher feedback

In reply to this post by Stephane Ducasse-3

Hi Stéphane,

> Le 22 sept. 2017 à 20:34, Stephane Ducasse <[hidden email]> a écrit :
>
> Hi christophe
>
> I took the bleeding edge and here are my report.
>
> - We need a signed VM because the security on mac is getting in our way.

Right. It is not directly related to the launcher. Pharo binaries need to be signed.
OS packaging scripts are shared (launcher, std pharo distribution).

> - I got PrimitiveFailed: CreatedDirectory in MacStore failed.
> So I do not know what to do :(
>
> I do not get why I cannot write on my download folder ;( but this
> error should be caught.
>
> - Pharo.app should be renamed PharoLauncher
> - the Quit menu is showing SqueakOSXApp and the about too.

This two points are not easy because they are related to how the VM is built.
I tried to use Alien and OS X integration to change menus at runtime but it takes time as I do not know a lot on OS X api.
We should put that on the TODO list.

> - There is a template 7.0 (beta) but it does not exist below Pharo60
> We should not have Pharo 60 but Pharo 6.1

fixed

> else it seems to work.
>
> well no :)
> I downloaded Pharo70 alpha and I got a problem with FT2Error primitive failed.
> May be this is normal. I do not know.

Not sure you tested the latest version.
I did a lot of improvements (especially for Linux) on the launcher to ensure the environment you get when forking from the launcher process is clean (setting the working dir and clean env variable set by the VM used by the launcher).
It should be fine now.

Stephane Ducasse-3

Re: PharoLauncher feedback

Tx I loved the launcher!

On Fri, Sep 29, 2017 at 3:50 PM, Christophe Demarey
<[hidden email]> wrote:

> Hi Stéphane,
>
>> Le 22 sept. 2017 à 20:34, Stephane Ducasse <[hidden email]> a écrit :
>>
>> Hi christophe
>>
>> I took the bleeding edge and here are my report.
>>
>> - We need a signed VM because the security on mac is getting in our way.
>
> Right. It is not directly related to the launcher. Pharo binaries need to be signed.
> OS packaging scripts are shared (launcher, std pharo distribution).
>
>> - I got PrimitiveFailed: CreatedDirectory in MacStore failed.
>> So I do not know what to do :(
>>
>> I do not get why I cannot write on my download folder ;( but this
>> error should be caught.
>>
>> - Pharo.app should be renamed PharoLauncher
>> - the Quit menu is showing SqueakOSXApp and the about too.
>
> This two points are not easy because they are related to how the VM is built.
> I tried to use Alien and OS X integration to change menus at runtime but it takes time as I do not know a lot on OS X api.
> We should put that on the TODO list.
>
>> - There is a template 7.0 (beta) but it does not exist below Pharo60
>> We should not have Pharo 60 but Pharo 6.1
>
> fixed
>
>> else it seems to work.
>>
>> well no :)
>> I downloaded Pharo70 alpha and I got a problem with FT2Error primitive failed.
>> May be this is normal. I do not know.
>
> Not sure you tested the latest version.
> I did a lot of improvements (especially for Linux) on the launcher to ensure the environment you get when forking from the launcher process is clean (setting the working dir and clean env variable set by the VM used by the launcher).
> It should be fine now.
>
>