Re: [Pharo-users] Running test

2019-02-07 Thread john pfersich
Yeah, I’m running DrGeo from Applications. Trying open gives you the same 
result. Yes, Mojave security is a PITA. But other apps downloaded from the web 
don’t have this problem. But I don’t develop on the Mac because of Apple’s 
paranoid behavior.  I’ll stick to Unix, thanks. 

/*—-*/
Sent from my iPhone
https://boincstats.com/signature/-1/user/51616339056/sig.png
See https://objectnets.net and https://objectnets.org

> On Feb 7, 2019, at 18:25, Sean P. DeNigris  wrote:
> 
> Are you running from /Applications? You might also have to right click and
> select open instead of double clicking. Mac security can make it a bit of a
> PITA
> 
> 
> 
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> 



Re: [Pharo-users] Running test

2019-02-07 Thread Sean P. DeNigris
Are you running from /Applications? You might also have to right click and
select open instead of double clicking. Mac security can make it a bit of a
PITA



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



Re: [Pharo-users] Formatting Dates

2019-02-07 Thread Eduardo de Oliveira Padoan
Seems like the method it ends up using, Date>>printDate:format:on:,
currently ignores the formatArray given and just prints using -MM-DD.

But there's a ExrendedDatePrinter class that implements the same method and
does what you expect.

I found it using ctrl-m when selecting the expression and looking at the
implementations, but I haven't used it to be sure.

On Wed, Feb 6, 2019 at 6:17 PM sergio ruiz  wrote:

> I have been using this to format dates:
>
> printFormat: #(3 2 1 $/ 1 1 2)
>
> which goes like:
>
> printFormat: formatArray
> "Answer a String describing the receiver using the argument formatArray."
>
> ^ String
> new: 16
> streamContents: [ :aStream | self printOn: aStream format: formatArray ]
>
> But i am unclear on how to assemble this formatArray to get a date like:
>
> mm/dd/
>
> any ideas?
>
> Thanks!
>
> 
> peace,
> sergio
> photographer, journalist, visionary
>
> Public Key: http://bit.ly/29z9fG0
> #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
> http://www.codeandmusic.com
> http://www.twitter.com/sergio_101
> http://www.facebook.com/sergio101
>


-- 
 Eduardo de Oliveira Padoan ⋮)


[Pharo-users] RBPattern syntax

2019-02-07 Thread Manuel Leuenberger
Hi,

I am looking into the RB pattern language for refactoring and I am having 
trouble matching and replacing non-trivial pattern. Given the following 
excerpt, I want to match "b shape ." and replace it with "b shape: [ :x | 
x  ]"

b shape circle
size: 15;
color: (Color veryLightGray alpha: 0.4);
if: [ :value | toBeRed includes: value ] fillColor: Color red.

How can I do this? I tried using "b shape ``@messages", but this only matches 
"b shape circle". Using "b shape `message `;middle; `;last" for some reason 
then also matches the following, which I think it should not:

b edges
moveBehind;
connectToAll: [ :v | 
v \\ 20 ~~ 0
ifTrue: [ Array with: v + 1 with: v + 20 ]
ifFalse: [ Array with: v + 20 ] ].

There seems not be too much documentation about the pattern language, only 
found tests, some short help description from RB and Yuriy's MatchTool.
How can I match the node correctly?

Cheers,
Manuel




Re: [Pharo-users] Running test

2019-02-07 Thread Hilaire
So beside the signing problem, I have a problem with the OS X vm. The
error is the same I got from the Linux VM referenced in the Pharo
download page... I think someone should double check these VMs are ok or
not.

I will check again the mac os vm in these drgeo bundle.

Hilaire


Le 07/02/2019 à 12:15, Andrei Chis a écrit :
> I tried the following:
> - download DrGeo.app-19.03a.zip
>  from
> the web browser, place it in Application and remove _CodeSignature;
> then it still appears as broken.
> - download DrGeo.app-19.03a.zip
>  using
> wget, place it in Applications and remove _CodeSignature: then it
> opens and asks for an image.
>
> But if I open it I get an error related to libgit.
>
> For DrGeo.app-18.06a.zip
>  I
> get the warning that it is from an unidentified developer but it works
> fine if I place it in the application folder.

-- 
Dr. Geo
http://drgeo.eu





Re: [Pharo-users] Running test

2019-02-07 Thread Hilaire
What is Smalltalk CI? Related to Chistophe?

Thanks

