[Pharo-users] Where do we go now ?

[Benoit St-Jean via Pharo-users]

--- Begin Message ---
Hello guys,

Just a quick word to get some things straight because, quite frankly, I really 
don't know where we're heading.

When Pharo started, the goal was to depart from Squeak and do a *major clean 
up* of all the code, especially Morphic.  The promise of a new, clean & lean 
Smalltalk attracted a lot of people.  And then...

I'm looking at the Pharo 7.0 image right now and I just don't get where we're 
heading.  Every Pharo release gets bigger, and bigger, and bigger.  I don't 
mind the environment getting bigger if it adds functionalities or new tools but 
that's not quite the case here. LOTS of stuff is just duplicated.

Do we really need 2 code completion classes (NECController, NOCController) ?  
Do we really need 2 system browsers (Nautilus, Calypso)? Do we really need 2 
compilers (OpalCompiler, Compiler) ?  Do we really need 8 delay schedulers 
(DelayMicrosecondScheduler, DelayMillisecondScheduler, DelayNullScheduler, 
DelayExperimentalSpinScheduler, DelaySpinScheduler, DelayTicklessScheduler, 
DelayExperimentalCourageousScheduler, DelayExperimentalSemaphoreScheduler) ?  
Do we really need 2 inspectors (GTInspector, EyeInspector) ?  Do we really need 
2 workspaces (GTPlayground, Workspace) ? Et cetera. Et cetera. Et cetera.  I 
could go on, and on, and on...

Pharo 5.1 had 5885 classes. Pharo 6.1 had 6481 classes. Pharo 7.0 alpha has 
7612 classes.  Can you see a trend?

Pharo 5.1 had 416 preference settings. Pharo 6.1 had 494 preference settings. 
Pharo 7.0 alpha has 662 preference settings.  Can you see a trend?

Pharo 5.1 had a 27.44 MB image. Pharo 6.1 had a 35.18 MB image. Pharo 7.0 alpha 
has a 47.97 MB image.  Can you see a trend?

Add to that the fact that Pharo is a nightmare when you want to port code.  
Just with the 7.0 release, 61 classes will be deprecated (and lots more to come 
if you search for the string "deprecated" into the code, most of the time 
hidden in the comments of the soon-to-be-deprecated-in-Pharo-8-I-guess classes).

You have code that deals with sockets, should you use the old Socket classes or 
convert everything to Zodiac? And why do we keep both "frameworks" in the image 
?  Pharo hasn't been backward compatible with "old socket classes" a looong 
time ago anyway!

You have code that deals with dependencies, should you use the old dependents 
mechanism or convert everything to announcements?

UI speaking, what framework should anyone use ?  Athens?  Something else?

You have code that deals with streams, should you use the old stream classes or 
convert everything to Zinc ? And why do we keep both "frameworks" in the image 
?  Pharo hasn't been backward compatible with the old stream classes a 
looong time ago anyway! 

So what's the plan?  For instance, should I keep using the Nautilus Browser or 
I should switch to the Calypso browser and get used to it because Nautilus will 
be deprecated?  Or should I just don't care because a third system browser will 
be added in Pharo 8 just because "it's cool, let's add this one too!" ?

Couldn't we just decide on what's "official" and what's a goodie or an external 
optional tool/package/framework the same way all other Smalltalks do?  If you 
say Calypso is the official & supported browser, fine!  Then just get Nautilus 
out of the image, create a nice loadable package for it and if someone prefers 
Nautilus, they'll just have to load it into the image, the same way VW has a 
gazillion optional tools/packages/frameworks you can load from a parcel!

Whenever I get asked a simple question by a newbie like "Oh, which system 
browser should I use?", quite frankly, I don't know what to answer.  Did we 
include Calypso to deprecate Nautilus later?  Is Calypso just a proof of 
concept?  Is it just an optional tool?  What about all those delay schedulers?  

"I loaded this code from SqueakSource and it just doesn't work".  Should I help 
the guy to fix it or just tell him to convert all the code to the corresponding 
framework in Pharo?

Perhaps a little bit of clarity and details about what's coming and what's the 
plan would be beneficial to a lot of us.

- 
Benoît St-Jean 
Yahoo! Messenger: bstjean 
Twitter: @BenLeChialeux 
Pinterest: benoitstjean 
Instagram: Chef_Benito
IRC: lamneth 
Blogue: endormitoire.wordpress.com 
"A standpoint is an intellectual horizon of radius zero".  (A. Einstein)--- End Message ---

