Le 06/03/2018 à 11:55, Guillermo Polito a écrit :
In any case, I only wanted to say that it is unfair to say that Pharo
is big when "you only load your packages".
And I feel that's not true, if you're using the graphical environment,
you need display, bitblt, morphic, widgets.
As soon as you n
Hey guys after my mistake we got "hacked" and someone banned all our
members in Discord
I have revoked all the bans but you will have to rejoin . Existing join
links are still valid , if you dont have one here is one
https://discord.gg/gtKeHne
My apologies for this inconvenience, I am still expl
On 10 March 2018 at 00:13, Siemen Baader wrote:
>
>
> On Fri, Mar 9, 2018 at 8:02 AM, Ben Coman wrote:
>
>> thx for looking into this. half way there ;)
>> do you have the Pharo build numbers that match these Nautilus versions?
>>
>
> I don't. PharoLauncher didn't work for me, when I try to lau
I think the roles got changed I am no longer admin (Note that it does not
really matter since I did not do much admin work but still)
On Sat, Mar 10, 2018 at 11:48 AM, Dimitris Chloupis
wrote:
> Hey guys after my mistake we got "hacked" and someone banned all our
> members in Discord
>
> I have
yes, please rejoin Discord you too ;)
> Begin forwarded message:
>
> From: Dimitris Chloupis
> Subject: [Pharo-dev] Please rejoin Discord
> Date: 10 March 2018 at 11:51:47 CET
> To: Pharo Development List
> Reply-To: Pharo Development List
>
>
> Hey guys after my mistake we got "hacked" and
Same here, no more admin
On Sat, Mar 10, 2018 at 12:15 PM, Clément Bera
wrote:
> I think the roles got changed I am no longer admin (Note that it does not
> really matter since I did not do much admin work but still)
>
> On Sat, Mar 10, 2018 at 11:48 AM, Dimitris Chloupis > wrote:
>
>> Hey guys
Hmm thats weird that you guys lost your admin roles, but not entirely,
maybe the hack is responsible, no problem will add you back.
I removed the authorisation of any third party apps and I am closing any
potential security hole. I think I got them all covered but will stick
around and keep owners
Hello
In Squeak and the dialect independent FileMan [1] there is
FileDirectory
assureExistence
"Make sure the current directory exists. If necessary, create all
parts in between"
What is the equivalent Pharo method? BTW is there a cheat sheet for
FileSystem operations in
Probably #ensureCreateDirectory
> On 10 Mar 2018, at 21:01, H. Hirzel wrote:
>
> Hello
>
> In Squeak and the dialect independent FileMan [1] there is
>
>
>FileDirectory
> assureExistence
> "Make sure the current directory exists. If necessary, create all
> parts in between
On sam. 10 mars 2018 at 21:02, H. Hirzel wrote:
> Hello
>
> In Squeak and the dialect independent FileMan [1] there is
>
>
> FileDirectory
>assureExistence
> "Make sure the current directory exists. If necessary, create
> all
> parts in between"
>
>
> What is the equivalen
>
> There is #ensureCreateDirectory in Pharo but I don't know if it will check
> the parents exists. (And I don't have a Pharo image to check.
>
It will, at least on Windows.
Peter
Yes, #ensureCreateDirectory is available.
I'd like to make sure a directory 'public' is available as a sibling
directory of the working directory (the directory where the Pharo
image is in)
However
FileSystem disk workingDirectory / '../public' ensureCreateDirectory
does not work as
F
On sam. 10 mars 2018 at 21:36, H. Hirzel wrote:
> Yes, #ensureCreateDirectory is available.
>
> I'd like to make sure a directory 'public' is available as a sibling
> directory of the working directory (the directory where the Pharo
> image is in)
>
> However
>
> FileSystem disk workingDirect
Operator priority :); unary messages `#ensureCreateDirectory have
precedence over binary `#/`
(FileSystem disk workingDirectory / '../public') ensureCreateDirectory.
Also please note that the workingDirectory should be based on where Pharow
as launched from, if you are looking for the image direc
I note that 'workingDirectory' is the directory where Pharo is
launched from. In my case it happens to be the same where the image is
in but that cannot be assumed generally.
So
(FileSystem workingDirectory / '..' / 'public') ensureCreateDirectory
Worked fine.
Thanks to all!
--Hannes
On
On sam. 10 mars 2018 at 21:49, H. Hirzel wrote:
> I note that 'workingDirectory' is the directory where Pharo is
> launched from. In my case it happens to be the same where the image is
> in but that cannot be assumed generally.
The fact that "workingDirectory" point to the folder from where Ph
16 matches
Mail list logo