Le 07/02/2019 à 12:05, Tim Mackinnon a écrit :
> I think this is where having a build pipeline might be worth investigating - 
> I think Smalltalk CI might let you automatically build on different machines, 
> such that you can package each build on its native environment in an 
> automated fashion. Maybe Christophe might chip in about how he builds Pharo 
> Launcher? If you can make it automated and based on your git repo - it should 
> simplify a lot for you, and make reliable builds much easier. (If not 
> Smalltalk CI, then there might be others you can use)
>
> Tim

-- 
Dr. Geo
http://drgeo.eu





Re: [Pharo-users] Running test

2019-02-07 Thread Tim Mackinnon


> On 7 Feb 2019, at 11:15, Andrei Chis  wrote:
> 
> To sign an app you need to use MacOS as you need some xcode tool from what I 
> remember.

Its worth checking with Christophe, as he may have automated this (there are 
tools that can do it - I recall). If Smalltalk CI can’t do it - then something 
like DrGeo might benefit from something like: 
https://azure.microsoft.com/en-gb/services/devops/pipelines/?=AID736752_SEM_bclv8aYq
 


Free for open source - does linux, windows, osx build pipelines - presumably 
you can automate this once and for all and save yourself some of this hassle. 
It seems to suck a lot of your time from the fun stuff otherwise.

Tim

Re: [Pharo-users] Running test

2019-02-07 Thread Tim Mackinnon
I think this is where having a build pipeline might be worth investigating - I 
think Smalltalk CI might let you automatically build on different machines, 
such that you can package each build on its native environment in an automated 
fashion. Maybe Christophe might chip in about how he builds Pharo Launcher? If 
you can make it automated and based on your git repo - it should simplify a lot 
for you, and make reliable builds much easier. (If not Smalltalk CI, then there 
might be others you can use)

Tim

> On 7 Feb 2019, at 09:40, Hilaire  wrote:
> 
> Can signing the bundle content be done from Linux? Or is it mandatory to
> do it from OS X?
> 
> From what I looked at the Linux Pharo Launcher, I can only fetch image
> and associated VM for Linux but I may have miss something.
> 
> Hilaire
> 
> 
> Le 06/02/2019 à 21:41, Tim Mackinnon a écrit :
>> For OS X (and possibly Windows) it’s worth understanding how Pharo
>> Launcher creates its installation program as that’s the way to solve
>> this properly and it makes it look much more polished as well.
>> 
>> I think it’s not too hard too do, and you can copy those steps?
>> 
> -- 
> Dr. Geo
> http://drgeo.eu
> 
> 
> 




Re: [Pharo-users] Running test

2019-02-07 Thread Hilaire
Ok, one more thing that could be helpful to try and to give me
indication: remove the folder DrGeo.app/Contents/_CodeSignature and
start again DrGeo.app from the Application folder.

What OS X says?

Thanks

Le 06/02/2019 à 22:02, john pfersich a écrit :
> Yes before I tried to start it. 
>
-- 
Dr. Geo
http://drgeo.eu





Re: [Pharo-users] Running test

2019-02-07 Thread Hilaire
...then look at how signing the functionnal bundle.

The 18.06 bundle[1] is not signed and from feedback I got it can start
once dragged in the Application folder.

[1] https://launchpad.net/drgeo/trunk/18.06/+download/DrGeo.app-18.06a.zip


-- 
Dr. Geo
http://drgeo.eu





Re: [Pharo-users] Running test

2019-02-07 Thread Hilaire
I get another different feedback, while not good, it exposes a plugin error.

https://twitter.com/gl_4/status/1093004875733106688

First should be to get a starting app with signature warning, then

Le 06/02/2019 à 22:02, john pfersich a écrit :
> Yes before I tried to start it. 
>
-- 
Dr. Geo
http://drgeo.eu





Re: [Pharo-users] Running test

2019-02-07 Thread Hilaire
Can signing the bundle content be done from Linux? Or is it mandatory to
do it from OS X?

>From what I looked at the Linux Pharo Launcher, I can only fetch image
and associated VM for Linux but I may have miss something.

Hilaire


Le 06/02/2019 à 21:41, Tim Mackinnon a écrit :
> For OS X (and possibly Windows) it’s worth understanding how Pharo
> Launcher creates its installation program as that’s the way to solve
> this properly and it makes it look much more polished as well.
>
> I think it’s not too hard too do, and you can copy those steps?
>
-- 
Dr. Geo
http://drgeo.eu





Re: [Pharo-users] Why DirectoryIsNotEmpty on FileReference>>deleteAll ?