Re: [Pharo-users] Progress bar for ZnClient>>#downloadTo:

[Ben Coman]

You may have guessed I hadn't used Jobs much before.
Then I was surprised that I couldn't find much about Jobs in either
Pharo By Example, Deep Into Pharo or Enterprise Pharo.

>From digging around I made a minimal example I report
to help others' searches, and open it for improvement.

x := 1.
[
[x < 100] whileTrue:
[ x := x + 10.
0.1 seconds wait.
]
] forkAt: 30 named: 'worker'.

[ :job |
[ x < 100 ] whileTrue:
[ job current: x.
0.1 seconds wait.
]
] asJob
  title: 'Work progress...';
  min: 0;
max: 100;
run.

cheers -ben


On 12 April 2018 at 23:02, Ben Coman  wrote:

>
>
> On 12 April 2018 at 18:15, Sven Van Caekenberghe  wrote:
>
>> Ben,
>>
>> You disappoint me, as I would expect you to trace senders/users of
>> #signalProgress: ;-)
>>
>
> :P
> Yeah I knew I was being slack.  I couldn't really follow its operation and
> was a bit tired.
> Actually maybe part of my confusion is that #signalProgress feels more
> like a command than a status.
> I've a slight feeling it would be better as #signallingProgress.
>
>
>
>> ZnClient only signals certain Notifications which a UI around it should
>> deal with.
>>
>> For example,
>>
>> [ :bar |
>>   bar title: 'Downloading Sources...'.
>>   [
>> ZnClient new
>>   url: 'http://files.pharo.org/sources/PharoV30.sources';
>>   signalProgress: true;
>>   downloadTo: FileLocator temp ]
>> on: HTTPProgress
>> do: [ :progress |
>>   progress isEmpty ifFalse: [ bar current: progress percentage ].
>>   progress resume ] ] asJob run.
>>
>
> Thanks, that worked, but its a bit convoluted for my goldfish memory to
> remember each time.
> I'd expect having that as a convenience method would be useful to many.
>
> ZnClient
> showProgress: 'Downloading sources...'
> during: [ :znClient |
> znClient url: 'http://files.pharo.org/sources/PharoV30.sources'.
> znClient downloadTo: FileLocator imageDirectory ].
>
> ZnClient class >> showProgress: title during: clientBlock
> |client|
> client := ZnClient new.
> client signallingProgress: true.
> [ :bar |
>   bar title: title.
>   [clientBlock value: client]
>   on: HTTPProgress
> do: [ :progress |
>   progress isEmpty ifFalse: [ bar current: progress percentage ].
>   progress resume ] ] asJob run.
>
> Easily discoverable as the only class-side method of ZnClient,
> and this would also make a useful howto reference.
>
>
>
>> But there are other UI approaches as well.
>
>
>> Sven
>>
>
> Thanks for you prompt response.
> cheers -ben
>
>
>
>> > On 12 Apr 2018, at 11:25, Ben Coman  wrote:
>> >
>> > I see ZnClient >> downloadTo:
>> > calls  ZnClient >> downloadEntityTo:
>> > which uses #withProgressDo:
>> > which indicates a progress bar might appear.
>> >
>> > But...
>> > ZnClient new
>> > url: ' https://download.libsodium.org
>> /libsodium/releases/libsodium-1.0.16-msvc.zip' ;
>> > downloadTo: FileLocator imageDirectory.
>> > doesn't show a progress bar.  What is the recommended way to display
>> one?
>> >
>> > cheers -ben
>>
>>
>>
>

Re: [Pharo-users] SmalltalkCI now supports loading tonel-based projects

[Gabriel Cotelli]

Framework for testing Smalltalk projects on Linux, macOS, and Windows and
on Travis CI and AppVeyor.  https://github.com/hpi-swa/smalltalkCI

On Thu, Apr 12, 2018 at 2:04 PM, Hilaire  wrote:

> What is SmalltalkCI?
>
> Tonel is a very cool feature as it makes commiting source in file based
> repo very friendly, and browsing from from web based UI tools nice too.
>
>
>
> Le 07/04/2018 à 11:28, Peter Uhnák a écrit :
>
>> SmalltalkCI now supports loading tonel-based projects, so feel free to
>> start using it.
>>
>>
> --
> Dr. Geo
> http://drgeo.eu
>
>
>
>

Re: [Pharo-users] SmalltalkCI now supports loading tonel-based projects

[Hilaire]

What is SmalltalkCI?

Tonel is a very cool feature as it makes commiting source in file based 
repo very friendly, and browsing from from web based UI tools nice too.



Le 07/04/2018 à 11:28, Peter Uhnák a écrit :
SmalltalkCI now supports loading tonel-based projects, so feel free to 
start using it.




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

Re: [Pharo-users] SmalltalkCI now supports loading tonel-based projects

[Sean P. DeNigris]

Stephane Ducasse-3 wrote
> Thanks this is good to know because I want to migrate all my projects
> and future project to use tonel.

+1!



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

Re: [Pharo-users] In P7 scrpt variable to tmp when in debugger

[Hilaire]

Thanks.


Le 12/04/2018 à 17:18, Marcus Denker a écrit :

I should have a fix ready tomorrow.


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

Re: [Pharo-users] In P7 scrpt variable to tmp when in debugger

[Marcus Denker]

> On 12 Apr 2018, at 17:06, Hilaire  wrote:
> 
> Hi Marcus, Benoit,
> 
> Nice to know. I was testing in a set up with both .changes and source files. 
> So I was suspecting something like what your described. I can imagine in 
> production code your feature to speed up compilation will be appreciated. For 
> Dr. Geo and Smalltalk sketch, it is better to have variable names.
> 

I should have a fix ready tomorrow.

> Thanks
> 
> Hilaire
> 
> Le 12/04/2018 à 16:31, Marcus Denker a écrit :
>> Hello,
>> 
>> I changed the way code is compiled for #evaluate: to speed it up, but it 
>> turns out that having nice vars is actually more important than
>> speed in most cases.
>> 
>> I will change this again and just add it as an optional feature (you then 
>> can set an option if you need speed, but the default will be to keep the
>> var names).
>> 
>> For an intermediate fix, you can change in OpalCompiler>>#evaluate the send 
>> of #generate to #generateWithSource.
>> 
>>  Marcus
> 
> -- 
> Dr. Geo
> http://drgeo.eu
> 
> 
> 

Re: [Pharo-users] In P7 scrpt variable to tmp when in debugger

[Hilaire]

Hi Marcus, Benoit,

Nice to know. I was testing in a set up with both .changes and source 
files. So I was suspecting something like what your described. I can 
imagine in production code your feature to speed up compilation will be 
appreciated. For Dr. Geo and Smalltalk sketch, it is better to have 
variable names.


Thanks

Hilaire

Le 12/04/2018 à 16:31, Marcus Denker a écrit :

Hello,

I changed the way code is compiled for #evaluate: to speed it up, but it turns 
out that having nice vars is actually more important than
speed in most cases.

I will change this again and just add it as an optional feature (you then can 
set an option if you need speed, but the default will be to keep the
var names).

For an intermediate fix, you can change in OpalCompiler>>#evaluate the send of 
#generate to #generateWithSource.

Marcus


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

Re: [Pharo-users] Progress bar for ZnClient>>#downloadTo:

[Ben Coman]

On 12 April 2018 at 18:15, Sven Van Caekenberghe  wrote:

> Ben,
>
> You disappoint me, as I would expect you to trace senders/users of
> #signalProgress: ;-)
>

:P
Yeah I knew I was being slack.  I couldn't really follow its operation and
was a bit tired.
Actually maybe part of my confusion is that #signalProgress feels more like
a command than a status.
I've a slight feeling it would be better as #signallingProgress.



> ZnClient only signals certain Notifications which a UI around it should
> deal with.
>
> For example,
>
> [ :bar |
>   bar title: 'Downloading Sources...'.
>   [
> ZnClient new
>   url: 'http://files.pharo.org/sources/PharoV30.sources';
>   signalProgress: true;
>   downloadTo: FileLocator temp ]
> on: HTTPProgress
> do: [ :progress |
>   progress isEmpty ifFalse: [ bar current: progress percentage ].
>   progress resume ] ] asJob run.
>

Thanks, that worked, but its a bit convoluted for my goldfish memory to
remember each time.
I'd expect having that as a convenience method would be useful to many.

ZnClient
showProgress: 'Downloading sources...'
during: [ :znClient |
znClient url: 'http://files.pharo.org/sources/PharoV30.sources'.
znClient downloadTo: FileLocator imageDirectory ].