2019-02-07 Thread Albrecht Baur via Pharo-users
--- Begin Message ---

it is not urgent for me - I have a workaround.

So for me it can wait until the next stable is released.

Albrecht


On 07.02.19 09:58, Alistair Grant wrote:

Hi Esteban,

On Thu, 7 Feb 2019 at 09:41, Esteban Lorenzano  wrote:

Means we will need a new stable for Pharo 7/8 ?

Esteban

Albrecht will obviously be the one to say how urgent it is for him, or
whether he can get by with vmLatest80.  From my perspective: the issue
has been there "forever" (2010 or earlier) and has only just been
reported.  I expect that we'll eventually update the Pharo 7 VM
anyway, and this can probably wait until then.  Pharo 8 can wait as
well, for the same reasons.

Cheers,
Alistair




On 7 Feb 2019, at 09:23, Alistair Grant  wrote:

On Thu, 7 Feb 2019 at 09:08, Albrecht Baur  wrote:

Hi Alistair,

I have tested it and works with the latest VM.

Great, thanks for the confirmation.

Cheers,
Alistair




thanks,

Albrecht

On 07.02.19 07:56, Alistair Grant wrote:

Hi Albrecht,

On Wed, 6 Feb 2019 at 19:51, Albrecht Baur via Pharo-users
 wrote:

thank you! That is good news.

best,

Albrecht

Would you please download the latest VM and confirm that it resolves the issue:

curl get.pharo.org/64/vmLatest80 | bash

The Pharo 8 VM works with Pharo 7 images.

Thanks,
Alistair



On 06.02.19 09:34, Alistair Grant wrote:

Hi Albrecht,

On Tue, 5 Feb 2019 at 15:26, Albrecht Baur  wrote:

Hi Alistair,

here the system report output:

...

Thanks for the info.  Please see:

Issue: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/368
PR: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/371

Assuming the CI build passes, I'll wait a day or so to give the VM
guys a chance to review the changes and comment before merging.

Cheers,
Alistair





--- End Message ---


Re: [Pharo-users] Why DirectoryIsNotEmpty on FileReference>>deleteAll ?

2019-02-07 Thread Alistair Grant
Hi Esteban,

On Thu, 7 Feb 2019 at 09:41, Esteban Lorenzano  wrote:
>
> Means we will need a new stable for Pharo 7/8 ?
>
> Esteban

Albrecht will obviously be the one to say how urgent it is for him, or
whether he can get by with vmLatest80.  From my perspective: the issue
has been there "forever" (2010 or earlier) and has only just been
reported.  I expect that we'll eventually update the Pharo 7 VM
anyway, and this can probably wait until then.  Pharo 8 can wait as
well, for the same reasons.

Cheers,
Alistair



> > On 7 Feb 2019, at 09:23, Alistair Grant  wrote:
> >
> > On Thu, 7 Feb 2019 at 09:08, Albrecht Baur  
> > wrote:
> >>
> >> Hi Alistair,
> >>
> >> I have tested it and works with the latest VM.
> >
> > Great, thanks for the confirmation.
> >
> > Cheers,
> > Alistair
> >
> >
> >
> >> thanks,
> >>
> >> Albrecht
> >>
> >> On 07.02.19 07:56, Alistair Grant wrote:
> >>> Hi Albrecht,
> >>>
> >>> On Wed, 6 Feb 2019 at 19:51, Albrecht Baur via Pharo-users
> >>>  wrote:
>  thank you! That is good news.
> 
>  best,
> 
>  Albrecht
> >>> Would you please download the latest VM and confirm that it resolves the 
> >>> issue:
> >>>
> >>> curl get.pharo.org/64/vmLatest80 | bash
> >>>
> >>> The Pharo 8 VM works with Pharo 7 images.
> >>>
> >>> Thanks,
> >>> Alistair
> >>>
> >>>
>  On 06.02.19 09:34, Alistair Grant wrote:
> > Hi Albrecht,
> >
> > On Tue, 5 Feb 2019 at 15:26, Albrecht Baur 
> >  wrote:
> >> Hi Alistair,
> >>
> >> here the system report output:
> >>
> >> ...
> > Thanks for the info.  Please see:
> >
> > Issue: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/368
> > PR: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/371
> >
> > Assuming the CI build passes, I'll wait a day or so to give the VM
> > guys a chance to review the changes and comment before merging.
> >
> > Cheers,
> > Alistair
> >
> >
>
>



Re: [Pharo-users] Why DirectoryIsNotEmpty on FileReference>>deleteAll ?