ZnClient class >> showProgress: title during: clientBlock
|client|
client := ZnClient new.
client signallingProgress: true.
[ :bar |
  bar title: title.
  [clientBlock value: client]
  on: HTTPProgress
do: [ :progress |
  progress isEmpty ifFalse: [ bar current: progress percentage ].
  progress resume ] ] asJob run.

Easily discoverable as the only class-side method of ZnClient,
and this would also make a useful howto reference.



> But there are other UI approaches as well.


> Sven
>

Thanks for you prompt response.
cheers -ben



> > On 12 Apr 2018, at 11:25, Ben Coman  wrote:
> >
> > I see ZnClient >> downloadTo:
> > calls  ZnClient >> downloadEntityTo:
> > which uses #withProgressDo:
> > which indicates a progress bar might appear.
> >
> > But...
> > ZnClient new
> > url: ' https://download.libsodium.org/libsodium/releases/
> libsodium-1.0.16-msvc.zip' ;
> > downloadTo: FileLocator imageDirectory.
> > doesn't show a progress bar.  What is the recommended way to display one?
> >
> > cheers -ben
>
>
>

Re: [Pharo-users] In P7 scrpt variable to tmp when in debugger

[Benoit St-Jean via Pharo-users]

--- Begin Message ---
What happens if you debug the script starting with a "self halt" ?  Are the 
variables there with their original name?  looks like decompiled code.  A 
problem with your .sources file?


- 
Benoît St-Jean 
Yahoo! Messenger: bstjean 
Twitter: @BenLeChialeux 
Pinterest: benoitstjean 
Instagram: Chef_Benito
IRC: lamneth 
Blogue: endormitoire.wordpress.com 
"A standpoint is an intellectual horizon of radius zero".  (A. Einstein) 

On Thursday, April 12, 2018, 10:11:37 a.m. EDT, Hilaire  
wrote:  
 
 Hi,

When an executed script throws an error, in the debugger the script lost 
its variable names and the code is not exactly the same.

Any idea why?

See screenshot

Thanks

Hilaire

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

  --- End Message ---

Re: [Pharo-users] In P7 scrpt variable to tmp when in debugger

[Marcus Denker]

> On 12 Apr 2018, at 16:10, Hilaire  wrote:
> 
> Hi,
> 
> When an executed script throws an error, in the debugger the script lost its 
> variable names and the code is not exactly the same.
> 
> Any idea why?
> 

Hello,

I changed the way code is compiled for #evaluate: to speed it up, but it turns 
out that having nice vars is actually more important than
speed in most cases.

I will change this again and just add it as an optional feature (you then can 
set an option if you need speed, but the default will be to keep the
var names).

For an intermediate fix, you can change in OpalCompiler>>#evaluate the send of 
#generate to #generateWithSource.

Marcus

Re: [Pharo-users] Frozen at start up

[Hilaire]

It looks like deferring to the UIManager is ok for the start up. No need 
to fork at background user level or something like that.



Le 12/04/2018 à 12:42, Hilaire a écrit :
     to use the deferred action in the startup you can add it to the 
SessionManager >> addDeferredStartupAction:, this will execute after 
all the startup actions. However, I was wrong it will not solve the 
problem of the splash, as the deferred action is still running in 
maximum priority (maybe this should be changed).


And what about UIManager default defer: [], does it run at an 
acceptable lower priority? 


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

Re: [Pharo-users] To be there or not to be there

[Hilaire]

Glad to read that.

Note: it is unlikely I could met again such situation as I already 
re-organized the code. But good to know there is this update menu item 
if such case arise again.


Thanks

Hilaire


Le 12/04/2018 à 15:17, Denis Kudriashov a écrit :

Stef found and I fixed one case which could be related to your problem.
So next release it will be integrated.

Also I added to #extra menu group the item "Update" which will help in 
such buggy cases.




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

Re: [Pharo-users] To be there or not to be there

[Denis Kudriashov]

Stef found and I fixed one case which could be related to your problem.
So next release it will be integrated.

Also I added to #extra menu group the item "Update" which will help in such
buggy cases.

2018-04-03 23:06 GMT+02:00 Hilaire :

> Hello,
>
> I have re-organized the packages and classes in DrGeo with Calypso. An now
> I come to a situation where methods seems to be there without been there.
>
> For example DrGeoWindow>>newTable: methods,
>
> - Calypso can browse it and can show its implementor
>
> - Nautilus can browse it and can NOT show its implementor
>
> - and more importantly when exported to tonel file, it is missing !
>
> Who knows what else methods are missing.
>
> See screenshot.
>
> Any idea?
>
> Hilaire
>
> --
> Dr. Geo
> http://drgeo.eu
>
>

Re: [Pharo-users] [SmalltalkCI] loading tonel dependencies?

[Gabriel Cotelli]

I've created a new issue in smalltalkCI issue tracker:
https://github.com/hpi-swa/smalltalkCI/issues/365
. 


On Thu, Apr 12, 2018 at 6:12 AM, Peter Uhnák  wrote:

> peter,
>>  are you sure that dependencies of a project in tonel format can be
>> loaded?
>
>
> I agree with Gabriel, this has to be a Metacello issue.
>
> The support that was added was having your repo in tonel. If tonel
> dependencies are problem, that's a different issue. I think this is best to
> report directly to SmalltalkCI issue tracker.
>
> But I think smalltalkCI disabled it for Pharo (see disableIcebergDuring:
>> ). I don't know why.
>>
>
> I know that some (long) time ago loading it with iceberg was causing some
> weird trouble, but recently some people mentioned that they use it without
> problems (I think this was from Jenkins CI), so enabling it in SmalltalkCI
> sounds like a good idea.
>
> Peter
>
> On Thu, Apr 12, 2018 at 3:40 AM, Bernardo Ezequiel Contreras <
> vonbecm...@gmail.com> wrote:
>
>> in a fresh 6.1 image , i did this
>>
>> Metacello new
>> baseline: 'EarleyParser';
>> repository: 'github://vonbecmann/earley-parser/repository';
>> load.
>>
>> expression in the playground and it works.
>>
>> so there's something bogus in smalltalkCI.
>>
>>
>>
>> On Wed, Apr 11, 2018 at 9:14 PM, Gabriel Cotelli 
>> wrote:
>>
>>> If Iceberg enableMetacelloIntegration is true the load seems to work.
>>> But I think smalltalkCI disabled it for Pharo (see disableIcebergDuring: ).
>>> I don't know why.
>>>
>>> On Wed, Apr 11, 2018 at 6:40 PM, Bernardo Ezequiel Contreras <
>>> vonbecm...@gmail.com> wrote:
>>>
 peter,
  are you sure that dependencies of a project in tonel format can be
 loaded?

 earley-parser -> linked-list

 see https://travis-ci.org/vonbecmann/earley-parser/builds/365332549

 thanks in advance

 --
 Bernardo E.C.

 Sent from a cheap desktop computer in South America.

>>>
>>>
>>
>>
>> --
>> Bernardo E.C.
>>
>> Sent from a cheap desktop computer in South America.
>>
>
>

Re: [Pharo-users] installation of packages on 6.1

[Baveco, Hans]

Thanks for this explanation Stef,

Now looking forward to Guilles work - sounds like it will be a very helpful 
resource when starting to use Git!
Hans


-Original Message-
From: Stephane Ducasse  
Sent: woensdag 11 april 2018 22:01
To: Any question about pharo is welcome 
Subject: Re: [Pharo-users] installation of packages on 6.1

Hans

just a meta remark (I personally find the API of git quite terrible - In 
addition I do not really like the github UI it feels like these ugly google 
noUIDesigned "UI") now you should consider that more and more people find git 
cool and powerful. And as a matter of fact it is.
So you should consider that understanding and learning git is a way to look 
less obsolete in the future. And it has nothing to do with Pharo.
Except that Pharo is becoming less foreign for mamy people thank to this.
I worked super well with git and iceberg on projects managing my dev in a 
branch before it is ready to be incorporated.
So solid branches was what was really missing to monticello and before you use 
it you may have problems to really assess them but once you work with them you 
get the power they bring and the comfort.
Guille is working on a nice explanation of Git and central concept of branch 
and you may want to read (at least I will read it because Guille understand it 
super super well).

Stef