2019-02-07 Thread Esteban Lorenzano
Means we will need a new stable for Pharo 7/8 ?

Esteban

> On 7 Feb 2019, at 09:23, Alistair Grant  wrote:
> 
> On Thu, 7 Feb 2019 at 09:08, Albrecht Baur  
> wrote:
>> 
>> Hi Alistair,
>> 
>> I have tested it and works with the latest VM.
> 
> Great, thanks for the confirmation.
> 
> Cheers,
> Alistair
> 
> 
> 
>> thanks,
>> 
>> Albrecht
>> 
>> On 07.02.19 07:56, Alistair Grant wrote:
>>> Hi Albrecht,
>>> 
>>> On Wed, 6 Feb 2019 at 19:51, Albrecht Baur via Pharo-users
>>>  wrote:
 thank you! That is good news.
 
 best,
 
 Albrecht
>>> Would you please download the latest VM and confirm that it resolves the 
>>> issue:
>>> 
>>> curl get.pharo.org/64/vmLatest80 | bash
>>> 
>>> The Pharo 8 VM works with Pharo 7 images.
>>> 
>>> Thanks,
>>> Alistair
>>> 
>>> 
 On 06.02.19 09:34, Alistair Grant wrote:
> Hi Albrecht,
> 
> On Tue, 5 Feb 2019 at 15:26, Albrecht Baur  
> wrote:
>> Hi Alistair,
>> 
>> here the system report output:
>> 
>> ...
> Thanks for the info.  Please see:
> 
> Issue: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/368
> PR: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/371
> 
> Assuming the CI build passes, I'll wait a day or so to give the VM
> guys a chance to review the changes and comment before merging.
> 
> Cheers,
> Alistair
> 
> 




Re: [Pharo-users] Why DirectoryIsNotEmpty on FileReference>>deleteAll ?

2019-02-07 Thread Alistair Grant
On Thu, 7 Feb 2019 at 09:08, Albrecht Baur  wrote:
>
> Hi Alistair,
>
> I have tested it and works with the latest VM.

Great, thanks for the confirmation.

Cheers,
Alistair



> thanks,
>
> Albrecht
>
> On 07.02.19 07:56, Alistair Grant wrote:
> > Hi Albrecht,
> >
> > On Wed, 6 Feb 2019 at 19:51, Albrecht Baur via Pharo-users
> >  wrote:
> >> thank you! That is good news.
> >>
> >> best,
> >>
> >> Albrecht
> > Would you please download the latest VM and confirm that it resolves the 
> > issue:
> >
> > curl get.pharo.org/64/vmLatest80 | bash
> >
> > The Pharo 8 VM works with Pharo 7 images.
> >
> > Thanks,
> > Alistair
> >
> >
> >> On 06.02.19 09:34, Alistair Grant wrote:
> >>> Hi Albrecht,
> >>>
> >>> On Tue, 5 Feb 2019 at 15:26, Albrecht Baur  
> >>> wrote:
>  Hi Alistair,
> 
>  here the system report output:
> 
>  ...
> >>> Thanks for the info.  Please see:
> >>>
> >>> Issue: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/368
> >>> PR: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/371
> >>>
> >>> Assuming the CI build passes, I'll wait a day or so to give the VM
> >>> guys a chance to review the changes and comment before merging.
> >>>
> >>> Cheers,
> >>> Alistair
> >>>



Re: [Pharo-users] Why DirectoryIsNotEmpty on FileReference>>deleteAll ?

2019-02-07 Thread Albrecht Baur via Pharo-users
--- Begin Message ---

Hi Alistair,

I have tested it and works with the latest VM.

thanks,

Albrecht

On 07.02.19 07:56, Alistair Grant wrote:

Hi Albrecht,

On Wed, 6 Feb 2019 at 19:51, Albrecht Baur via Pharo-users
 wrote:

thank you! That is good news.

best,

Albrecht

Would you please download the latest VM and confirm that it resolves the issue:

curl get.pharo.org/64/vmLatest80 | bash

The Pharo 8 VM works with Pharo 7 images.

Thanks,
Alistair



On 06.02.19 09:34, Alistair Grant wrote:

Hi Albrecht,

On Tue, 5 Feb 2019 at 15:26, Albrecht Baur  wrote:

Hi Alistair,

here the system report output:

...

Thanks for the info.  Please see:

Issue: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/368
PR: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/371

Assuming the CI build passes, I'll wait a day or so to give the VM
guys a chance to review the changes and comment before merging.

Cheers,
Alistair



--- End Message ---