On Wed, Apr 11, 2018 at 11:23 AM, Herbert Vojčík  wrote:
> No, it is possible to install them without github account.
>
> You need to set protocol to https:
>
>  Iceberg enableMetacelloIntegration: true; remoteTypeSelector: #httpsUrl.
>
> Herby
>
> Baveco, Hans wrote:
>>
>> Thanks Ben!
>>
>> I created a github account, installed git and git bash, created SSH 
>> keys, added keys to my github account, and changed the settings in 
>> Pharo to use these keys, and finally was able to install the packages I 
>> wanted to try.
>> (roassal2 still not installing though).
>>
>> Question remains, is this really the only way to get these packages 
>> that live on github into the image? I had no plans to work with 
>> git/github, but was now forced to spent quite some time on it
>>
>> Cheers,
>>
>> Hans
>>
>> *From:*Ben Coman 
>> *Sent:* maandag 9 april 2018 22:54
>> *To:* Any question about pharo is welcome 
>> 
>> *Subject:* Re: [Pharo-users] installation of packages on 6.1
>>
>> On 6 April 2018 at 00:02, Baveco, Hans 
> wur.nl
>>
>> > wrote:
>>
>> Trying to install Territorial the installation got stuck on the
>> installation of Roassal2 1.35, with error “LGitObjectNotInitialized”
>>
>> Transcript says:
>>
>> “Project: Roassal2 1.35
>>
>> I got an error while cloning: There was an authentication error
>> while trying to execute the operation: error authenticating:
>> failed connecting agent.
>>
>> This happens usually because you didn't provide a valid set of
>> credentials.
>>
>> You may fix this problem in different ways:
>>
>> 1. adding your keys to ssh-agent, executing ssh-add ~/.ssh/id_rsa
>> in your command line.
>>
>> 2. adding your keys in settings (open settings browser search for
>> "Use custom SSH keys" and
>>
>> add your public and private keys).
>>
>> 3. using HTTPS instead SSH (Just use an url in the form
>> HTTPS://etc.git). I will try to clone the HTTPS variant.”
>>
>> I have encountered this several t
>
> imes before, for different
>>
>> packages (on windows 7, pharo 6.1 (Image: Pharo6.0 [Latest update:
>> #60540])) and have no idea how to deal with this.
>>
>> Any suggestions?
>>
>> Hans
>>
>> On Windows you need to use option 2. World Menu > Settings > etc...
>>
>> cheers -ben
>>
>

Re: [Pharo-users] Frozen at start up

[Hilaire]

Le 12/04/2018 à 12:06, teso...@gmail.com a 
écrit :
     to use the deferred action in the startup you can add it to the 
SessionManager >> addDeferredStartupAction:, this will execute after 
all the startup actions. However, I was wrong it will not solve the 
problem of the splash, as the deferred action is still running in 
maximum priority (maybe this should be changed).


And what about UIManager default defer: [], does it run at an acceptable 
lower priority?


So the solution for the splash window will be to fork the process in a 
lower priority (with an explicit priority)



Any idea which priority it should be?

Hilaire

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

Re: [Pharo-users] Frozen at start up

[Hilaire]

Hi Pablo,

I will one or the other for the Splash screen,

The most annoying is the warning message at start up. Can your take a 
look at this app in your system if it  shows up? (the splash is off in 
this version, so it should not cause trouble)


https://www.dropbox.com/s/te2gel05u1y1sp9/DrGeo.app.zip?dl=0

Thanks

Hilaire

Le 12/04/2018 à 12:06, teso...@gmail.com a 
écrit :

Hi Hilaire,
     to use the deferred action in the startup you can add it to the 
SessionManager >> addDeferredStartupAction:, this will execute after 
all the startup actions. However, I was wrong it will not solve the 
problem of the splash, as the deferred action is still running in 
maximum priority (maybe this should be changed).


So the solution for the splash window will be to fork the process in a 
lower priority (with an explicit priority)




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

Re: [Pharo-users] Progress bar for ZnClient>>#downloadTo:

[Sven Van Caekenberghe]

Ben,

You disappoint me, as I would expect you to trace senders/users of 
#signalProgress: ;-)

ZnClient only signals certain Notifications which a UI around it should deal 
with.

For example,

[ :bar |
  bar title: 'Downloading Sources...'.
  [
ZnClient new 
  url: 'http://files.pharo.org/sources/PharoV30.sources'; 
  signalProgress: true; 
  downloadTo: FileLocator temp ]
on: HTTPProgress 
do: [ :progress |
  progress isEmpty ifFalse: [ bar current: progress percentage ]. 
  progress resume ] ] asJob run.

But there are other UI approaches as well.

Sven

> On 12 Apr 2018, at 11:25, Ben Coman  wrote:
> 
> I see ZnClient >> downloadTo:
> calls  ZnClient >> downloadEntityTo:
> which uses #withProgressDo: 
> which indicates a progress bar might appear.
> 
> But...
> ZnClient new 
> url: ' 
> https://download.libsodium.org/libsodium/releases/libsodium-1.0.16-msvc.zip' ;
> downloadTo: FileLocator imageDirectory.
> doesn't show a progress bar.  What is the recommended way to display one?
> 
> cheers -ben

Re: [Pharo-users] Frozen at start up

[teso...@gmail.com]

Hi Hilaire,
 to use the deferred action in the startup you can add it to the
SessionManager >> addDeferredStartupAction:, this will execute after all
the startup actions. However, I was wrong it will not solve the problem of
the splash, as the deferred action is still running in maximum priority
(maybe this should be changed).

So the solution for the splash window will be to fork the process in a
lower priority (with an explicit priority)

Cheers

On Wed, Apr 11, 2018 at 3:56 PM, Hilaire  wrote:

> Removing the Splash screen avoid locking the image. About deferred action,
> how do you do it?
>
> However why do I have this start up message about Pharo not been properly
> claused?
>
> The installation of the app ends with a proper save and quit.
>
> DrGeoInstallerWorkstation>>install
> super install.
> DrGDefault beWorkstation.
> self cleanUpForRelease.
> Author fullName: 'MrCleaner'.
> Smalltalk saveAs: 'drgeo'.
> World submorphs
> select: [:m | m class == (Smalltalk at: #DrGeoWindow)]
> thenDo: [:drMorph | drMorph deleteWithoutConfirmation ].
>
> self cleanMySelf.
> Smalltalk fixObsoleteReferences.
> Smalltalk garbageCollect.
> Smalltalk garbageCollect.
> Smalltalk garbageCollect.
>
> PharoChangesCondenser condense.
> ExternalDropHandler registerHandler:
> (ExternalDropHandler
> type: nil
> extension: 'fgeo'
> action: [ :stream | DrGeo fullscreenOn: stream ]).
>
> Smalltalk snapshot: true andQuit: true.
>
>
> What is even strange, when I run the buid in the system building it, this
> message does not show up?
>
> Any idea?
>
> Thanks
>
> Hilaire
>
> Le 10/04/2018 à 21:36, teso...@gmail.com a écrit :
>
>> In Pharo 7 the startup of the session runs in higher priority so it
>> cannot be interrupted.
>> This is done in that way to fix some problems during the initialization
>> of the session (Now, I could not remember what was fixed).
>>
>
> --
> Dr. Geo
> http://drgeo.eu
>
>
>
>


-- 
Pablo Tesone.
teso...@gmail.com

Re: [Pharo-users] Quick website fix

[Marcus Denker]

Fixed!

> On 12 Apr 2018, at 11:38, Markus Fritsche  wrote:
> 
> Hi,
> 
> it says on "https://pharo.org/contribute-propose-fix; that Manuscript
> used to be called "Fugbugz" - although an understandable mistake, I
> believe it was called "Fogbugz" :-)
> 
> 
> Kind regards
> 
>   Markus
> 
> 

[Pharo-users] Quick website fix

[Markus Fritsche]

Hi,

it says on "https://pharo.org/contribute-propose-fix; that Manuscript
used to be called "Fugbugz" - although an understandable mistake, I
believe it was called "Fogbugz" :-)


Kind regards

  Markus

Re: [Pharo-users] Frozen at start up

[Stephane Ducasse]

Not like that. Pablo proposed to help you and he is much better than me :)
I'm busy with administria.

On Thu, Apr 12, 2018 at 10:38 AM, Hilaire  wrote:
> Hi Stef,
>
> No clue why I have this warning message at start up?
>
> Hilaire
>
> Le 11/04/2018 à 21:48, Stephane Ducasse a écrit :
>>
>> Hi hilaire
>>
>> Favor Smalltalk globals at: #... over Smalltalk at: #
>>
>> Stef
>
>
> --
> Dr. Geo
> http://drgeo.eu
>
>
>

Re: [Pharo-users] migration to 6.1 was super easy.

[Stephane Ducasse]

Thanks this is a great testimony.
BTW I would love to have a success story around your project.
Can we take it off line?

On Thu, Apr 12, 2018 at 2:00 AM, PAUL DEBRUICKER  wrote:
> Thanks for all the hard work.
>
>
> It took me about 30 minutes to migrate one of my projects from 32bit Pharo 5 
> to 64bit 6.1 this afternoon.  It has about 40 external dependencies so I 
> thought it would take much longer to get everything sorted.

[Pharo-users] Progress bar for ZnClient>>#downloadTo:

[Ben Coman]

I see ZnClient >> downloadTo:
calls  ZnClient >> downloadEntityTo:
which uses #withProgressDo:
which indicates a progress bar might appear.

But...
ZnClient new
url: ' https://download.libsodium.org/libsodium/releases/
libsodium-1.0.16-msvc.zip' ;
downloadTo: FileLocator imageDirectory.
doesn't show a progress bar.  What is the recommended way to display one?

cheers -ben

Re: [Pharo-users] [SmalltalkCI] loading tonel dependencies?

[Peter Uhnák]

>
> peter,
>  are you sure that dependencies of a project in tonel format can be loaded?


I agree with Gabriel, this has to be a Metacello issue.

The support that was added was having your repo in tonel. If tonel
dependencies are problem, that's a different issue. I think this is best to
report directly to SmalltalkCI issue tracker.

But I think smalltalkCI disabled it for Pharo (see disableIcebergDuring: ).
> I don't know why.
>

I know that some (long) time ago loading it with iceberg was causing some
weird trouble, but recently some people mentioned that they use it without
problems (I think this was from Jenkins CI), so enabling it in SmalltalkCI
sounds like a good idea.

Peter

On Thu, Apr 12, 2018 at 3:40 AM, Bernardo Ezequiel Contreras <
vonbecm...@gmail.com> wrote:

> in a fresh 6.1 image , i did this
>
> Metacello new
> baseline: 'EarleyParser';
> repository: 'github://vonbecmann/earley-parser/repository';
> load.
>
> expression in the playground and it works.
>
> so there's something bogus in smalltalkCI.
>
>
>
> On Wed, Apr 11, 2018 at 9:14 PM, Gabriel Cotelli 
> wrote:
>
>> If Iceberg enableMetacelloIntegration is true the load seems to work. But
>> I think smalltalkCI disabled it for Pharo (see disableIcebergDuring: ). I
>> don't know why.
>>
>> On Wed, Apr 11, 2018 at 6:40 PM, Bernardo Ezequiel Contreras <
>> vonbecm...@gmail.com> wrote:
>>
>>> peter,
>>>  are you sure that dependencies of a project in tonel format can be
>>> loaded?
>>>
>>> earley-parser -> linked-list
>>>
>>> see https://travis-ci.org/vonbecmann/earley-parser/builds/365332549
>>>
>>> thanks in advance
>>>
>>> --
>>> Bernardo E.C.
>>>
>>> Sent from a cheap desktop computer in South America.
>>>
>>
>>
>
>
> --
> Bernardo E.C.
>
> Sent from a cheap desktop computer in South America.
>

Re: [Pharo-users] Frozen at start up

[Hilaire]

Hi Stef,

No clue why I have this warning message at start up?

Hilaire

Le 11/04/2018 à 21:48, Stephane Ducasse a écrit :

Hi hilaire

Favor Smalltalk globals at: #... over Smalltalk at: #

Stef


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

[Pharo-users] [Newsletter] Content Needed

[Marcus Denker]

Hi,

The Pharo Monthly Newsletter is working quite well. 
https://newsletter.pharo.org 

We now reached a level where it is not just 3 things, but much much more..  of 
course this comes with a downside:
- Sometimes topics that would be worth a small article are just posted 
as a one-liners
- I forget / overlook things for sure (so much happening!)

If you want your (or some other project or topic) to be in the newsletter —> 
send me a mail, in the best of all cases
with a fully written text that you want to have posted.

This includes:
- new libraries and projects
- dates
- high level description of existing projects
- videos
- Blog posts
- books
- lectures
- Success Stories of all kinds (nice to present your Company!)
- Research (e.g. published papers or project descriptions)
- Expanded versions of news posted as one-liners before
- ….

There is a explicit jobs section, too. 

Marcus

Re: [Pharo-users] [TechTalk] April 12: GIT with Iceberg

[Marcus Denker]

This is today 

5:00 PM - 7:00 PM (UTC+02:00)

There is a calendar entry to download at: 
https://association.pharo.org/event-2797068

> On 10 Apr 2018, at 16:34, Marcus Denker  wrote:
> 
> Hi,
> 
> There next TechTalk will be April 12: GIT with Iceberg
> 
>   https://association.pharo.org/event-2797068
> 
> 
> A regular chat about Pharo. Happens on Discord.
> 
> The Tech talks are open to both members and non-members! 
> 
> Topic:  GIT with Iceberg. Demo of improved UI
> 
> We will send an information to all subscribers some hours before the talk 
> starts.
> 
>