[Pharo-dev] Need help for collecting tests usage data

[Blondeau Vincent]

Hi,

An intern of the RMod research team needs your help:

Cheers,
Vincent

De : Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] De la part de 
Benoit Verhaeghe
Envoyé : mercredi 7 juin 2017 16:47
À : pharo-us...@lists.pharo.org
Objet : [Pharo-users] Need help for collecting tests usage data


Hi everyone.



I need your help. I’m working on how pharo developers use the tests. And you 
are pharo developers.

So I developed a plugin and I would like you to download it. You just have to 
execute this line in a playground



Metacello new

smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo60';

configuration: 'TestsUsageAnalyser';

version: #stable;

get;

load.



You will have to do it only one time in one image. Then, if they are updates 
it’ll be done automatically and if you create a new image it will be 
automatically installed.



The plugin will collect data on which tests you run, when, and the 
modifications you'll have done.

Normally, it should be completely transparent for the users and the data are 
anonymous.



If you want more details about the project or how it works, you can answer to 
this mail, or send me an email at 
benoit.verhae...@inria.fr or by using discord.

Thanks a lot.

Benoit Verhaeghe

!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] please test download for Pharo 6.0

[Blondeau Vincent]

My review:
- For Pharo x64: Version 6.0 for OS X, GNU/Linux, and Windows -> Version 6.0 
for OS X and GNU/Linux.
- The VM and .sources are the same as for Pharo5. -> The VM and .sources are 
the same as for Pharo 6.
- http://files.pharo.org/image/70/latest.zip -> dead link (but this is expected 
;))

Thanks Esteban!

Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de volkert
Envoyé : mercredi 31 mai 2017 18:25
À : pharo-dev@lists.pharo.org
Objet : Re: [Pharo-dev] please test download for Pharo 6.0


 *   Downloaded Linux 64 Bit.
 *   Installed Roassal.
 *   Run Examples.
 *   VM crashed :-(
BW, Volkert

Am 31.05.2017 um 17:59 schrieb Esteban Lorenzano:



On 31 May 2017, at 17:46, Peter Uhnak 
 wrote:



I find the Windows distribution a bit chaotic as all the files (vm, vm libs, 
image, sources) are in the same folder. Maybe there were issues with using 
shortcuts? Because then launching the image will also create pharo-local in the 
folder (and any other file that image writes to imageDirectory), so it could be 
more chaos for a new user.



yes, it has been like that since some time and we need to change it… but not 
now for release :)





The linux distro contains sources twice

1) pharo6.0/shared/PharoV60.sources

2) pharo6.0/bin/PharoV60.sources



yeah, that’s also a problem from one-click days… maybe I can fix that/



Esteban





Peter





On Wed, May 31, 2017 at 04:18:19PM +0200, Esteban Lorenzano wrote:

Hello,



we are getting ready for release.

please take a minute to review:



http://pharo.org/STAGE.download 




(notice that zerconf download will not work because it is not yet moved… so 
#stable will download current stable version which is 5.0)



cheers,

Esteban








!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] Test and Patch for writeStream error

[Blondeau Vincent]

Hi,

Thanks for reporting!

If you want to contribute and have your fix integrated, I advise you to follow 
the procedure here: http://pharo.org/contribute-propose-fix

If you need help, don't hesitate to reply!

Regards,
Vincent

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de K K
> Subbu
> Envoyé : mardi 18 avril 2017 17:34
> À : Pharo Development List
> Objet : [Pharo-dev] Test and Patch for writeStream error
>
> Hi,
>
> I stumbled on an error in WriteStream>>ensureEndsWith: method. The error
> caused extra blank lines in logs.
>
> Attached small changeset fixes it. It also adds a test to catch such errors in
> the future. With this fix,
>
> ./pharo generator.image PharoVMSpur32Builder buildUnix32
>
> gives a compact output without extra blank lines.
>
> To which box in which repo should I save this cs for mainlining it?
>
> Regards .. Subbu

!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] Growing large images: the case of Moose models

[Blondeau Vincent]

Thanks Eliot for the implementation of the new compactor!

Just to add a piece of information: the mse imported have a size of 40Mb.

Cheers,
Vincent


De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Clément 
Bera
Envoyé : vendredi 3 mars 2017 11:56
À : Discusses Development of Pharo
Objet : [Pharo-dev] Growing large images: the case of Moose models

Hello everyone,

This morning I investigated with Vincent Blondeau a problem reported by the 
Moose community a while ago: loading Moose model is slower in Spur (Pharo 5+) 
than in pre-Spur (Pharo 4 and older). In general, this problem was present for 
anyone growing images to a significant size.

To investigate the problem, we loaded a 200Mb[3] Moose model on a 250Mb image, 
growing the image to 450Mb. Loading such a model takes 2 minutes in Spur and 
1m30s in pre-Spur VMs.

Using the stable Pharo VM, the analysis results were the following:
- total time spent to load the Model: 2 minutes
- time spent in full GC: 1 minute (4 fullGCs)
- time spent in scavenges[1]: 15 seconds
On the 2 minutes spent, we have 50% of the time spent in full GCs, 12.5% in 
scavenges, 37.5% executing code.

We then used the latest VM that features the new compactor (VM from beginning 
of March 2017 and over). The full GC execution time went down from 1 minute to 
2 seconds.

In addition, we increased the size of Eden[2] from 4Mb to 12Mb. Time spent in 
scavenges decreased from 15 seconds to 5 seconds.

Overall, loading the model is now taking ~50 seconds instead of 2 minutes.

To increase Eden size, one needs to run a script similar to:

| currentEdenSize desiredEdenSize |
currentEdenSize := Smalltalk vm parameterAt: 44.
desiredEdenSize := currentEdenSize * 4.
Smalltalk vm parameterAt: 45 put: desiredEdenSize.

And then restart the image.

I hope this report can be useful for some of you. I will try to make a blog 
post out of it, detailing other GC settings one can change from the image to 
improve performance.

Best,

Clement

[1] A scavenge is basically the garbage collection of only young objects
[2] Eden is basically the space where objects are initially allocated.
[3] All numbers in the report are order of magnitudes and not precise numbers




!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] [Moose-dev] Re: Re: Segmentation fault on Moose 6.1 Build

[Blondeau Vincent]

Nice try, but it doesn't seems to :( :
https://ci.inria.fr/moose/job/moose-6.1/556/console

Smalltalk stack dump:
0xbfc61c50 I GrafPort>copyBits 0x9c1f7a8: a(n) GrafPort
0xbfc61c70 I GrafPort>image:at:sourceRect:rule: 0x9c1f7a8: a(n) GrafPort
0xbfc61ca0 I FormCanvas>image:at:sourceRect:rule: 0x9c12a98: a(n) FormCanvas

Cheers,
Vincent


> -Message d'origine-
> De : Moose-dev [mailto:moose-dev-boun...@list.inf.unibe.ch] De la part de
> Tudor Girba
> Envoyé : vendredi 3 mars 2017 10:22
> À : Pharo Development List
> Cc : Moose-related development
> Objet : [Moose-dev] Re: [Pharo-dev] Re: Segmentation fault on Moose 6.1
> Build
>
> Thanks.
>
> I have switched the Moose job back to using the latest image. Let’s see how
> it works.
>
> Cheers,
> Doru
>
>
> > On Mar 3, 2017, at 9:19 AM, Pavel Krivanek 
> wrote:
> >
> > Esteban created a working fix for this issue.
> >
> > Cheers,
> > -- Pavel
> >
> > 2017-03-03 3:16 GMT+01:00 Ben Coman :
> > To confirm specific reproducibility, using...
> > http://files.pharo.org/image/60/60421.zip
> >
> > I did...
> > $ cd opensmalltalk-vm
> > $ git checkout d54edc56
> > $ git log
> > commit d54edc5638c9f90c80f214e59e19240f8ead87f8
> > Author: Eliot Miranda 
> > Date:   Thu Mar 2 09:53:05 2017 -0800
> > CogVM source as per VMMaker.oscog-eem.2143
> > Fix regression in Sista sources due to receiverTags work.
> >
> > $ cd build.linux32x86/pharo.cog.spur/build.debug
> > $ cd products/debug/phcogspurlinuxht
> > $ pharo  ~/temp/Case19785/Pharo-60421.image
> >
> > World > Playground, evaluate...
> >surf := AthensCairoSurface extent: Display extent.
> >Display getCanvas drawImage: surf asForm  at: 0@0
> >
> > 70% ==> image seg fault
> > 30% ==> PrimitiveFailed: primitive #primSignal:andReturnAs:fromContext:
> >
> > but doing
> > Smalltalk snapshot: true andQuit: true.
> > surf := AthensCairoSurface extent: Display extent.
> > Display getCanvas drawImage: surf asForm  at: 0@0.
> >
> > 100% ==> PrimitiveFailed: primitive #primSignal:andReturnAs:fromContext:
> >
> >
> > Evaluate the following in Playground for 100% segfault from command line.
> >
> > EllipseMorph compile: 'step
> > |surf|
> > [   surf := AthensCairoSurface extent: Display extent.
> > Display getCanvas drawImage: surf asForm  at: 0@0.
> > ] on: Error do: [ ].
> > self position: self position + (50@0). "To observe survival of seg
> fault"   '.
> > Smalltalk snapshot: true andQuit: true.
> > EllipseMorph new openInWorld.
> >
> >
> > btw, I'm on 32-bit Debian 8 Jessie
> > $ uname -a
> > Linux dom0 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08)
> > i686 GNU/Linux
> >
> > cheers -ben
> >
> >
> > On Fri, Mar 3, 2017 at 12:08 AM, Blondeau Vincent
>  wrote:
> > > Hi Eliot,
> > >
> > >
> > >
> > > Thanks to take care of this issue!
> > >
> > >
> > >
> > > Pavel opened a bug issue here:
> > > https://pharo.fogbugz.com/f/cases/19785/Athens-crashes-the-VM . You
> > > need the latest Pharo image and VM and it crashes under Linux
> > > (32-bit) and OSX (El Captain, 32-bit VM). And I personally tried
> > > with Windows7 and the bug happens too.
> > >
> > >
> > >
> > > To reproduce: Morph new testAthensRender
> > >
> > >
> > >
> > > An extract of the opened issue:
> > >
> > >
> > >
> > > Edited by Pavel Krivanek 02/03/2017 (Today) 16:10
> > >
> > > An empty surface crashes it too:
> > > surf := AthensCairoSurface extent: Display extent.
> > > Display getCanvas drawImage: surf asForm  at: 0@0
> > >
> > >
> > >
> > > The problem is in the method AthensCairoSurface>>#asForm where the
> > > previous slice started to add 1 to surface heigth
> > >
> > >
> > >
> > > Well, I tried to revert AthensCairoSurface>>#asForm which fixes this
> > > particular case but Roassal still crashes on copyBits
> > >
> > >
> > >
> > > Cheers,
> > >
> > > Vincent
> > >
> > >
> > >
> > > De : Moose-dev [mailto:moose-dev-boun...@list.inf.unibe.ch] De la
> > > part de Eliot Miranda Envoyé : jeudi 2 mars 2017 17:0

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Segmentation fault on Moose 6.1 Build

[Blondeau Vincent]

I'll do.

Cheers,
Vincent

> -Message d'origine-
> De : Moose-dev [mailto:moose-dev-boun...@list.inf.unibe.ch] De la part de
> Tudor Girba
> Envoyé : jeudi 2 mars 2017 16:49
> À : Pharo Development List
> Cc : Moose-related development
> Objet : [Moose-dev] Re: [Pharo-dev] Re: Re: Segmentation fault on Moose
> 6.1 Build
>
> As I said, thanks for doing that. Just make sure to announce such changes in
> the future because they are hard to debug otherwise.
>
> Thanks again.
>
> Cheers,
> Doru
>
> > On Mar 2, 2017, at 4:45 PM, Blondeau Vincent
>  wrote:
> >
> > I fixed the Pharo image used to the 60418 to get a working moose image
> since the bug with Athens is resolved.
> >
> > Cheers,
> > Vincent
> >
> >> -Message d'origine-
> >> De : Moose-dev [mailto:moose-dev-boun...@list.inf.unibe.ch] De la
> >> part de Tudor Girba Envoyé : jeudi 2 mars 2017 16:42 À : Pharo
> >> Development List Cc : Moose-related development Objet : [Moose-dev]
> >> Re: [Pharo-dev] Re: Segmentation fault on Moose 6.1 Build
> >>
> >> Hmm, it looks like something changed and the build is now yellow.
> >>
> >> Does anyone have the time to check this mysterious behavior?
> >>
> >> Cheers,
> >> Doru
> >>
> >>
> >>> On Mar 2, 2017, at 1:24 PM, Pavel Krivanek
> >>> 
> >> wrote:
> >>>
> >>> I will try to make some easier way to reproduce it and open an issue
> >>>
> >>> -- Pavel
> >>>
> >>> 2017-03-02 11:58 GMT+01:00 Pavel Krivanek
> :
> >>> Hm, I haven't check the time of the failing build... Yes, it will be 
> >>> related...
> >>>
> >>> 2017-03-02 11:51 GMT+01:00 Tudor Girba :
> >>> Except for tiny changes in Athens in 60419 :)
> >>>
> >>> Doru
> >>>
> >>>
> >>>> On Mar 2, 2017, at 11:33 AM, Pavel Krivanek
> >>  wrote:
> >>>>
> >>>> On image side nothing relevant happened in 60418 where it started
> >>>> to
> >> fail.
> >>>>
> >>>> -- Pavel
> >>>>
> >>>> 2017-03-02 11:31 GMT+01:00 Blondeau Vincent
> >> :
> >>>> I heard that the gc compactor have changed.
> >>>>
> >>>> Cheers,
> >>>> Vincent
> >>>>
> >>>>> -Message d'origine-
> >>>>> De : Moose-dev [mailto:moose-dev-boun...@list.inf.unibe.ch] De la
> >>>>> part de Tudor Girba Envoyé : jeudi 2 mars 2017 11:29 À : Pharo
> >>>>> Development List Cc : Moose-related development Objet :
> >>>>> [Moose-dev] Re: [Pharo-dev] Segmentation fault on Moose 6.1 Build
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> Was there a change related to the stable VM?
> >>>>>
> >>>>> Cheers,
> >>>>> Doru
> >>>>>
> >>>>>
> >>>>>> On Mar 2, 2017, at 11:23 AM, Blondeau Vincent
> >>>>>  wrote:
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> The latest builds of the Moose6.1 image are failing due to a
> >>>>>> segmentation
> >>>>> fault.
> >>>>>> Here is the link to the last build:
> >>>>>> https://ci.inria.fr/moose/job/moose-6.1/550/console
> >>>>>>
> >>>>>> How can we fix this?
> >>>>>>
> >>>>>> Thanks in advance,
> >>>>>>
> >>>>>> Cheers,
> >>>>>> Vincent
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>
> !!!
> >>>>> ***
> >>>>>> ** "Ce message et les pièces jointes sont
> >>>>>> confidentiels et réservés à l'usage exclusif de ses
> >>>>>> destinataires. Il peut
> >>>>> également être protégé par le secret professionnel. Si vous
> >>>>> recevez ce message par erreur, merci d'en avertir immédiatement
> >>>>> l'expéditeur et de le détruire. L'intégrité du message ne pouvant
> >>>>> être assurée sur Internet, la 

Re: [Pharo-dev] [Moose-dev] Re: Re: Segmentation fault on Moose 6.1 Build

[Blondeau Vincent]

I fixed the Pharo image used to the 60418 to get a working moose image since 
the bug with Athens is resolved.

Cheers,
Vincent

> -Message d'origine-
> De : Moose-dev [mailto:moose-dev-boun...@list.inf.unibe.ch] De la part de
> Tudor Girba
> Envoyé : jeudi 2 mars 2017 16:42
> À : Pharo Development List
> Cc : Moose-related development
> Objet : [Moose-dev] Re: [Pharo-dev] Re: Segmentation fault on Moose 6.1
> Build
>
> Hmm, it looks like something changed and the build is now yellow.
>
> Does anyone have the time to check this mysterious behavior?
>
> Cheers,
> Doru
>
>
> > On Mar 2, 2017, at 1:24 PM, Pavel Krivanek 
> wrote:
> >
> > I will try to make some easier way to reproduce it and open an issue
> >
> > -- Pavel
> >
> > 2017-03-02 11:58 GMT+01:00 Pavel Krivanek :
> > Hm, I haven't check the time of the failing build... Yes, it will be 
> > related...
> >
> > 2017-03-02 11:51 GMT+01:00 Tudor Girba :
> > Except for tiny changes in Athens in 60419 :)
> >
> > Doru
> >
> >
> > > On Mar 2, 2017, at 11:33 AM, Pavel Krivanek
>  wrote:
> > >
> > > On image side nothing relevant happened in 60418 where it started to
> fail.
> > >
> > > -- Pavel
> > >
> > > 2017-03-02 11:31 GMT+01:00 Blondeau Vincent
> :
> > > I heard that the gc compactor have changed.
> > >
> > > Cheers,
> > > Vincent
> > >
> > > > -Message d'origine-
> > > > De : Moose-dev [mailto:moose-dev-boun...@list.inf.unibe.ch] De la
> > > > part de Tudor Girba Envoyé : jeudi 2 mars 2017 11:29 À : Pharo
> > > > Development List Cc : Moose-related development Objet :
> > > > [Moose-dev] Re: [Pharo-dev] Segmentation fault on Moose 6.1 Build
> > > >
> > > > Hi,
> > > >
> > > > Was there a change related to the stable VM?
> > > >
> > > > Cheers,
> > > > Doru
> > > >
> > > >
> > > > > On Mar 2, 2017, at 11:23 AM, Blondeau Vincent
> > > >  wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > The latest builds of the Moose6.1 image are failing due to a
> > > > > segmentation
> > > > fault.
> > > > > Here is the link to the last build:
> > > > > https://ci.inria.fr/moose/job/moose-6.1/550/console
> > > > >
> > > > > How can we fix this?
> > > > >
> > > > > Thanks in advance,
> > > > >
> > > > > Cheers,
> > > > > Vincent
> > > > >
> > > > >
> > > > >
> > > >
> !!!
> > > > ***
> > > > > ** "Ce message et les pièces jointes sont
> > > > > confidentiels et réservés à l'usage exclusif de ses
> > > > > destinataires. Il peut
> > > > également être protégé par le secret professionnel. Si vous
> > > > recevez ce message par erreur, merci d'en avertir immédiatement
> > > > l'expéditeur et de le détruire. L'intégrité du message ne pouvant
> > > > être assurée sur Internet, la responsabilité de Worldline ne
> > > > pourra être recherchée quant au contenu de ce message. Bien que
> > > > les meilleurs efforts soient faits pour maintenir cette
> > > > transmission exempte de tout virus, l'expéditeur ne donne aucune
> > > > garantie à cet égard et sa responsabilité ne saurait être recherchée
> pour tout dommage résultant d'un virus transmis.
> > > > >
> > > > > This e-mail and the documents attached are confidential and
> > > > > intended
> > > > solely for the addressee; it may also be privileged. If you
> > > > receive this e-mail in error, please notify the sender immediately
> > > > and destroy it. As its integrity cannot be secured on the
> > > > Internet, the Worldline liability cannot be triggered for the
> > > > message content. Although the sender endeavours to maintain a
> > > > computer virus-free network, the sender does not warrant that this
> > > > transmission is virus-free and will not be liable for any damages
> resulting from any virus transmitted.!!!"
> > > > > 
> > > >
> > > > --
> > > > www.tudorgirba.com
> > > > www.feenk.com
> 

Re: [Pharo-dev] [Moose-dev] Re: Segmentation fault on Moose 6.1 Build

[Blondeau Vincent]

I heard that the gc compactor have changed.

Cheers,
Vincent

> -Message d'origine-
> De : Moose-dev [mailto:moose-dev-boun...@list.inf.unibe.ch] De la part de
> Tudor Girba
> Envoyé : jeudi 2 mars 2017 11:29
> À : Pharo Development List
> Cc : Moose-related development
> Objet : [Moose-dev] Re: [Pharo-dev] Segmentation fault on Moose 6.1 Build
>
> Hi,
>
> Was there a change related to the stable VM?
>
> Cheers,
> Doru
>
>
> > On Mar 2, 2017, at 11:23 AM, Blondeau Vincent
>  wrote:
> >
> > Hi,
> >
> > The latest builds of the Moose6.1 image are failing due to a segmentation
> fault.
> > Here is the link to the last build:
> > https://ci.inria.fr/moose/job/moose-6.1/550/console
> >
> > How can we fix this?
> >
> > Thanks in advance,
> >
> > Cheers,
> > Vincent
> >
> >
> >
> !!!
> ***
> > ** "Ce message et les pièces jointes sont
> > confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut
> également être protégé par le secret professionnel. Si vous recevez ce
> message par erreur, merci d'en avertir immédiatement l'expéditeur et de le
> détruire. L'intégrité du message ne pouvant être assurée sur Internet, la
> responsabilité de Worldline ne pourra être recherchée quant au contenu de
> ce message. Bien que les meilleurs efforts soient faits pour maintenir cette
> transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à
> cet égard et sa responsabilité ne saurait être recherchée pour tout dommage
> résultant d'un virus transmis.
> >
> > This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive this 
> e-mail in
> error, please notify the sender immediately and destroy it. As its integrity
> cannot be secured on the Internet, the Worldline liability cannot be triggered
> for the message content. Although the sender endeavours to maintain a
> computer virus-free network, the sender does not warrant that this
> transmission is virus-free and will not be liable for any damages resulting
> from any virus transmitted.!!!"
> > 
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> “Live like you mean it."
>
> ___
> Moose-dev mailing list
> moose-...@list.inf.unibe.ch
> https://www.list.inf.unibe.ch/listinfo/moose-dev

!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

[Pharo-dev] Segmentation fault on Moose 6.1 Build

[Blondeau Vincent]

Hi,

The latest builds of the Moose6.1 image are failing due to a segmentation fault.
Here is the link to the last build: 
https://ci.inria.fr/moose/job/moose-6.1/550/console

How can we fix this?

Thanks in advance,

Cheers,
Vincent


!!!*
"Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"
Segmentation fault Thu Mar  2 02:38:37 2017


/builds/workspace/moose-6.1/pharo-vm/pharo
Pharo VM version: 5.0-201702221539  Wed Feb 22 15:46:29 UTC 2017 gcc 4.6.3 
[Production Spur ITHB VM]
Built from: CoInterpreter * VMMaker.oscog-EstebanLorenzano.2136 uuid: 
40534c32-ca6b-4e97-91ec-31d509e49b0c Feb 22 2017
With: StackToRegisterMappingCogit * VMMaker.oscog-EstebanLorenzano.2136 uuid: 
40534c32-ca6b-4e97-91ec-31d509e49b0c Feb 22 2017
Revision: VM: 201702221539 https://github.com/pharo-project/pharo-vm.git $ 
Date: Wed Feb 22 16:39:40 2017 +0100 $ Plugins: 201702221539 
https://github.com/pharo-project/pharo-vm.git $
Build host: Linux testing-docker-9b911eb3-3e93-4fc4-acb7-571482555639 
4.8.12-040812-generic #201612020431 SMP Fri Dec 2 09:33:31 UTC 2016 i686 i686 
i386 GNU/Linux
plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: 
/builds/workspace/moose-6.1/pharo-vm/]


C stack backtrace & registers:
eax 0xbfce26a4 ebx 0xbfce25c0 ecx 0xbfce2658 edx 0xbfce260c
edi 0xbfce2490 esi 0xbfce2490 ebp 0xbfce2528 esp 0xbfce2574
eip 0xbfce2788
*[0xbfce2788]
/builds/workspace/moose-6.1/pharo-vm/pharo[0x806016f]
/builds/workspace/moose-6.1/pharo-vm/pharo[0x80604d6]
[0xb77a640c]
[0xb735c000]
[0xa157e87]
[0xa157bdc]
[0xa189dd8]
[0xa101adc]
[0xa100ff0]
[0xa100fc0]
[0x178]


Smalltalk stack dump:
0xbfce7648 M GrafPort>copyBits 0xa2bb340: a(n) GrafPort
0xbfce7660 M GrafPort>image:at:sourceRect:rule: 0xa2bb340: a(n) GrafPort
0xbfce7688 M FormCanvas>image:at:sourceRect:rule: 0xa2b1690: a(n) FormCanvas
0xbfce76b8 M [] in TRMorph>drawOn: 0xa2b1708: a(n) TRMorph
0xbfce76d0 M BlockClosure>on:do: 0xa40d698: a(n) BlockClosure
0xbfce76fc I TRMorph>drawOn: 0xa2b1708: a(n) TRMorph
0xbfce53a8 M FormCanvas(Canvas)>draw: 0xa2b1690: a(n) FormCanvas
0xbfce53c4 M FormCanvas(Canvas)>drawMorph: 0xa2b1690: a(n) FormCanvas
0xbfce53e4 M [] in TRMorph(Morph)>fullDrawOn: 0xa2b1708: a(n) TRMorph
0xbfce53fc M FormCanvas>roundCornersOf:in:during: 0xa2b1690: a(n) FormCanvas
0xbfce5420 M FormCanvas(Canvas)>roundCornersOf:during: 0xa2b1690: a(n) 
FormCanvas
0xbfce5444 M [] in TRMorph(Morph)>fullDrawOn: 0xa2b1708: a(n) TRMorph
0xbfce545c M BlockClosure>on:do: 0xa2b17d8: a(n) BlockClosure
0xbfce547c M TRMorph(Morph)>fullDrawOn: 0xa2b1708: a(n) TRMorph
0xbfce5498 M FormCanvas(Canvas)>fullDraw: 0xa2b1690: a(n) FormCanvas
0xbfce54b4 M FormCanvas(Canvas)>fullDrawMorph: 0xa2b1690: a(n) FormCanvas
0xbfce54d4 M [] in GLMPanelMorph(Morph)>drawSubmorphsOn: 0xa2b1868: a(n) 
GLMPanelMorph
0xbfce54f4 M Array(SequenceableCollection)>reverseDo: 0xa2b18a8: a(n) Array
0xbfce5510 M [] in GLMPanelMorph(Morph)>drawSubmorphsOn: 0xa2b1868: a(n) 
GLMPanelMorph
0xbfce552c M FormCanvas>clipBy:during: 0xa2b1930: a(n) FormCanvas
0xbfce5550 M GLMPanelMorph(Morph)>drawSubmorphsOn: 0xa2b1868: a(n) GLMPanelMorph
0xbfce5570 M [] in GLMPanelMorph(Morph)>fullDrawOn: 0xa2b1868: a(n) 
GLMPanelMorph
0xbfce5588 M FormCanvas>roundCornersOf:in:during: 0xa2b1930: a(n) FormCanvas
0xbfce55ac M FormCanvas(Canvas)>roundCornersOf:during: 0xa2b1930: a(n) 
FormCanvas
0xbfce55d0 M [] in GLMPanelMorph(Morph)>fullDrawOn: 0xa2b1868: a(n) 
GLMPanelMorph
0xbfce55e8 M BlockClosure>on:do: 0xa2b1a40: a(n) BlockClosure
0xbfce5608 M GLMPanelMorph(Morph)>fullDrawOn: 0xa2b1868: a(n) GLMPanelMorph
0xbfce5624 M FormCanvas(Canvas)>fullDraw: 0xa2b1930: a(n) FormCanvas
0xbfce5640 M FormCanvas(Canvas)>fullDrawMorph: 0xa2b1930: a(n) FormCanvas
0xbfce5660 M

[Pharo-dev] Crash.dmp not created on windows

[Blondeau Vincent]

Hello,

Since the release of the spur vm, the crash dump file (crash.dmp) is not 
generated when the image crashes under Windows (7 especially).
Now, I have an image I cannot use because its crashed at startup and I cannot 
report a bug to VM developers in the purpose to resolve the crash.

An issue on this has been opened almost for one year:
https://pharo.fogbugz.com/f/cases/17506/when-an-Image-crashes-a-crash-dmp-file-is-created-but-nothing-is-written-to-it-Windows

Does the creation of this crash.dmp is planned?

Thanks in advance,

Cheers,
Vincent


!!!*
"Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] [Moose-dev] Re: Segfault on Moose 6.1 jobs

[Blondeau Vincent]

Thanks Eliot,

However, I use this URL to get Pharo vm: http://get.pharo.org/60+vmLatest. The 
zip file (here: http://files.pharo.org/get-files/60/) was created on October 
12, 2016.

Did you mean that I do not get the latest one for Pharo60?

Vincent

De : Moose-dev [mailto:moose-dev-boun...@list.inf.unibe.ch] De la part de Eliot 
Miranda
Envoyé : mercredi 16 novembre 2016 18:41
À : Pharo Development List
Cc : Moose-related development
Objet : [Moose-dev] Re: [Pharo-dev] Segfault on Moose 6.1 jobs

Hi Vincent,

On Wed, Nov 16, 2016 at 2:56 AM, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:
Hello,

I would like to report some random segfaults happing during the build of the 
Moose 6.1 image (based on Pharo 6).
Please find attached the latest failing stack trace.

Here are the 2 jobs that fails:
https://ci.inria.fr/moose/job/moose-6.1/345/console
https://ci.inria.fr/moose/job/moose-6.1/347/console

It seems that they are not failing for the same reason.

Maybe because the job is not using the latest VM? :

pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production 
Spur ITHB VM]
Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 
16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016

Yes, this is very old.  I suggest you update to something around VMMaker 1776 
at the start of November.  Right now there is a little instability from the 
LLP64 work for Win64, otherwise I would recommend the tip.

With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 
uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
Revision: https://github.com/pharo-project/pharo-vm.git Commit: 
9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: 
GitHub mailto:nore...@github.com>> Jenkins build #594
Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 
16:39:45 UTC 2012 i686 i686 i386 GNU/Linux
plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: 
/builds/workspace/moose-6.1/pharo-vm/]

Thanks in advance

Cheers,
Vincent


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"



--
_,,,^..^,,,_
best, Eliot

!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

[Pharo-dev] Segfault on Moose 6.1 jobs

[Blondeau Vincent]

Hello,

I would like to report some random segfaults happing during the build of the 
Moose 6.1 image (based on Pharo 6).
Please find attached the latest failing stack trace.

Here are the 2 jobs that fails:
https://ci.inria.fr/moose/job/moose-6.1/345/console
https://ci.inria.fr/moose/job/moose-6.1/347/console

It seems that they are not failing for the same reason.

Maybe because the job is not using the latest VM? :

pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production 
Spur ITHB VM]
Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 
16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 
uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
Revision: https://github.com/pharo-project/pharo-vm.git Commit: 
9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: 
GitHub  Jenkins build #594
Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 
16:39:45 UTC 2012 i686 i686 i386 GNU/Linux
plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: 
/builds/workspace/moose-6.1/pharo-vm/]

Thanks in advance

Cheers,
Vincent


!!!*
"Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"
Segmentation fault Wed Nov 16 11:36:49 2016


/builds/workspace/moose-6.1/pharo-vm/pharo
pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production 
Spur ITHB VM]
Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 
16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 
uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
Revision: https://github.com/pharo-project/pharo-vm.git Commit: 
9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: 
GitHub  Jenkins build #594
Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 
16:39:45 UTC 2012 i686 i686 i386 GNU/Linux
plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: 
/builds/workspace/moose-6.1/pharo-vm/]


C stack backtrace & registers:
eax 0xbfee7204 ebx 0xbfee7120 ecx 0xbfee71b8 edx 0xbfee716c
edi 0xbfee6ff0 esi 0xbfee6ff0 ebp 0xbfee7088 esp 0xbfee70d4
eip 0xbfee72e8
*[0xbfee72e8]
/builds/workspace/moose-6.1/pharo-vm/pharo[0x80c11b2]
/builds/workspace/moose-6.1/pharo-vm/pharo[0x80c1516]
[0xb772040c]
/builds/workspace/moose-6.1/pharo-vm/pharo(isWords+0xb)[0x8080a1b]
/builds/workspace/moose-6.1/pharo-vm/pharo[0x80d36ee]
/builds/workspace/moose-6.1/pharo-vm/pharo[0x80d7db8]
[0x9900bd0]
[0x994081d]
[0x994054c]
[0x9900b70]
[0x9901714]
[0x9900b70]
[0x9900b40]
[0x442]


Smalltalk stack dump:
0xbff1f170 M GrafPort>copyBits 0x9a07440: a(n) GrafPort
0xbff1f188 M GrafPort>image:at:sourceRect:rule: 0x9a07440: a(n) GrafPort
0xbff1f1b0 M FormCanvas>image:at:sourceRect:rule: 0x9a05738: a(n) FormCanvas
0xbff1f1e8 I [] in TRMorph>drawOn: 0x9a00fc0: a(n) TRMorph
0xbff1f200 M BlockClosure>on:do: 0x9a074e8: a(n) BlockClosure
0xbff1f22c I TRMorph>drawOn: 0x9a00fc0: a(n) TRMorph
0xbfef0efc M FormCanvas(Canvas)>draw: 0x9a05738: a(n) FormCanvas
0xbfef0f18 M FormCanvas(Canvas)>drawMorph: 0x9a05738: a(n) FormCanvas
0xbfef0f38 M [] in TRMorph(Morph)>fullDrawOn: 0x9a00fc0: a(n) TRMorph
0xbfef0f50 M FormCanvas>roundCornersOf:in:during: 0x9a05738: a(n) FormCanvas
0xbfef0f74 M FormCanvas(Canvas)>roundCornersOf:during: 0x9a05738: a(n) 
FormCanvas
0xbfef0f98 M [] in TRMorph(Morph)>fullDrawOn: 0x9a00fc0: a(n) TRMorph
0xbfef0fb0 M BlockClosure>on:do: 0x9a05838: a(n) BlockClosure
0xbfef0fd0 M TRMorph(Morph)>fullDrawOn: 0x9a00fc0: a(n) TRMorph
0xbfef0fec M FormCanvas(Canvas)>fullDraw: 0x9a05738: a(n) FormCanvas
0xbfef1008 M 

Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC

[Blondeau Vincent]

You can make links that never expires (unless you deactivate them) (else it is 
30 minutes):
https://discord.gg/jyVT2dp

Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Esteban 
Lorenzano
Envoyé : mardi 25 octobre 2016 09:27
À : Pharo Development List
Objet : Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC

instant invites expires very fast.
I will be sending a new one before the meeting.

Esteban

On 25 Oct 2016, at 04:57, Hernán Morales Durand 
mailto:hernan.mora...@gmail.com>> wrote:


16:00 UTC is 13:00hs in Argentina but the link now (23:57hs) says "The instant 
invite is invalid or has expired"

2016-10-24 12:08 GMT-03:00 p...@highoctane.be<mailto:p...@highoctane.be> 
mailto:p...@highoctane.be>>:
https://discord.gg/EBDhD

On Mon, Oct 24, 2016 at 4:44 PM, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:
I think that his tomorrow is Tuesday, because he sent the email Monday (CEST).
But, I will be interested by a link to find the TechTalk on discord too.

Thanks

Vincent

> -Message d'origine-
> De : Pharo-dev 
> [mailto:pharo-dev-boun...@lists.pharo.org<mailto:pharo-dev-boun...@lists.pharo.org>]
>  De la part de
> Dale Henrichs
> Envoyé : lundi 24 octobre 2016 16:35
> À : pharo-dev@lists.pharo.org<mailto:pharo-dev@lists.pharo.org>
> Objet : Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC
>
> Hmmm... since Esteban sent the email at 1 am my time and this _is_
> tomorrow for me ... but perhaps Esteban means Tuesday? since I think this is
> still _today_ in Europe?
>
> Dale
>
>
> On 10/24/16 7:31 AM, Dale Henrichs wrote:
> > Since time is short (for me) and I still have to get out ouf bed,
> > shower eat and maybe get into the office before the meeting ... could
> > someone drop me an email with the details I need to find and install
> > (?) discord and find the techtalk ... I'll be out of pocket for about
> > an hour getting ready --- as this is short notice (for me) ---
> >
> > Thanks,
> >
> > Dale
> >
> > On 10/24/16 12:58 AM, Esteban Lorenzano wrote:
> >> Hello fellow pharoers,
> >>
> >> The time has come (1 month passes so fast!). And tomorrow we will be
> >> handling another TechTalk.
> >> This time we propose to talk about the new Bootstrap process.
> >>
> >> For this, I’d ask Guille, Pavel and/or Christophe to be present. They
> >> are the ones actually working on it, so we’ll all learn from what
> >> they have to say :)
> >>
> >> Meeting will be handled with discord, as last time.
> >>
> >> And as always, this will also be a place to ask anything about pharo
> >> development (statuses, proposals, etc., etc., etc.)
> >>
> >> See you tomorrow !
> >>
> >> Esteban
> >
>


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"




!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maint

Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC

[Blondeau Vincent]

I think that his tomorrow is Tuesday, because he sent the email Monday (CEST).
But, I will be interested by a link to find the TechTalk on discord too.

Thanks

Vincent

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Dale Henrichs
> Envoyé : lundi 24 octobre 2016 16:35
> À : pharo-dev@lists.pharo.org
> Objet : Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC
>
> Hmmm... since Esteban sent the email at 1 am my time and this _is_
> tomorrow for me ... but perhaps Esteban means Tuesday? since I think this is
> still _today_ in Europe?
>
> Dale
>
>
> On 10/24/16 7:31 AM, Dale Henrichs wrote:
> > Since time is short (for me) and I still have to get out ouf bed,
> > shower eat and maybe get into the office before the meeting ... could
> > someone drop me an email with the details I need to find and install
> > (?) discord and find the techtalk ... I'll be out of pocket for about
> > an hour getting ready --- as this is short notice (for me) ---
> >
> > Thanks,
> >
> > Dale
> >
> > On 10/24/16 12:58 AM, Esteban Lorenzano wrote:
> >> Hello fellow pharoers,
> >>
> >> The time has come (1 month passes so fast!). And tomorrow we will be
> >> handling another TechTalk.
> >> This time we propose to talk about the new Bootstrap process.
> >>
> >> For this, I’d ask Guille, Pavel and/or Christophe to be present. They
> >> are the ones actually working on it, so we’ll all learn from what
> >> they have to say :)
> >>
> >> Meeting will be handled with discord, as last time.
> >>
> >> And as always, this will also be a place to ask anything about pharo
> >> development (statuses, proposals, etc., etc., etc.)
> >>
> >> See you tomorrow !
> >>
> >> Esteban
> >
>


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] [Pharo-users] [ANN] RProjectConnector V2.1

[Blondeau Vincent]

> -Message d'origine-
> De : Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] De la part de
> Serge Stinckwich
> Envoyé : mercredi 14 septembre 2016 15:09
> À : Any question about pharo is welcome
> Cc : scismallt...@googlegroups.com; Pharo Development List
> Objet : Re: [Pharo-users] [Pharo-dev] [ANN] RProjectConnector V2.1
>
> Hi Vincent,
>
Hi Serge,


> Ok I try again with the latest Pharo 6.0.
>
> When I evaluate:
>
> Gofer it smalltalkhubUser: 'VincentBlondeau' project:
> 'RProjectConnector'; configuration; loadStable There is an error : could not
> resolve Rconnector. Apparently there is a problem with the package name,
> because this vincentBlondeau and not VincentBlondeau (Uppercase). Did you
> already try your configuration in an empty Pharo 6.0 image ? :-)

Not really for this one ... I corrected and it should work now ;)
>
> I was able to load RConnector-vincentBlondeau.72 directly from Monticello
> repo.
> I modify the RLibrary>>macModuleName path name to
> /usr/local/Cellar/r/3.3.1_2/R.framework/Versions/3.3/Resources/lib/libR.dyl
> ib
> When I relaunch my image, I have an error: the R session is not well
> initialized at startup.
>
> In RSession>>isExistsRf_initEmbeddedR I still see a reference to Alien class.
> You are still using Alien ?
>

Because I didn't found something better before. But, I just looked at it and 
changed to ExternalAddress method.

Can you try again with version 73 ?

Thanks,
Vincent

>
>
> On Tue, Sep 13, 2016 at 6:25 PM, Blondeau Vincent
>  wrote:
> >
> >
> >
> >> -Message d'origine-
> >> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part
> >> de Serge Stinckwich Envoyé : vendredi 2 septembre 2016 16:44 À :
> >> Pharo Development List Cc : scismallt...@googlegroups.com; Any
> >> question about pharo is welcome Objet : Re: [Pharo-dev] [ANN]
> >> RProjectConnector V2.1
> >>
> >> Great job Vincent !
> >>
> > It will be great when it will work on OS X ;)
> >
> >> There is some problems on Mac OS X:
> >> - when I try to load in a fresh Pharo 5.0 image, I got a DNU on:
> >> RObjectArray class>>initElementType:
> >> I was able to load the package after a while by loading directly the
> >> package with the Monticello Browser
> >
> > Strange, I deleted these methods... Please ensure you are using a Pharo 6.0
> image (it should work under Pharo 5.0 too) and that version 14 of
> ConfigurationOfRProjectConnector and version 71 of the RConnector
> packages are loaded.
> >
> >> - Apparently there is still some methods using NB like: RSession
> >> class>>checkSession or RSession class>>initEmbeddedR:
> >
> > Should not, it is modified ...
> >
> >>
> >> I try to move the R dll close to my Pharo VM and also inside the
> >> Plugins directory but without success ...
> >
> > It should be at the same location that libcairo.2.dylib
> >
> >> Is there a way to say where are the R dll instead of copying them ?
> >>
> > Didn't think so .. Maybe the VM developers knows ?
> >
> >
> > Thanks!
> >
> > Vincent
> >
> >
> >> Thank you.
> >>
> >>
> >>
> >>
> >> On Thu, Sep 1, 2016 at 5:42 PM, Blondeau Vincent
> >>  wrote:
> >> > Hello everyone,
> >> >
> >> >
> >> >
> >> > I am glad to announce the release of version 2.1 of the
> RProjectConnector.
> >> >
> >> > The binding between Pharo and R (https://www.r-project.org/) is now
> >> > translated to UFFI and so to Pharo 6.0.
> >> >
> >> >
> >> >
> >> > You can call directly your R methods from Pharo. For example, with
> >> > the famous iris clustering example:
> >> >
> >> >
> >> >
> >> >   iris := 'eval' asREval: {RObject findVar: 'iris'}.
> >> >
> >> >   'plot'
> >> >
> >> > asREval:
> >> >
> >> > {(iris at: 'Petal.Length').
> >> >
> >> > (iris at: 'Petal.Width').
> >> >
> >> > (#pch -> 21).
> >> >
> >> > (#xlab -> 'length').
> >> >
> >> >  

Re: [Pharo-dev] [ANN] RProjectConnector V2.1

[Blondeau Vincent]

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Serge Stinckwich
> Envoyé : vendredi 2 septembre 2016 16:44
> À : Pharo Development List
> Cc : scismallt...@googlegroups.com; Any question about pharo is welcome
> Objet : Re: [Pharo-dev] [ANN] RProjectConnector V2.1
>
> Great job Vincent !
>
It will be great when it will work on OS X ;)

> There is some problems on Mac OS X:
> - when I try to load in a fresh Pharo 5.0 image, I got a DNU on:
> RObjectArray class>>initElementType:
> I was able to load the package after a while by loading directly the package
> with the Monticello Browser

Strange, I deleted these methods... Please ensure you are using a Pharo 6.0 
image (it should work under Pharo 5.0 too) and that version 14 of 
ConfigurationOfRProjectConnector and version 71 of the RConnector packages are 
loaded.

> - Apparently there is still some methods using NB like: RSession
> class>>checkSession or RSession class>>initEmbeddedR:

Should not, it is modified ...

>
> I try to move the R dll close to my Pharo VM and also inside the Plugins
> directory but without success ...

It should be at the same location that libcairo.2.dylib

> Is there a way to say where are the R dll instead of copying them ?
>
Didn't think so .. Maybe the VM developers knows ?


Thanks!

Vincent


> Thank you.
>
>
>
>
> On Thu, Sep 1, 2016 at 5:42 PM, Blondeau Vincent
>  wrote:
> > Hello everyone,
> >
> >
> >
> > I am glad to announce the release of version 2.1 of the RProjectConnector.
> >
> > The binding between Pharo and R (https://www.r-project.org/) is now
> > translated to UFFI and so to Pharo 6.0.
> >
> >
> >
> > You can call directly your R methods from Pharo. For example, with the
> > famous iris clustering example:
> >
> >
> >
> >   iris := 'eval' asREval: {RObject findVar: 'iris'}.
> >
> >   'plot'
> >
> > asREval:
> >
> > {(iris at: 'Petal.Length').
> >
> > (iris at: 'Petal.Width').
> >
> > (#pch -> 21).
> >
> > (#xlab -> 'length').
> >
> > (#ylab -> 'Width').
> >
> > (#bg  ->((iris at: 'Species') collect:
> > [ :value | {'red'. 'green3'. 'blue'} at: value ])).
> >
> > (#main -> 'Edgar Anderson''s Iris Data')}.
> >
> >   iris inspect.
> >
> >
> >
> > To use it, you should install R and copy the R libraries near the
> > Pharo VM (see the documentation on SmalltalkHub
> > (http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector) for
> > how to proceed).
> >
> >
> >
> > Don’t forget to relaunch Pharo after the installation to be able to
> > use the connector.
> >
> >
> >
> > Only basic features are implemented yet, but you can participate to
> > its extension!
> >
> >
> >
> > Cheers,
> >
> > Vincent Blondeau
> >
> >
> >
> !!!
> ***
> > ** "Ce message et les pièces jointes sont
> > confidentiels et réservés à l'usage exclusif de ses destinataires. Il
> > peut également être protégé par le secret professionnel. Si vous
> > recevez ce message par erreur, merci d'en avertir immédiatement
> > l'expéditeur et de le détruire. L'intégrité du message ne pouvant être
> > assurée sur Internet, la responsabilité de Worldline ne pourra être
> > recherchée quant au contenu de ce message. Bien que les meilleurs
> > efforts soient faits pour maintenir cette transmission exempte de tout
> > virus, l'expéditeur ne donne aucune garantie à cet égard et sa
> > responsabilité ne saurait être recherchée pour tout dommage résultant
> > d'un virus transmis.
> >
> > This e-mail and the documents attached are confidential and intended
> > solely for the addressee; it may also be privileged. If you receive
> > this e-mail in error, please notify the sender immediately and destroy
> > it. As its integrity cannot be secured on the Internet, the Worldline
> > liability cannot be triggered for the message content. Although the
> > sender endeavours to maintain a computer virus-fr

Re: [Pharo-dev] [Pharo-users] [ANN] RProjectConnector V2.1

[Blondeau Vincent]

Sorry, I haven’t a Mac.

First, you have to install R.
Then, I think you should only have to copy the R libraries (somewhere in the 
disk^^) to the Pharo VM folder.

Tell me if it works ;)

Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de 
Alexandre Bergel
Envoyé : jeudi 1 septembre 2016 17:49
À : Any question about pharo is welcome
Cc : scismallt...@googlegroups.com; Pharo Development List
Objet : Re: [Pharo-dev] [Pharo-users] [ANN] RProjectConnector V2.1

I wanted to try, but there is no installation instruction for OS X :-(
Can you produce some on OS X? It would be great

Anyway, this is great Vincent! Keep pushing!

Alexandre


On Sep 1, 2016, at 12:42 PM, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:

Hello everyone,

I am glad to announce the release of version 2.1 of the RProjectConnector.
The binding between Pharo and R (https://www.r-project.org/) is now translated 
to UFFI and so to Pharo 6.0.

You can call directly your R methods from Pharo. For example, with the famous 
iris clustering example:

  iris := 'eval' asREval: {RObject findVar: 'iris'}.
  'plot'
asREval:
{(iris at: 'Petal.Length').
(iris at: 'Petal.Width').
(#pch -> 21).
(#xlab -> 'length').
(#ylab -> 'Width').
(#bg  ->((iris at: 'Species') collect: [ :value 
| {'red'. 'green3'. 'blue'} at: value ])).
(#main -> 'Edgar Anderson''s Iris Data')}.
  iris inspect.

To use it, you should install R and copy the R libraries near the Pharo VM (see 
the documentation on SmalltalkHub 
(http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector) for how to 
proceed).


Don’t forget to relaunch Pharo after the installation to be able to use the 
connector.

Only basic features are implemented yet, but you can participate to its 
extension!

Cheers,
Vincent Blondeau

!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

[Pharo-dev] [ANN] RProjectConnector V2.1

[Blondeau Vincent]

Hello everyone,

I am glad to announce the release of version 2.1 of the RProjectConnector.
The binding between Pharo and R (https://www.r-project.org/) is now translated 
to UFFI and so to Pharo 6.0.

You can call directly your R methods from Pharo. For example, with the famous 
iris clustering example:

  iris := 'eval' asREval: {RObject findVar: 'iris'}.
  'plot'
asREval:
{(iris at: 'Petal.Length').
(iris at: 'Petal.Width').
(#pch -> 21).
(#xlab -> 'length').
(#ylab -> 'Width').
(#bg  ->((iris at: 'Species') collect: [ :value 
| {'red'. 'green3'. 'blue'} at: value ])).
(#main -> 'Edgar Anderson''s Iris Data')}.
  iris inspect.

To use it, you should install R and copy the R libraries near the Pharo VM (see 
the documentation on SmalltalkHub 
(http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector) for how to 
proceed).


Don't forget to relaunch Pharo after the installation to be able to use the 
connector.

Only basic features are implemented yet, but you can participate to its 
extension!

Cheers,
Vincent Blondeau

!!!*
"Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] VTermOutputDriver

[Blondeau Vincent]

That is not the point… Look at the end:

MessageNotUnderstood: receiver of "nextPutAll:" is nil
UndefinedObject(Object)>>doesNotUnderstand: #nextPutAll:
TermInfoCharacter>>print:
TermInfoCharacter>>set:
TermInfoCharacter>>color:
VTermOutputDriver>>color:
VTermOutputDriver>>yellow:
ImageWorker>>inform:


De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de 
Valentin Ryckewaert
Envoyé : lundi 11 juillet 2016 10:43
À : Pharo Development List
Objet : Re: [Pharo-dev] VTermOutputDriver

It looks like it's a problem of deleted methods executed (I deleted the method 
reset for example)
I don't really see what i can do to solve this...

2016-07-11 10:39 GMT+02:00 Blondeau Vincent 
mailto:vincent.blond...@worldline.com>>:
Hi,

You should check the stacktrace : 
https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/5662/console

Cheers,
Vincent

De : Pharo-dev 
[mailto:pharo-dev-boun...@lists.pharo.org<mailto:pharo-dev-boun...@lists.pharo.org>]
 De la part de Valentin Ryckewaert
Envoyé : lundi 11 juillet 2016 10:35
À : Pharo Development List
Objet : [Pharo-dev] VTermOutputDriver

Hello everyone,

I don't understand why my slice isn't working, could someone help me please? I 
just need a clue and I could fix the problem :)

https://pharo.fogbugz.com/f/cases/18650

Thanks,
Valentin

!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] VTermOutputDriver

[Blondeau Vincent]

Hi,

You should check the stacktrace : 
https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/5662/console

Cheers,
Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de 
Valentin Ryckewaert
Envoyé : lundi 11 juillet 2016 10:35
À : Pharo Development List
Objet : [Pharo-dev] VTermOutputDriver

Hello everyone,

I don't understand why my slice isn't working, could someone help me please? I 
just need a clue and I could fix the problem :)

https://pharo.fogbugz.com/f/cases/18650

Thanks,
Valentin

!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] [UFFI] Call a function where argument type is char ** (argv)

[Blondeau Vincent]

TL;DR: How to pass as argument an array of Strings (char **) with Unified-FFI?

Vincent

De : Blondeau Vincent
Envoyé : mercredi 25 mai 2016 13:58
À : Pharo Development List
Objet : [UFFI] Call a function where argument type is char ** (argv)

Hello,

I have written a R bridge in Pharo and I would like to migrate it from 
NativeBoost to UFFI.
Most of the changes are easy to do but I am stuck to a double pointer problem.
I have to call the function: int Rf_initEmbeddedR(int argc, char ** argv). I 
know how to give the int but the char ** is a problem. It is an array of 
Strings.

With NB, I managed to have this (working) code:
"This is 32bit... too bad..."
strings := OrderedCollection new.
par := NativeBoost allocate: 4 * params size.
params
keysAndValuesDo: [ :i :each |
| str |
str := each asNBExternalString.
strings add: str.
par nbUInt32AtOffset: (i - 1) * 
4 put: str value ].
self prim_initEmbeddedRargc: params size argv: par ]
ensure: [
"Free the memory we allocated"
par ifNotNil: [ par free ].
strings ifNotNil: [ strings do: 
[ :each | each free ] ] ]

With a primitive call:
Self nbCall: #(int Rf_initEmbeddedR(int argc, char *argv))

Do I still need to create my own array of strings or FFI creates it for me? How?

Thanks in advance for your answers,

Vincent


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

[Pharo-dev] [UFFI] Call a function where argument type is char ** (argv)

[Blondeau Vincent]

Hello,

I have written a R bridge in Pharo and I would like to migrate it from 
NativeBoost to UFFI.
Most of the changes are easy to do but I am stuck to a double pointer problem.
I have to call the function: int Rf_initEmbeddedR(int argc, char ** argv). I 
know how to give the int but the char ** is a problem.

With NB, I managed to have this (working) code:
"This is 32bit... too bad..."
strings := OrderedCollection new.
par := NativeBoost allocate: 4 * params size.
params
keysAndValuesDo: [ :i :each |
| str |
str := each asNBExternalString.
strings add: str.
par nbUInt32AtOffset: (i - 1) * 
4 put: str value ].
self prim_initEmbeddedRargc: params size argv: par ]
ensure: [
"Free the memory we allocated"
par ifNotNil: [ par free ].
strings ifNotNil: [ strings do: 
[ :each | each free ] ] ]

With a primitive call:
Self nbCall: #(int Rf_initEmbeddedR(int argc, char *argv))

Do I still need to create my own array of strings or FFI creates it for me? How?

Thanks in advance for your answers,

Vincent


!!!*
"Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] Looking for moderators and helpers for the Pharo Mooc

[Blondeau Vincent]

Me too.

Vincent

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Serge
> Stinckwich
> Envoyé : jeudi 28 avril 2016 14:45
> À : Pharo Development List
> Objet : Re: [Pharo-dev] Looking for moderators and helpers for the Pharo Mooc
>
> I can help.
>
>
> On Thu, Apr 28, 2016 at 8:43 PM, stepharo  wrote:
> > Hi guys
> >
> > We are looking for moderators and people to help in the forum on the mooc.
> >
> > Let me know if you want to help.
> >
> > Stef
> >
> >
>
>
>
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] [Pharo-users] Call about Numerical Methods in Pharo :)

[Blondeau Vincent]

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Serge Stinckwich
> Envoyé : jeudi 3 mars 2016 11:04
> À : Any question about pharo is welcome
> Cc : Didier Besset; Souissi Sami; Pharo Development List
> Objet : Re: [Pharo-dev] [Pharo-users] Call about Numerical Methods in Pharo
> :)
>
> On Thu, Mar 3, 2016 at 10:43 AM, Blondeau Vincent
>  wrote:
> > Hi,
> >
> > That's a very good idea.
> > For now, I use a Pharo-R binding to make the statistics, but it is better 
> > if it is
> directly in the image.
> >
> > For my part, it should be nice to have:
> > - Principal Component Analysis
> > - Time series
>
> I already a very simple time series class. What kind of operations you want to
> do on time series ?

For now, I am not using time series.
But one year ago, I was using Holt Winters and Seasonal Decomposition 
(HoltWinters and stl functions under R).
And it is possible that I reuse them in a close future.

>
> > - Correlation with several variables (Correlation matrix) +
> > significance tests (pearson, spearman...)
> > - Standard statistical tests: normality, variance, mean, distribution
> > - And the more important is to have nice tools to visualize the data (Box
> plot, histogram, scatterplots, PCA ones) with a simple API for standard things
> but that we can customize. The best is that we are able to draw regression
> lines on them. But I think that is more a Roassal part.
>
> You have to ask Alex to the viz :-)

;)
>
> Please join the SciSmalltalk ml in order to express your needs ;-)
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] [Pharo-users] Call about Numerical Methods in Pharo :)

[Blondeau Vincent]

Hi Alex,

This binding allows to execute (almost) any function provided by R via Native 
Calls.

You can find some documentation here: 
http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector
I just released a new stable version,  you should be able to load it from the 
catalog (Pharo40 only).
However, you must install R and copy the libraries in the VM folder (see doc).
And it is working only with pre-spur images (the migration to FFI has to be 
done).

Try to run the tests (in RConnector package). Iff they are green, you succeeded 
to configure the binding.

And you can plot the famous Iris Data:
iris := 'eval' asREval: { RObject findVar: 'iris' }.
'plot'
asREval:
{(iris at: 'Petal.Length').
(iris at: 'Petal.Width').
(#pch -> 21).
(#xlab -> 'length').
(#ylab -> 'Width').
(#bg  ->((iris at: 'Species') collect: [ :value 
| {'red'. 'green3'. 'blue'} at: value ])).
(#main -> 'Edgar Anderson''s Iris Data')}.


plot(iris$Petal.Length, iris$Petal.Width, pch=21, 
bg=c("red","green3","blue")[unclass(iris$Species)], main="Edgar Anderson's Iris 
Data")

is the genuine R function.

And inspect them:
iris inspect

You can use any collection of pharo and put it as argument, it should do the 
boxing automatically.

Warning: while testing new functions, don’t forget to save because evaluation 
of a non-existing R function throws a error that is not caught and makes Pharo 
crashing.

Cheers,
Vincent


De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de 
Alexandre Bergel
Envoyé : mardi 8 mars 2016 20:23
À : Any question about pharo is welcome
Cc : Didier Besset; Souissi Sami; Pharo Development List
Objet : Re: [Pharo-dev] [Pharo-users] Call about Numerical Methods in Pharo :)

Vincent, can you tell a bit more what this binding is about?
how can I try?

Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




On Mar 3, 2016, at 6:43 AM, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:

Hi,

That's a very good idea.
For now, I use a Pharo-R binding to make the statistics, but it is better if it 
is directly in the image.

For my part, it should be nice to have:
- Principal Component Analysis
- Time series
- Correlation with several variables (Correlation matrix) + significance tests 
(pearson, spearman...)
- Standard statistical tests: normality, variance, mean, distribution
- And the more important is to have nice tools to visualize the data (Box plot, 
histogram, scatterplots, PCA ones) with a simple API for standard things but 
that we can customize. The best is that we are able to draw regression lines on 
them. But I think that is more a Roassal part.

Thanks for the initiative,

Cheers,
Vincent


-Message d'origine-
De : Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] De la part de
stepharo
Envoyé : mercredi 2 mars 2016 14:17
À : Pharo Development List; Any question about pharo is welcome; Didier
Besset; Souissi Sami
Objet : [Pharo-users] Call about Numerical Methods in Pharo :)

Hi guys

I met Didier Besset and we had a great hacking session and discussions with
Serge Stinckwich.
Didier would like to help Pharo and the numerical part of it. ***Big
thanks*** Didier.

We would like to do several things:

- Work on "Hows to"
  The numerical methods in Pharo is good but the gap between us and the
math is too large :)
 so the idea is to have a series of "how to ..."
- histomgram (simple, based on distribution)

- Improve the SciPharo/NumPha (previously SciSmalltalk) library
This morning we started to implement a
ComponentPrincipalDecomposition by combining two of the
objects available in SciPharo.
Then we started to enhance the distributions to make sure that we can
plug other distribution for having
controlled random number.

- Do a public call to know what is missing for you: this is this mail :)
Didier would like to work on concrete cases. I love that attitude
So tell us :)

Hernan ??
Alex: ?? pvalue? better distribution?
Vincent: covariance? CPA?
Philippe: times series
Serge R frames?
Sami: Better random number and various distributions?

- Organise a two day lectures with practices on concrete case in September
with a recording session.
Either at IRD Bondy or Lille.

- Make sure that the Numerical Method book will get on lulu :) with a
better cover and title

Re: [Pharo-dev] [Pharo-users] Call about Numerical Methods in Pharo :)

[Blondeau Vincent]

Hi,

That's a very good idea.
For now, I use a Pharo-R binding to make the statistics, but it is better if it 
is directly in the image.

For my part, it should be nice to have:
- Principal Component Analysis
- Time series
- Correlation with several variables (Correlation matrix) + significance tests 
(pearson, spearman...)
- Standard statistical tests: normality, variance, mean, distribution
- And the more important is to have nice tools to visualize the data (Box plot, 
histogram, scatterplots, PCA ones) with a simple API for standard things but 
that we can customize. The best is that we are able to draw regression lines on 
them. But I think that is more a Roassal part.

Thanks for the initiative,

Cheers,
Vincent

> -Message d'origine-
> De : Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] De la part de
> stepharo
> Envoyé : mercredi 2 mars 2016 14:17
> À : Pharo Development List; Any question about pharo is welcome; Didier
> Besset; Souissi Sami
> Objet : [Pharo-users] Call about Numerical Methods in Pharo :)
>
> Hi guys
>
> I met Didier Besset and we had a great hacking session and discussions with
> Serge Stinckwich.
> Didier would like to help Pharo and the numerical part of it. ***Big
> thanks*** Didier.
>
> We would like to do several things:
>
>  - Work on "Hows to"
>The numerical methods in Pharo is good but the gap between us and the
> math is too large :)
>   so the idea is to have a series of "how to ..."
>  - histomgram (simple, based on distribution)
>
>  - Improve the SciPharo/NumPha (previously SciSmalltalk) library
>  This morning we started to implement a
> ComponentPrincipalDecomposition by combining two of the
>  objects available in SciPharo.
>  Then we started to enhance the distributions to make sure that we can
> plug other distribution for having
>  controlled random number.
>
>  - Do a public call to know what is missing for you: this is this mail :)
>  Didier would like to work on concrete cases. I love that attitude
>  So tell us :)
>
>  Hernan ??
>  Alex: ?? pvalue? better distribution?
>  Vincent: covariance? CPA?
>  Philippe: times series
>  Serge R frames?
>  Sami: Better random number and various distributions?
>
>  - Organise a two day lectures with practices on concrete case in 
> September
> with a recording session.
>  Either at IRD Bondy or Lille.
>
>  - Make sure that the Numerical Method book will get on lulu :) with a
> better cover and title :)
>
>
> Stef
>


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] What is the limit of prespur VM memory under Windows?

[Blondeau Vincent]

Hi Eliot,

I executed the cmd like advised in the link you gave me and change the ini file 
to AddressSpaceLimit=30
I got now 1384.4 Mo for a non-spur and 1778.0Mo for a spur thanks to the script 
of Paul.

But we still far of the 3Go…

Anyway, I tried again and it load all I wanted!

Thanks
Vincent


De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Eliot 
Miranda
Envoyé : lundi 29 février 2016 19:25
À : Pharo Development List
Objet : Re: [Pharo-dev] What is the limit of prespur VM memory under Windows?

Hi Clément,


On Feb 29, 2016, at 10:01 AM, Clément Bera 
mailto:bera.clem...@gmail.com>> wrote:
No.

The limit is supposed to be around 500 Mb on windows or 1 Gb for some 
specifically compiled VMs. 1 Gb VM may not start on windows, you may need to 
restart the computer before.

IIRC the default limit is 512Mb and that can be raised on the command line (or 
in an ini file ?).

But I think that at least Windows xo has a 2gb preprocessor limit by default.  
I remember that to go higher one needed to change how the system booted in 
win.ini.  See eg 
https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-enable-a-3GB-switch-on-Windows-Vista-Windows-7-or-Windows-XP-s.html



To bypass the limit the best way is to use a spur VM honestly. Spur32VMs are 
limited to around 2.7Gb on Windows.

+1 :)

_,,,^..^,,,_ (phone)


2016-02-29 18:53 GMT+01:00 Blondeau Vincent 
mailto:vincent.blond...@worldline.com>>:
Hi,


I am confronted with a memory issue under Windows.

I have an image of 745Mo with a Moose model, and I cannot instantiate a string 
of 30Mo: I get a OutOfMemoryException.

The theoretical limit is 2Go, isn’t it?



I have a prespur vm under a Windows 64 bits:
Smalltalk vm version:
'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 
4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec  3 2015
NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 
4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec  3 2015
https://github.com/pharo-project/pharo-vm.git Commit: 
28d077d8df494ce050ca42c97c892471e8b8740c Date: 2015-10-16 12:02:43 +0200 By: 
Esteban Lorenzano mailto:esteba...@gmail.com>> Jenkins 
build #15019

I set in Pharo.ini: AddressSpaceLimit=20



What can I do to bypass the issue?





Thanks in advance,

Vincent


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] What is the limit of prespur VM memory under Windows?

[Blondeau Vincent]

Thanks for the  script, it is very useful :)

By running it, I get:
Not spur image: 1143.0 Mo
Spur image: 1140.1 Mo

We are far than the 2Go... even for spur.

Vincent


> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Paul DeBruicker
> Envoyé : lundi 29 février 2016 18:42
> À : pharo-dev@lists.pharo.org
> Objet : Re: [Pharo-dev] What is the limit of prespur VM memory under
> Windows?
>
> A while ago Eliot Miranda posted this script to see when an image runs out of
> memory:
>
> | them |
> them := OrderedCollection new.
> [[them addLast: (ByteArray new: 1600).
> Transcript cr; show: ((Smalltalk vm parameterAt: 3) / (1024*1024.0)
> printShowingDecimalPlaces: 1); flush] repeat]
> on: OutOfMemory
> do: [:ex| 2 to: them size by: 2 do: [:i| them at: i put: nil. Smalltalk
> garbageCollect]].
> Transcript cr; show: ((Smalltalk vm parameterAt: 3) / (1024*1024.0)
> printShowingDecimalPlaces: 1); flush.
> them := nil.
> Smalltalk garbageCollect.
> Transcript cr; show: ((Smalltalk vm parameterAt: 3) / (1024*1024.0)
> printShowingDecimalPlaces: 1); flush
>
>
>
>
> its from
> here:http://forum.world.st/New-Cog-VMs-available-
> td4764823.html#a4764840
>
> With that you ought to easily be able to see how high you can go on a
> platform.
>
>
>
> Blondeau Vincent wrote
> > Hi,
> >
> >
> > I am confronted with a memory issue under Windows.
> >
> > I have an image of 745Mo with a Moose model, and I cannot instantiate
> > a string of 30Mo: I get a OutOfMemoryException.
> >
> > The theoretical limit is 2Go, isn't it?
> >
> >
> >
> > I have a prespur vm under a Windows 64 bits:
> > Smalltalk vm version:
> > 'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid:
> > 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec  3 2015 NBCogit
> > NativeBoost-CogPlugin-EstebanLorenzano.21 uuid:
> > 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec  3 2015
> > https://github.com/pharo-project/pharo-vm.git Commit:
> > 28d077d8df494ce050ca42c97c892471e8b8740c Date: 2015-10-16 12:02:43
> > +0200
> > By: Esteban Lorenzano <
>
> > estebanlm@
>
> > > Jenkins build #15019
> >
> > I set in Pharo.ini: AddressSpaceLimit=20
> >
> >
> >
> > What can I do to bypass the issue?
> >
> >
> >
> >
> >
> > Thanks in advance,
> >
> > Vincent
> >
> >
> >
> !!!
> ***
> > ** "Ce message et les pi?ces jointes sont
> > confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il
> > peut ?galement ?tre prot?g? par le secret professionnel. Si vous
> > recevez ce message par erreur, merci d'en avertir imm?diatement
> > l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre
> > assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre
> > recherch?e quant au contenu de ce message. Bien que les meilleurs
> > efforts soient faits pour maintenir cette transmission exempte de tout
> > virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa
> > responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant
> > d'un virus transmis.
> >
> > This e-mail and the documents attached are confidential and intended
> > solely for the addressee; it may also be privileged. If you receive
> > this e-mail in error, please notify the sender immediately and destroy
> > it. As its integrity cannot be secured on the Internet, the Worldline
> > liability cannot be triggered for the message content. Although the
> > sender endeavours to maintain a computer virus-free network, the
> > sender does not warrant that this transmission is virus-free and will
> > not be liable for any damages resulting from any virus transmitted.!!!"
>
>
>
>
>
> --
> View this message in context: http://forum.world.st/What-is-the-limit-of-
> prespur-VM-memory-under-Windows-tp4881619p4881625.html
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra êtr

[Pharo-dev] What is the limit of prespur VM memory under Windows?

[Blondeau Vincent]

Hi,


I am confronted with a memory issue under Windows.

I have an image of 745Mo with a Moose model, and I cannot instantiate a string 
of 30Mo: I get a OutOfMemoryException.

The theoretical limit is 2Go, isn't it?



I have a prespur vm under a Windows 64 bits:
Smalltalk vm version:
'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 
4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec  3 2015
NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 
4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec  3 2015
https://github.com/pharo-project/pharo-vm.git Commit: 
28d077d8df494ce050ca42c97c892471e8b8740c Date: 2015-10-16 12:02:43 +0200 By: 
Esteban Lorenzano  Jenkins build #15019

I set in Pharo.ini: AddressSpaceLimit=20



What can I do to bypass the issue?





Thanks in advance,

Vincent


!!!*
"Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] How to run a new image to execute a process

[Blondeau Vincent]

Hello,

The main problem under Windows is that the return value of the execution of the 
process cannot be received  because the stdin stdout streams are not integrated.
But I think you should be able to launch the process and to find a way to 
communicate between both images (Http or file change?).

If you just want to avoid freezing, you can try to fork the import process.

Cheers,
Vincent


De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de 
Guillaume Larcheveque
Envoyé : lundi 29 février 2016 14:01
À : Pharo Development List
Objet : [Pharo-dev] How to run a new image to execute a process

Hello,

I want to run the generation of a mooseModel in a new image with a new vm 
process (To avoid freezing or occupying space of my first one and also have 
more available memory).

I know i can use OSProcess but Cyril told me it will not work on Windows and i 
don't want to be platform dependent.

Do you see another solution to do that?

--
Guillaume Larcheveque

!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] Recursion inside #doesNotUnderstand: method. Why?

[Blondeau Vincent]

Hi,

Because when you are receiving a DNU, you have the possibility to implement the 
method before resuming the exception.
If you choose to implement the method, the message is sent again to the newly 
created method and the execution restarts.

Vincent


De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Denis 
Kudriashov
Envoyé : jeudi 25 février 2016 17:56
À : Discusses Development of Pharo
Objet : [Pharo-dev] Recursion inside #doesNotUnderstand: method. Why?

Hi.

Does anybody know why #doesNotUnderstand: is implemented with recursion at the 
end?

doesNotUnderstand: aMessage
| exception resumeValue |
(exception := MessageNotUnderstood new)
message: aMessage;
receiver: self.
resumeValue := exception signal.
^exception reachedDefaultHandler
ifTrue: [aMessage sentTo: self]
ifFalse: [resumeValue].

Best regards,
Denis

!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] Recursion inside #doesNotUnderstand: method. Why?

[Blondeau Vincent]

I don’t think so:

Put a halt here:
…ifTrue: [self halt. aMessage sentTo: self]…


1.   Open a playground

2.   Do: Object new toto

You should have a debugger that pops. Don’t close it.

3.   Go in Nautilus, implement toto on Object

4.   Click on proceed in the debugger.

You should have a Halt instead. And if you click on proceed  again, it should 
execute the toto method.
So it is used, and I frequently use it.

Cheers,
Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Denis 
Kudriashov
Envoyé : jeudi 25 février 2016 18:06
À : Discusses Development of Pharo
Objet : Re: [Pharo-dev] Recursion inside #doesNotUnderstand: method. Why?

Maybe in past it was used to create methods in debugger on the fly. But now it 
is not.
I just check it. I removed recursion logic and methods creation continue 
working in debugger. Maybe we should remove this strange behaviour

2016-02-25 17:56 GMT+01:00 Denis Kudriashov 
mailto:dionisi...@gmail.com>>:
Hi.

Does anybody know why #doesNotUnderstand: is implemented with recursion at the 
end?

doesNotUnderstand: aMessage
| exception resumeValue |
(exception := MessageNotUnderstood new)
message: aMessage;
receiver: self.
resumeValue := exception signal.
^exception reachedDefaultHandler
ifTrue: [aMessage sentTo: self]
ifFalse: [resumeValue].

Best regards,
Denis


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

Re: [Pharo-dev] ZTimestamp improvement

[Blondeau Vincent]

I implemented some tests for the slice. You should be able to reuse them.

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Sven Van Caekenberghe
> Envoyé : jeudi 25 février 2016 14:57
> À : Pharo Development List
> Objet : Re: [Pharo-dev] ZTimestamp improvement
>
> Yes I saw what you did and indeed the same fix needs to be applied to
> ZTimestamp. I will do it after adding some tests. Thx!
>
> > On 25 Feb 2016, at 14:06, Blondeau Vincent
>  wrote:
> >
> > Hello,
> >
> > I use Ztimestamp to parse a date but the time zone offset is wrongly set:
> > (DateAndTime readTimezoneOffsetFrom: '+0530' readStream) printString
> gives '0:05:00:00' instead of  '0:05:30:00'.
> > See https://pharo.fogbugz.com/f/cases/17693/Time-offset-parsing-is-false
> for the DateAndTime issue.
> >
> > As the bug is in DateAndTime>>readOptionalSeparatorFrom: and
> ZTimestamp reuses the same code, I propose to apply the same patch to it.
> > Can I have the commit access to the repo
> (http://smalltalkhub.com/#!/~SvenVanCaekenberghe/Neo) to submit the
> patch?
> >
> > Cheers,
> > Vincent
> >
> >
> >
> > Ce message et les pièces jointes sont confidentiels et réservés à l'usage
> exclusif de ses destinataires. Il peut également être protégé par le secret
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir
> immédiatement l'expéditeur et de le détruire. L'intégrité du message ne
> pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra
> être recherchée quant au contenu de ce message. Bien que les meilleurs
> efforts soient faits pour maintenir cette transmission exempte de tout virus,
> l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne
> saurait être recherchée pour tout dommage résultant d'un virus transmis.
> >
> > This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive this 
> e-mail in
> error, please notify the sender immediately and destroy it. As its integrity
> cannot be secured on the Internet, the Worldline liability cannot be triggered
> for the message content. Although the sender endeavours to maintain a
> computer virus-free network, the sender does not warrant that this
> transmission is virus-free and will not be liable for any damages resulting
> from any virus transmitted.
>


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"

[Pharo-dev] ZTimestamp improvement

[Blondeau Vincent]

Hello,

I use Ztimestamp to parse a date but the time zone offset is wrongly set:
(DateAndTime readTimezoneOffsetFrom: '+0530' readStream) printString gives 
'0:05:00:00' instead of  '0:05:30:00'.
See https://pharo.fogbugz.com/f/cases/17693/Time-offset-parsing-is-false for 
the DateAndTime issue.

As the bug is in DateAndTime>>readOptionalSeparatorFrom: and ZTimestamp reuses 
the same code, I propose to apply the same patch to it.
Can I have the commit access to the repo 
(http://smalltalkhub.com/#!/~SvenVanCaekenberghe/Neo) to submit the patch?

Cheers,
Vincent




Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] [GTInpector] Numeric sorting in occurences column of a Bag

[Blondeau Vincent]

Hi,

While inspecting a bag, in the Occurrences tab, I would like a numeric sorting 
of the occurrences  column.
For now it is an alpha-numeric sort which is not practical with numbers >= 10

So, I saw that is it possible to add a sortedBy: block on the column (through 
column:evaluated:sortedBy:).
Consequently, I changed Bag>> gtInspectorOccurrencesIn: :
column: 'Occurences'
evaluated: [ :each | self occurrencesOf: each ]
+ sortedBy: [ :a :b | a <= b ];
beMultiple;


I expected a sort in the occurrence column, but the sort is made in the item 
column.. and not apply on the occurrences  one!?

Is it a known bug ?

Example dataset: #( 1 11 11 11 1 1 1 11 1 1 1 1 1 1 1 1 1 1 1 1 11 1 1 1 1 1 11 
1 1  2 00 2001 00 010 10 1000) asBag

BTW, I don't really understand the difference of sort if we click on the Item 
or the Occurrences label...

Thanks in advance,
Vincent




Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Shortcuts are broken under Windows

[Blondeau Vincent]

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Nicolai 
Hess
Envoyé : mercredi 17 février 2016 20:48
À : Pharo Development List
Objet : Re: [Pharo-dev] Shortcuts are broken under Windows



2016-02-17 18:33 GMT+01:00 Blondeau Vincent 
mailto:vincent.blond...@worldline.com>>:
Hi,

Due to recent changes on shortcuts, on the new image several shortcuts 
(CTRL+V,Z,M,W,Enter and the Alt ones) are not active at least in the debugger 
and in the senders list…

ctrl+v
ctrl+z
ctrl+w
are working for me
ctrl+m does not work, this is known
what "the Alt ones" do you mean?

The same with alt: it was possible to use the shortcuts with alt and ctrl. 
Alt+V is the same as Ctrl +V.
Now both don’t work… in the sender and implementers list, and in the GTdebugger.

Edit: I updated the VM to 20160203. Excepted the CTRL+M, everything seems to 
work again.
Thanks Nicolai

Vincent

I would like to fix this but I don’t know what changed…
How do I change the configuration? Is it in  pragmated methods?
Or it is another bug?

Cheers,
Vincent




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] Shortcuts are broken under Windows

[Blondeau Vincent]

Hi,

Due to recent changes on shortcuts, on the new image several shortcuts 
(CTRL+V,Z,M,W,Enter and the Alt ones) are not active at least in the debugger 
and in the senders list...
I would like to fix this but I don't know what changed...
How do I change the configuration? Is it in  pragmated methods?
Or it is another bug?

Cheers,
Vincent




Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5)

[Blondeau Vincent]

If you remove any line, it stops crashing…
I really don’t know what is going on…

Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Henrik 
Nergaard
Envoyé : vendredi 5 février 2016 14:03
À : Pharo Development List
Objet : Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We 
are in "code freeze" for Pharo 5)

Removing
#(IRPrinterV2 #(visitStoreTemp: visitStoreRemoteTemp: 
visitPopIntoLiteralVariable: visitPushTemp: visitReturnLiteral: 
visitStoreInstVar: visitStoreLiteralVariable: visitPushLiteralVariable: 
visitPushInstVar: visitJump: visitPushLiteral: label: visitPushArray: 
visitPopIntoTemp: visitReturnInstVar: visitPopIntoRemoteTemp: visitTempVector: 
visitJumpIf: visitPushRemoteTemp: visitPopIntoInstVar: visitSend: ))
And it stops crashing.

- BTW, there is not crash.dmp, does it works with spur?
https://pharo.fogbugz.com/f/cases/17506/when-an-Image-crashes-a-crash-dmp-file-is-created-but-nothing-is-written-to-it-Windows

Best regards,
Henrik

From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of 
Blondeau Vincent
Sent: Friday, February 5, 2016 1:54 PM
To: Pharo Development List 
mailto:pharo-dev@lists.pharo.org>>
Subject: Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We 
are in "code freeze" for Pharo 5)

Very strange bug indeed that happens on windows machines that crashes the VM. I 
succeeded to reduce the problem to an evaluation of a collection…
Can someone have the same issue under Windows or Mac?

To reproduce : Copy paste the contents of the attached file in the playground 
and print it or do it
It works on pre-spur vm.

BTW, there is not crash.dmp, does it works with spur?
Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Marcus 
Denker
Envoyé : vendredi 5 février 2016 13:01
À : Pharo Development List
Objet : Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We 
are in "code freeze" for Pharo 5)


On 05 Feb 2016, at 12:40, Marcus Denker 
mailto:marcus.den...@inria.fr>> wrote:

I will try do integrate it now…



No, it still fails.

https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=win/706/

The last test it executed seems to be this:

running suite: Refactoring-Tests-Environment

starting testcase: RBBrowserEnvironmentTest>>testAndEnvironment ...

Very strange...

   Marcus




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5)

[Blondeau Vincent]

Very strange bug indeed that happens on windows machines that crashes the VM. I 
succeeded to reduce the problem to an evaluation of a collection…
Can someone have the same issue under Windows or Mac?

To reproduce : Copy paste the contents of the attached file in the playground 
and print it or do it
It works on pre-spur vm.

BTW, there is not crash.dmp, does it works with spur?
Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Marcus 
Denker
Envoyé : vendredi 5 février 2016 13:01
À : Pharo Development List
Objet : Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We 
are in "code freeze" for Pharo 5)


On 05 Feb 2016, at 12:40, Marcus Denker 
mailto:marcus.den...@inria.fr>> wrote:

I will try do integrate it now…



No, it still fails.

https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=win/706/

The last test it executed seems to be this:

running suite: Refactoring-Tests-Environment

starting testcase: RBBrowserEnvironmentTest>>testAndEnvironment ...

Very strange...

   Marcus




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.
#(#(FLObjectCluster #(printNameOn: ))
#(MBVersionInfo #(printOn: ))
#(GTGenericStackDebugger #(printStackExtraColumnForContext: ))
#(RBCompositeRefactoryChange #(printOn: ))
#(BenchmarkResult #(printOn: ))
#(GTEventCollector #(printOn: ))
#(Pragma #(gtDisplayOn: ))
#(ZnSingleThreadedServer #(printOn: ))
#(StrikeFontSet #(printOn: ))
#(TextIndent #(printOn: ))
#(ExternalStructure #(longPrintOn: ))
#(LimitingLineStreamWrapper #(printOn: ))
#(ZnEntity #(printOn: ))
#(OrderedCollectionTest #(testPrintOn ))
#(MIMEHeaderValue #(printOn: ))
#(LayoutClassScope #(printOn: ))
#(GLMMatchingPresentationsChanged #(printOn: ))
#(FLGlobalSendMock #(printOn: ))
#(ValueLink #(printOn: ))
#(GoferReference #(printOn: ))
#(TextFontReference #(writeScanOn: ))
#(EpContentStringVisitor #(displayBrowserOperation: ))
#(TxInterval #(printOn: ))
#(MetacelloVersion #(printOn: versionKey ))
#(FFIExternalObject #(printOn: ))
#(RBMethod #(printOn: ))
#(TraitBehavior #(printOn: ))
#(GTExampleResult #(gtDisplayOn: ))
#(Duration #(printOn: ))
#(Categorizer #(stringForFileOut ))
#(MouseClickState #(printOn: ))
#(ZnLogEvent #(printOneLineOn: ))
#(TxSelectionChangeOperation #(printOn: ))
#(Slot #(storeOn: ))
#(MetacelloSemanticVersionNumber #(versionString ))
#(OSEvent #(printOn: ))
#(BagTest #(testPrintOn ))
#(MCVariableDefinition #(printOn: ))
#(TestResult #(fileOutOn: ))
#(Point #(storeOn: printOn: ))
#(GTExample #(gtDisplayOn: ))
#(FLIteratingCluster #(printNameOn: ))
#(RBValueToken #(printOn: ))
#(TextAlignment #(writeScanOn: ))
#(RPackageTag #(printOn: ))
#(AdditionalMethodState #(printOn: ))
#(AJInstruction #(printStringLimitedTo: ))
#(MalGraphNode #(printOn: ))
#(MorphTreeNodeModel #(printOn: ))
#(DiffElement #(printOn: ))
#(FLHeader #(gtGetMetaData ))
#(FT2Handle #(printOn: ))
#(ZnSimplifiedByteEncoder #(printOn: ))
#(NBMemoryBlock #(printOn: ))
#(AJx86InstructionDescription #(printOn: ))
#(GLMPane #(printOn: ))
#(DictionaryTest #(testPrintOn ))
#(Exit #(printOn: ))
#(RBRefactoryTyper #(printType:for:on: ))
#(GTEventCollectorsTest #(testPrintOn ))
#(FontSubstitutionDuringLoading #(printOn: ))
#(SocketStream #(print: ))
#(RBLintRuleTest #(displayName printOn: run ))
#(TextEmphasis #(printOn: ))
#(FLSimpleStack #(printOn: ))
#(EpMonticelloVersionSave #(printOn: ))
#(OSKeyboardEvent #(printOn: ))
#(Collection #(printNameOn: ))
#(SetTest #(testPrintOn ))
#(OSWindowDropEvent #(printOn: ))
#(Delay #(printOn: ))
#(Rectangle #(storeOn: printOn: ))
#(STONReference #(printOn: ))
#(Array #(printAsSelfEvaluatingFormOn: printOn: ))
#(GTEventRegistry #(printOn: ))
#(TextColor #(printOn: ))
#(IRStackCount #(printOn: ))
#(LookupKey #(printOn: ))
#(FLHo

Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5)

[Blondeau Vincent]

Indeed… I get a crash of Pharo when I launch the tests…

Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Marcus 
Denker
Envoyé : vendredi 5 février 2016 13:01
À : Pharo Development List
Objet : Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We 
are in "code freeze" for Pharo 5)


On 05 Feb 2016, at 12:40, Marcus Denker 
mailto:marcus.den...@inria.fr>> wrote:

I will try do integrate it now…



No, it still fails.

https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=win/706/

The last test it executed seems to be this:

running suite: Refactoring-Tests-Environment

starting testcase: RBBrowserEnvironmentTest>>testAndEnvironment ...

Very strange...

   Marcus




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5)

[Blondeau Vincent]

Take an image, load Epicea, launch the tests; they should pass. Save and quit  
the image. Relaunch the image, launch the tests, some was red.

Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Martin 
Dias
Envoyé : vendredi 5 février 2016 08:22
À : Pharo Development List
Objet : Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We 
are in "code freeze" for Pharo 5)

I´ve just released a new version and updated the fogbugz case. I hoep it works 
now. How did you repdoruce the error Vincent?

Martin

On Thu, Feb 4, 2016 at 6:24 PM, stepharo 
mailto:steph...@free.fr>> wrote:
Thanks vincent!

Le 4/2/16 16:25, Blondeau Vincent a écrit :

I just tried to integrate and the tests are failing when reopening the image. 
Just added the opening of the session file at the right place and the closing 
of the file at the end of the critical section. Now, it works fine for me 
(under W7 of course ;):

Name: Ombu-VincentBlondeau.191
Author: VincentBlondeau
Time: 4 February 2016, 4:22:48.687273 pm
UUID: ebaf974e-9285-e147-bcaa-0049ff093ffe
Ancestors: Ombu-MartinDias.190

Vincent
-Message d'origine-
De : Pharo-dev 
[mailto:pharo-dev-boun...@lists.pharo.org<mailto:pharo-dev-boun...@lists.pharo.org>]
 De la part de
Marcus Denker
Envoyé : jeudi 4 février 2016 15:19
À : Pharo Development List
Objet : Re: [Pharo-dev] [ANN] We are in "code freeze" for Pharo 5

On 04 Feb 2016, at 15:16, Damien Cassou 
mailto:damien.cas...@inria.fr>> wrote:

Esteban Lorenzano mailto:esteba...@gmail.com>> writes:
We are on “just bugfixes” since some time now… I delayed the
announcement because Epicea still needs to enter and we didn’t manage to
include it yet.
But well… with the exception of Epicea, no new features will be included
un Pharo 5… just bugfixes (and we have a lot of bugfixes incoming… this
release will be hard :( )
what is Epicea's integration status?
We have some strange problem on Windows…  the test on the build server
fails after integrating it.

Martin already fixed one problem, but my try yesterday failed again.

   Marcus


Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.





Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5)

[Blondeau Vincent]

I just tried to integrate and the tests are failing when reopening the image. 
Just added the opening of the session file at the right place and the closing 
of the file at the end of the critical section. Now, it works fine for me 
(under W7 of course ;):

Name: Ombu-VincentBlondeau.191
Author: VincentBlondeau
Time: 4 February 2016, 4:22:48.687273 pm
UUID: ebaf974e-9285-e147-bcaa-0049ff093ffe
Ancestors: Ombu-MartinDias.190

Vincent

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Marcus Denker
> Envoyé : jeudi 4 février 2016 15:19
> À : Pharo Development List
> Objet : Re: [Pharo-dev] [ANN] We are in "code freeze" for Pharo 5
>
>
> > On 04 Feb 2016, at 15:16, Damien Cassou  wrote:
> >
> > Esteban Lorenzano  writes:
> >
> >> We are on “just bugfixes” since some time now… I delayed the
> announcement because Epicea still needs to enter and we didn’t manage to
> include it yet.
> >> But well… with the exception of Epicea, no new features will be included
> un Pharo 5… just bugfixes (and we have a lot of bugfixes incoming… this
> release will be hard :( )
> >
> > what is Epicea's integration status?
> >
> We have some strange problem on Windows…  the test on the build server
> fails after integrating it.
>
> Martin already fixed one problem, but my try yesterday failed again.
>
>   Marcus
>



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] gtdebugger debug actions buttons

[Blondeau Vincent]

I agree with Christophe. Maybe put the buttons on the line under?

Cheers,
Vincent

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Christophe Demarey
> Envoyé : mercredi 27 janvier 2016 09:07
> À : Pharo Development List
> Objet : [Pharo-dev] gtdebugger debug actions buttons
>
> Hi,
>
> I find the new debugger quite but after using it a while, I figure out that 
> the
> placement of debug actions (into, over, etc.) buttons leads to make me
> overuse the mouse and loose time.
> With the spec debugger, buttons are huge and easily accessible . With
> GTDebugger,  there are at the top right of the window and you need to
> move the mouse over the whole window to reach them.
> I know there are shortcuts but I would like to see if we can find a better 
> place
> for these buttons (and maybe bigger buttons).
>
> Regards,
> Christophe


Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Why the Spotter list is truncated?

[Blondeau Vincent]

https://pharo.fogbugz.com/f/cases/17469/Spotter-list-is-truncated

Vincent

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Tudor Girba
> Envoyé : lundi 25 janvier 2016 14:43
> À : Pharo Development List
> Objet : Re: [Pharo-dev] Why the Spotter list is truncated?
>
> Hi,
>
> This is indeed a bug that we noticed. It is not yet in Pharo, but it will be 
> soon.
> It is due to the new infrastructure to allow expanding a category in place
> when it is the only one available.
>
> In the meantime, you can use: "printOn: #senders” and it will work for now.
>
> Please open a bug report in the Pharo bug tracker.
>
> Cheers,
> Doru
>
>
>
> > On Jan 25, 2016, at 2:16 PM, Blondeau Vincent
>  wrote:
> >
> > Hi,
> >
> > On a Moose image (should have the problem on a Pharo image too), I
> wanted to inspect the senders of printOn: (~ 400 results).
> > The end of the list finishes at MBVersionInfo>>printOn:… Where are the
> others??? :
> > 
> >
> > Moreover,  on the first page, I have to go in the  sender sublist to be 
> > able to
> click on the arrow to have the list… and clicking on #senders does nothing….
> >
> > 
> >
> > Thanks in advance for solving the issues,
> >
> > Cheers
> > Vincent
> >
> >
> >
> > Ce message et les pièces jointes sont confidentiels et réservés à l'usage
> exclusif de ses destinataires. Il peut également être protégé par le secret
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir
> immédiatement l'expéditeur et de le détruire. L'intégrité du message ne
> pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra
> être recherchée quant au contenu de ce message. Bien que les meilleurs
> efforts soient faits pour maintenir cette transmission exempte de tout virus,
> l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne
> saurait être recherchée pour tout dommage résultant d'un virus transmis.
> >
> > This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive this 
> e-mail in
> error, please notify the sender immediately and destroy it. As its integrity
> cannot be secured on the Internet, the Worldline liability cannot be triggered
> for the message content. Although the sender endeavours to maintain a
> computer virus-free network, the sender does not warrant that this
> transmission is virus-free and will not be liable for any damages resulting
> from any virus transmitted.
>



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] How to get launcher launching Spur images?

[Blondeau Vincent]

I just solved the bug that appears on Pharo 5, updated the configuration and 
uploaded it to the catalogs.
It should work now.

Vincent

Ps: I was using a Pharo 4.0 image

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de stepharo
Envoyé : jeudi 14 janvier 2016 10:44
À : Pharo Development List
Objet : Re: [Pharo-dev] How to get launcher launching Spur images?

I got it.
I was trying to use Launcher in Pharo 50.
I do not why I was trying it.
Now it works in Pharo 40.
Le 10/1/16 18:49, stepharo a écrit :
Hi

I changed the setting to be the following but I cannot get a spur image started 
on mac.
Does anybody succeed?

Stef


[cid:image001.png@01D14EBA.4FCBB990]




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] How to get launcher launching Spur images?

[Blondeau Vincent]

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> stepharo
> Envoyé : mercredi 13 janvier 2016 16:37
> À : Pharo Development List
> Objet : Re: [Pharo-dev] How to get launcher launching Spur images?
>
> So what is the conclusion?
> Can anybody get the launcher open both prespur and spur images?

I can. You can try the latest version. It should work.

Vincent
>
> Stef
>
>
> Le 13/1/16 13:16, Blondeau Vincent a écrit :
> > I confirm it works under W7 with Spur and not spur images.
> > Thanks !
> >
> > I think https://github.com/pharo-project/pharo-launcher/issues/1 can be
> closed now?
> >
> > Vincent
> >
> >> -Message d'origine-
> >> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part
> >> de Stephan Eggermont Envoyé : mercredi 13 janvier 2016 12:35 À :
> >> pharo-dev@lists.pharo.org Objet : Re: [Pharo-dev] How to get launcher
> >> launching Spur images?
> >>
> >> On 13-01-16 12:25, Blondeau Vincent wrote:
> >>> Under Windows, this cmd is working:
> >>> OSProcess command: $" asString, vmCommand , '"  "' , imagePath, '"'.
> >>> Does it work under Mac (with real double quotes and not 2 single
> quotes)?
> >>> If no, we should do something that is platform dependent..
> >> Yes, it works. Please confirm if version 87 works for you
> >>
> >> Stephan
> >>
> >>
> >
> >
> > Ce message et les pièces jointes sont confidentiels et réservés à l'usage
> exclusif de ses destinataires. Il peut également être protégé par le secret
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir
> immédiatement l'expéditeur et de le détruire. L'intégrité du message ne
> pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra
> être recherchée quant au contenu de ce message. Bien que les meilleurs
> efforts soient faits pour maintenir cette transmission exempte de tout virus,
> l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne
> saurait être recherchée pour tout dommage résultant d'un virus transmis.
> >
> > This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive this 
> e-mail
> in error, please notify the sender immediately and destroy it. As its 
> integrity
> cannot be secured on the Internet, the Worldline liability cannot be triggered
> for the message content. Although the sender endeavours to maintain a
> computer virus-free network, the sender does not warrant that this
> transmission is virus-free and will not be liable for any damages resulting
> from any virus transmitted.
>



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] How to get launcher launching Spur images?

[Blondeau Vincent]

I confirm it works under W7 with Spur and not spur images.
Thanks !

I think https://github.com/pharo-project/pharo-launcher/issues/1 can be closed 
now?

Vincent

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Stephan Eggermont
> Envoyé : mercredi 13 janvier 2016 12:35
> À : pharo-dev@lists.pharo.org
> Objet : Re: [Pharo-dev] How to get launcher launching Spur images?
>
> On 13-01-16 12:25, Blondeau Vincent wrote:
> > Under Windows, this cmd is working:
> > OSProcess command: $" asString, vmCommand , '"  "' , imagePath, '"'.
> > Does it work under Mac (with real double quotes and not 2 single quotes)?
> > If no, we should do something that is platform dependent..
>
> Yes, it works. Please confirm if version 87 works for you
>
> Stephan
>
>



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] How to get launcher launching Spur images?

[Blondeau Vincent]

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Stephan Eggermont
> Envoyé : mercredi 13 janvier 2016 11:45
> À : pharo-dev@lists.pharo.org
> Objet : Re: [Pharo-dev] How to get launcher launching Spur images?
>
> On 12-01-16 21:10, Stephan Eggermont wrote:
> > On 12-01-16 15:23, Ben Coman wrote:
> >> On Tue, Jan 12, 2016 at 10:03 PM, stepharo  wrote:
> >>> I loaded the stable version in Pharo 50 and I saw that it does not
> >>> have the Spur special Folder.
> >>> So I loaded the latest version of the packages from the repo and I
> >>> could not run the launcher anymore.
> >>>
> >>> So could you tell me how you did it?
> >>
> >> Err, umm...  looking just now I see only one settable VM path.  So it
> >> seems I did not load the latest, only the version from the Catalog.
> >> So I guess I can only run Spur images.
> >
> > That is likely. If you load a newer version you get the second path. I
> > didn't try, but that should allow you to run both also from a spur
> > launcher. In version 84 there is a change in the way the launcher is
> > started, that might be incompatible with OS-X?
>
> Ok, I checked. That launch command was incompatible with OS-X.
> I reverted the change. Please try with the latest version.
> Vincent, on what platform are you running?

On Windows7 :) But now the command is incompatible with W7 ;)

It is strange because with an older version of the Pharo launcher, e.g. 
PharoLauncher-Core-SeanDeNigris.76 it was this command:
OSProcess command: vmCommand , '  "' , imagePath, '"'.
And nobody had problems on Mac...
Does something changed in OSprocess?

Under Windows, this cmd is working:
OSProcess command: $" asString, vmCommand , '"  "' , imagePath, '"'.
Does it work under Mac (with real double quotes and not 2 single quotes)?
If no, we should do something that is platform dependent..

Vincent
>
> Stephan
>
>



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Pharo50 spur works on CentOS?

[Blondeau Vincent]

Agree.
I open a bug: 
https://pharo.fogbugz.com/f/cases/17378/Improve-command-line-handler-documentation-and-help
 that improve the doc.
I propose:
Usage: 
[--no-preferences|--preference-file=][--help|--list|--copyright|--version|--no-quit|
 ]
--help   print this help message
--list   list a description of all active command line handlers
--copyright  print the copyrights
--versionprint the version for the image and the vm
--no-quitkeep the image running without activating any other 
command line handler
 a valid subcommand in --list
 --help show subcommand help

Vincent

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Sven Van Caekenberghe
> Envoyé : mardi 12 janvier 2016 11:48
> À : Pharo Development List
> Objet : Re: [Pharo-dev] Pharo50 spur works on CentOS?
>
> No, I don't think so, it has a function.
>
> Some people like to configure Pharo images so that they have a running
> server inside them. In that case, starting your app is a simple as starting 
> the
> image, but you would probably need the --no-quit to prevent it from exiting
> immediately.
>
> (I personally don't like and never use that approach, but I know some people
> like it).
>
> The confusing aspect is that the same option is used in two places and the
> first one annihilates the second. But that is documented:
>
> prometheus:pharo5 sven$ ./pharo Pharo.image --help
> Usage: [--no-preferences|--preference-file=][] [--
> help] [--copyright] [--version] [--list] [ --no-quit ]
>   --help   print this help message
>   --copyright  print the copyrights
>   --versionprint the version for the image and the vm
>   --list   list a description of all active command line handlers
>   --no-quitkeep the image running without activating any other
> command line handler
>a valid subcommand in --list
>
> Documentation:
> A BasicCommandLineHandler handles default command line arguments and
> options.
>
> It clearly says "without activating any other command line handler". So using
> --no-quit BEFORE the subcommand annihilates the subcommand (AFAIU).
>
> > On 12 Jan 2016, at 11:28, Blondeau Vincent
>  wrote:
> >
> > So --no-quit should be removed from the default line handler?
> >
> > Vincent
> >
> >> -Message d'origine-
> >> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part
> >> de Esteban Lorenzano Envoyé : mardi 12 janvier 2016 11:18 À : Pharo
> >> Development List Objet : Re: [Pharo-dev] Pharo50 spur works on
> >> CentOS?
> >>
> >> But you cannot use it as a general command.
> >> If you use a subcommand (most likely) then you do not have it unless
> >> the subcommand defines it.
> >>
> >> Esteban
> >>
> >>> On 12 Jan 2016, at 11:12, Blondeau Vincent
> >>  wrote:
> >>>
> >>>
> >>>
> >>>> -Message d'origine-
> >>>> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la
> >>>> part de Sven Van Caekenberghe Envoyé : mardi 12 janvier 2016 10:57 À
> :
> >>>> Pharo Development List Objet : Re: [Pharo-dev] Pharo50 spur works
> >>>> on CentOS?
> >>>>
> >>>>
> >>>>>> On 12 Jan 2016, at 10:50, Esteban Lorenzano
> 
> >>>>> wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>> On 12 Jan 2016, at 10:34, Sven Van Caekenberghe 
> >> wrote:
> >>>>>>
> >>>>>>
> >>>>>>> On 12 Jan 2016, at 10:28, Blondeau Vincent
> >>>>  wrote:
> >>>>>>>
> >>>>>>> Indeed, it works. Thanks!
> >>>>>>>
> >>>>>>> But the command line usage is not clear :
> >>>>>>> ./pharo Pharo.image
> >>>>>>> Usage: [--no-preferences|--preference-
> file=][]
> >>>>>>> [--help] [--copyright] [--version] [--list] [ --no-quit ]
> >>>>>>>
> >>>>>>> Maybe, it can be :
> >>>>>>> Usage: [--no-preferences|--preference-
> file=][]
> >>>>>>> [--help] [--copyright] [--version] [--list] [ --no-quit ]
> >>>>>>> []
> >>>>>>>
> >>>>>>> Moreover, an option can usually be placed anywhere on the
> >>>>>

Re: [Pharo-dev] Pharo50 spur works on CentOS?

[Blondeau Vincent]

So --no-quit should be removed from the default line handler?

Vincent

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Esteban Lorenzano
> Envoyé : mardi 12 janvier 2016 11:18
> À : Pharo Development List
> Objet : Re: [Pharo-dev] Pharo50 spur works on CentOS?
>
> But you cannot use it as a general command.
> If you use a subcommand (most likely) then you do not have it unless the
> subcommand defines it.
>
> Esteban
>
> > On 12 Jan 2016, at 11:12, Blondeau Vincent
>  wrote:
> >
> >
> >
> >> -Message d'origine-
> >> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part
> >> de Sven Van Caekenberghe Envoyé : mardi 12 janvier 2016 10:57 À :
> >> Pharo Development List Objet : Re: [Pharo-dev] Pharo50 spur works on
> >> CentOS?
> >>
> >>
> >>>> On 12 Jan 2016, at 10:50, Esteban Lorenzano 
> >>> wrote:
> >>>
> >>>
> >>>
> >>>> On 12 Jan 2016, at 10:34, Sven Van Caekenberghe 
> wrote:
> >>>>
> >>>>
> >>>>> On 12 Jan 2016, at 10:28, Blondeau Vincent
> >>  wrote:
> >>>>>
> >>>>> Indeed, it works. Thanks!
> >>>>>
> >>>>> But the command line usage is not clear :
> >>>>> ./pharo Pharo.image
> >>>>> Usage: [--no-preferences|--preference-file=][]
> >>>>> [--help] [--copyright] [--version] [--list] [ --no-quit ]
> >>>>>
> >>>>> Maybe, it can be :
> >>>>> Usage: [--no-preferences|--preference-file=][]
> >>>>> [--help] [--copyright] [--version] [--list] [ --no-quit ]
> >>>>> []
> >>>>>
> >>>>> Moreover, an option can usually be placed anywhere on the command
> >> line, shouldn't it? Or at least it should raise an error?
> >>>>
> >>>> Yes it is a bit confusion (but you could try to read/understand the
> >>>> Pharo code, it is not very difficult ;-)
> >>>>
> >>>> But the idea is that the sub-command controls its own options (like
> >>>> passing linker options via the compiler to the linker - git also
> >>>> has global and per sub command options, no ?)
> >>>>
> >>>> --no-quit probably also works for the default command ... (I
> >>>> haven't
> >> looked), so at that point, the option is consumed already.
> >>>
> >>> No, it doesn't :)
> >>
> >> prometheus:pharo5 sven$ ./pharo Pharo.image printVersion [version]
> >> 5.0
> >> #50510
> >> prometheus:pharo5 sven$ ./pharo Pharo.image --no-quit ^C
> >>
> >> The last command 'hangs' (i.e. the image keeps running, just as
> advertised).
> >> So the default (Pharo, subclass of BasicCommandHandler) interpreted
> >> the -- no-quit and acted upon it. No ?
> >
> > Yes! See: BasicCommandLineHandler>>handleArgument:
> >>
> >>>>
> >>>>> Vincent



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Pharo50 spur works on CentOS?

[Blondeau Vincent]

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Sven Van Caekenberghe
> Envoyé : mardi 12 janvier 2016 10:57
> À : Pharo Development List
> Objet : Re: [Pharo-dev] Pharo50 spur works on CentOS?
>
>
> > On 12 Jan 2016, at 10:50, Esteban Lorenzano 
> wrote:
> >
> >
> >
> >> On 12 Jan 2016, at 10:34, Sven Van Caekenberghe  wrote:
> >>
> >>
> >>> On 12 Jan 2016, at 10:28, Blondeau Vincent
>  wrote:
> >>>
> >>> Indeed, it works. Thanks!
> >>>
> >>> But the command line usage is not clear :
> >>> ./pharo Pharo.image
> >>> Usage: [--no-preferences|--preference-file=][]
> >>> [--help] [--copyright] [--version] [--list] [ --no-quit ]
> >>>
> >>> Maybe, it can be :
> >>> Usage: [--no-preferences|--preference-file=][]
> >>> [--help] [--copyright] [--version] [--list] [ --no-quit ]
> >>> []
> >>>
> >>> Moreover, an option can usually be placed anywhere on the command
> line, shouldn't it? Or at least it should raise an error?
> >>
> >> Yes it is a bit confusion (but you could try to read/understand the
> >> Pharo code, it is not very difficult ;-)
> >>
> >> But the idea is that the sub-command controls its own options (like
> >> passing linker options via the compiler to the linker - git also has
> >> global and per sub command options, no ?)
> >>
> >> --no-quit probably also works for the default command ... (I haven't
> looked), so at that point, the option is consumed already.
> >
> > No, it doesn't :)
>
> prometheus:pharo5 sven$ ./pharo Pharo.image printVersion [version] 5.0
> #50510
> prometheus:pharo5 sven$ ./pharo Pharo.image --no-quit ^C
>
> The last command 'hangs' (i.e. the image keeps running, just as advertised).
> So the default (Pharo, subclass of BasicCommandHandler) interpreted the --
> no-quit and acted upon it. No ?

Yes! See: BasicCommandLineHandler>>handleArgument:
>
> >>
> >>> Vincent
> >>>
> >>>> -Message d'origine-
> >>>> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la
> >>>> part de Esteban Lorenzano Envoyé : lundi 11 janvier 2016 19:21 À :
> >>>> Pharo Development List Objet : Re: [Pharo-dev] Pharo50 spur works
> >>>> on CentOS?
> >>>>
> >>>>
> >>>>> On 11 Jan 2016, at 19:06, Sven Van Caekenberghe 
> wrote:
> >>>>>
> >>>>> Is it not ./pharo Pharo.image eval --no-quit 'ZnServer startDefaultOn:
> 8080'
> >>>>>
> >>>>> ?
> >>>>>
> >>>>> I.e. the --no-quit AFTER the eval.
> >>>>
> >>>> yes, is like that :)
> >>>>
> >>>>>
> >>>>> http://zn.stfx.eu/zn/build-and-deploy-1st-webapp/#runningarealclou
> >>>>> dser
> >>>>> ver
> >>>>>
> >>>>>> On 11 Jan 2016, at 18:46, Blondeau Vincent
> >>>>  wrote:
> >>>>>>
> >>>>>> The .sources are in the vm folder.
> >>>>>>
> >>>>>> And, it is working, but without the –no-quit option and this kind of
> code :
> >>>>>> [ZnServer startOn: 8080] fork. (Delay forSeconds: 20) wait
> >>>>>>
> >>>>>> The –no-quit option seems to have a bad influence…
> >>>>>>
> >>>>>> Can you tell me which packages you installed?
> >>>>>>
> >>>>>> Thanks
> >>>>>>
> >>>>>> Vincent
> >>>>>>
> >>>>>>
> >>>>>> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la
> >>>>>> part de Mariano Martinez Peck Envoyé : lundi 11 janvier 2016 18:27 À
> :
> >>>>>> Pharo Development List Objet : Re: [Pharo-dev] Pharo50 spur works
> >>>>>> on CentOS?
> >>>>>>
> >>>>>> It does work for me in CentOS.
> >>>>>> Are you sure .sources file is in the correct place?
> >>>>>>
> >>>>>> On Mon, Jan 11, 2016 at 1:55 PM, Blondeau Vincent
> >>>>  wrote:
> >>>>>> Thanks for your answer.
> >>>>>>
> &g

Re: [Pharo-dev] Pharo50 spur works on CentOS?

[Blondeau Vincent]

Indeed, it works. Thanks!

But the command line usage is not clear :
./pharo Pharo.image
Usage: [--no-preferences|--preference-file=][] [--help] 
[--copyright] [--version] [--list] [ --no-quit ]

Maybe, it can be :
Usage: [--no-preferences|--preference-file=][] [--help] 
[--copyright] [--version] [--list] [ --no-quit ] []

Moreover, an option can usually be placed anywhere on the command line, 
shouldn't it? Or at least it should raise an error?

Vincent

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Esteban Lorenzano
> Envoyé : lundi 11 janvier 2016 19:21
> À : Pharo Development List
> Objet : Re: [Pharo-dev] Pharo50 spur works on CentOS?
>
>
> > On 11 Jan 2016, at 19:06, Sven Van Caekenberghe  wrote:
> >
> > Is it not ./pharo Pharo.image eval --no-quit 'ZnServer startDefaultOn: 8080'
> >
> > ?
> >
> > I.e. the --no-quit AFTER the eval.
>
> yes, is like that :)
>
> >
> > http://zn.stfx.eu/zn/build-and-deploy-1st-webapp/#runningarealcloudser
> > ver
> >
> >> On 11 Jan 2016, at 18:46, Blondeau Vincent
>  wrote:
> >>
> >> The .sources are in the vm folder.
> >>
> >> And, it is working, but without the –no-quit option and this kind of code :
> >> [ZnServer startOn: 8080] fork. (Delay forSeconds: 20) wait
> >>
> >> The –no-quit option seems to have a bad influence…
> >>
> >> Can you tell me which packages you installed?
> >>
> >> Thanks
> >>
> >> Vincent
> >>
> >>
> >> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part
> >> de Mariano Martinez Peck Envoyé : lundi 11 janvier 2016 18:27 À :
> >> Pharo Development List Objet : Re: [Pharo-dev] Pharo50 spur works on
> >> CentOS?
> >>
> >> It does work for me in CentOS.
> >> Are you sure .sources file is in the correct place?
> >>
> >> On Mon, Jan 11, 2016 at 1:55 PM, Blondeau Vincent
>  wrote:
> >> Thanks for your answer.
> >>
> >> However, it seems that the server does not start with:
> >> ./pharo -vm-display-null -vm-sound-null Pharo.image --no-quit eval
> "ZnServer  startOn:  8080."
> >> Nothing in the terminal and no open port in "netstat -an"
> >>
> >> While, this command is writing something in the terminal:
> >> ./pharo -vm-display-null -vm-sound-null Pharo.image eval "ZnServer
> startOn:  8080."
> >> a ZnManagingMultiThreadedServer(running 8080)
> >>
> >> Vincent
> >>
> >>> -Message d'origine-
> >>> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part
> >>> de Sven Van Caekenberghe Envoyé : lundi 11 janvier 2016 17:03 À :
> >>> Pharo Development List Objet : Re: [Pharo-dev] Pharo50 spur works on
> >>> CentOS?
> >>>
> >>>
> >>>> On 11 Jan 2016, at 16:51, Blondeau Vincent
> >>>  wrote:
> >>>>
> >>>> Hello,
> >>>>
> >>>> I just wanted to run a latest Pharo image on a CentOS server to run
> >>>> a Zinc
> >>> server.
> >>>> So I did:
> >>>> curl get.pharo.org/50+vm | bash
> >>>>
> >>>> ./pharo Pharo.image eval “1+1”  evals to 2
> >>>>
> >>>> But,
> >>>> ./pharo Pharo.image --no-quit eval "ZnServer  startOn:  8080."
> >>>> returns:
> >>>> ioLoadModule(/root/Pharo/pharo-vm/libFT2Plugin.so):
> >>>>  libfreetype.so.6: cannot open shared object file: No such file or
> >>>> directory
> >>>>
> >>>> So the server is not launched…
> >>>>
> >>>> What are the libs that should be installed on the machine? Should I
> >>>> take
> >>> another VM?
> >>>>
> >>>> BTW, why a headless image needs a freetype lib?
> >>>
> >>> Yeah, that should not be the case:
> >>>
> >>> http://forum.world.st/Confused-about-libFT2Plugin-tt4842354.html
> >>>
> >>>> Thanks in advance,
> >>>>
> >>>> Cheers,
> >>>> Vincent Blondeau
> >>>>
> >>>>
> >>
> >>
> >>
> >> Ce message et les pièces jointes sont confidentiels et réservés à l'usage
> exclusif de ses destinataires. Il peut également être protégé par le secret
> professionnel. Si vou

Re: [Pharo-dev] Pharo50 spur works on CentOS?

[Blondeau Vincent]

The .sources are in the vm folder.

And, it is working, but without the –no-quit option and this kind of code :
[ZnServer startOn: 8080] fork. (Delay forSeconds: 20) wait

The –no-quit option seems to have a bad influence…

Can you tell me which packages you installed?

Thanks

Vincent


De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Mariano 
Martinez Peck
Envoyé : lundi 11 janvier 2016 18:27
À : Pharo Development List
Objet : Re: [Pharo-dev] Pharo50 spur works on CentOS?

It does work for me in CentOS.
Are you sure .sources file is in the correct place?

On Mon, Jan 11, 2016 at 1:55 PM, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:
Thanks for your answer.

However, it seems that the server does not start with:
./pharo -vm-display-null -vm-sound-null Pharo.image --no-quit eval "ZnServer  
startOn:  8080."
Nothing in the terminal and no open port in "netstat -an"

While, this command is writing something in the terminal:
./pharo -vm-display-null -vm-sound-null Pharo.image eval "ZnServer  startOn:  
8080."
a ZnManagingMultiThreadedServer(running 8080)

Vincent

> -Message d'origine-
> De : Pharo-dev 
> [mailto:pharo-dev-boun...@lists.pharo.org<mailto:pharo-dev-boun...@lists.pharo.org>]
>  De la part de
> Sven Van Caekenberghe
> Envoyé : lundi 11 janvier 2016 17:03
> À : Pharo Development List
> Objet : Re: [Pharo-dev] Pharo50 spur works on CentOS?
>
>
> > On 11 Jan 2016, at 16:51, Blondeau Vincent
> mailto:vincent.blond...@worldline.com>> wrote:
> >
> > Hello,
> >
> > I just wanted to run a latest Pharo image on a CentOS server to run a Zinc
> server.
> > So I did:
> > curl get.pharo.org/50+vm<http://get.pharo.org/50+vm> | bash
> >
> > ./pharo Pharo.image eval “1+1”  evals to 2
> >
> > But,
> > ./pharo Pharo.image --no-quit eval "ZnServer  startOn:  8080."
> > returns:
> > ioLoadModule(/root/Pharo/pharo-vm/libFT2Plugin.so):
> >   libfreetype.so.6: cannot open shared object file: No such file or 
> > directory
> >
> > So the server is not launched…
> >
> > What are the libs that should be installed on the machine? Should I take
> another VM?
> >
> > BTW, why a headless image needs a freetype lib?
>
> Yeah, that should not be the case:
>
> http://forum.world.st/Confused-about-libFT2Plugin-tt4842354.html
>
> > Thanks in advance,
> >
> > Cheers,
> > Vincent Blondeau
> >
> >



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.



--
Mariano
http://marianopeck.wordpress.com



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Pharo50 spur works on CentOS?

[Blondeau Vincent]

Thanks for your answer.

However, it seems that the server does not start with:
./pharo -vm-display-null -vm-sound-null Pharo.image --no-quit eval "ZnServer  
startOn:  8080."
Nothing in the terminal and no open port in "netstat -an"

While, this command is writing something in the terminal:
./pharo -vm-display-null -vm-sound-null Pharo.image eval "ZnServer  startOn:  
8080."
a ZnManagingMultiThreadedServer(running 8080)

Vincent

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Sven Van Caekenberghe
> Envoyé : lundi 11 janvier 2016 17:03
> À : Pharo Development List
> Objet : Re: [Pharo-dev] Pharo50 spur works on CentOS?
>
>
> > On 11 Jan 2016, at 16:51, Blondeau Vincent
>  wrote:
> >
> > Hello,
> >
> > I just wanted to run a latest Pharo image on a CentOS server to run a Zinc
> server.
> > So I did:
> > curl get.pharo.org/50+vm | bash
> >
> > ./pharo Pharo.image eval “1+1”  evals to 2
> >
> > But,
> > ./pharo Pharo.image --no-quit eval "ZnServer  startOn:  8080."
> > returns:
> > ioLoadModule(/root/Pharo/pharo-vm/libFT2Plugin.so):
> >   libfreetype.so.6: cannot open shared object file: No such file or 
> > directory
> >
> > So the server is not launched…
> >
> > What are the libs that should be installed on the machine? Should I take
> another VM?
> >
> > BTW, why a headless image needs a freetype lib?
>
> Yeah, that should not be the case:
>
> http://forum.world.st/Confused-about-libFT2Plugin-tt4842354.html
>
> > Thanks in advance,
> >
> > Cheers,
> > Vincent Blondeau
> >
> >



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] Pharo50 spur works on CentOS?

[Blondeau Vincent]

Hello,

I just wanted to run a latest Pharo image on a CentOS server to run a Zinc 
server.
So I did:
curl get.pharo.org/50+vm | bash

./pharo Pharo.image eval "1+1"  evals to 2

But,
./pharo Pharo.image --no-quit eval "ZnServer  startOn:  8080."
returns:
ioLoadModule(/root/Pharo/pharo-vm/libFT2Plugin.so):
  libfreetype.so.6: cannot open shared object file: No such file or directory

So the server is not launched...

What are the libs that should be installed on the machine? Should I take 
another VM?

BTW, why a headless image needs a freetype lib?

Thanks in advance,

Cheers,
Vincent Blondeau




Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] GTDebugger not draggable with latest VM

[Blondeau Vincent]

Hi,

I have a problem on the latest Moose6.0 image.
I was not able to open a Roassal view, I had a NativeBoost Generic failure...
So I updated the VM to last stable, and, now, the GTdebugger and the Moose 
panel are not draggable anymore...
Can somebody is able to reproduce the problem?

Thanks

Cheers,
Vincent



Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] Issue with large file path on windows

[Blondeau Vincent]

Hello,

I would like to read from Pharo a file with a long name (so more than 255 
chars) under Windows.
A thread from last month (13 oct): "Re: [Pharo-dev] [Vm-dev] Re: issue with 
large file path on windows", talks about a patch.
Does it has been integrated?
If it has, which VM should I take to have the patch?
My current one is http://files.pharo.org/vm/pharo/win/494.zip

Thanks,

Vincent Blondeau




Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Smalltalkhub is very instable this afternoon

[Blondeau Vincent]

Thx Esteban !

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Esteban 
Lorenzano
Envoyé : vendredi 20 novembre 2015 17:50
À : Pharo Development List
Objet : Re: [Pharo-dev] Smalltalkhub is very instable this afternoon

done

On 20 Nov 2015, at 11:41, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:

Hello,

Can Smalltalkhub be restarted (or other) because it is impossible to work by 
getting continuously errors 500, 503, 403, 401…. while loading or committing?

TIA

Cheers,

Vincent BLONDEAU



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] Smalltalkhub is very instable this afternoon

[Blondeau Vincent]

Hello,

Can Smalltalkhub be restarted (or other) because it is impossible to work by 
getting continuously errors 500, 503, 403, 401 while loading or committing?

TIA

Cheers,

Vincent BLONDEAU



Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Smalltalkhub instable

[Blondeau Vincent]

Thanks Marcus

Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Marcus 
Denker
Envoyé : mercredi 7 octobre 2015 16:56
À : Pharo Development List
Objet : Re: [Pharo-dev] Smalltalkhub instable


On 07 Oct 2015, at 15:47, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:

Hi,

It is very hard to work because Smalltalkhub is very instable today.
I wanted to launch https://ci.inria.fr/moose/job/moose-6.0 but I get either an 
400 or 500 error… (It seems to work now but for how long?)

Can somebody could look at this issue ?

I restarted apache…which seems to be the source of the problem when loading 
static files makes problems.

  Marcus




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] Smalltalkhub instable

[Blondeau Vincent]

Hi,

It is very hard to work because Smalltalkhub is very instable today.
I wanted to launch https://ci.inria.fr/moose/job/moose-6.0 but I get either an 
400 or 500 error... (It seems to work now but for how long?)

Can somebody could look at this issue ?

Thanks in advance,

Vincent BLONDEAU



Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] [Pharo-users] [ann] brick on top of bloc - preview

[Blondeau Vincent]

Loading traits only is working, there are traits in Moose and it is well 
working...
E.g.:
Trait named: #TOODependencyQueries
uses: TDependencyQueries
category: 'Famix-Core'

Vincent

-Message d'origine-
De : Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] De la part de 
Marcus Denker
Envoyé : mercredi 26 août 2015 10:52
À : Any question about pharo is welcome
Cc : Pharo Development List
Objet : Re: [Pharo-users] [ann] brick on top of bloc - preview


> On 26 Aug 2015, at 10:42, Tudor Girba  wrote:
>
> Aha. Thanks for the help, Vincent.
>
> Now, the next problem: Does anyone know why the "Unrecognized class 
> definition" problem occurs? :)
>

It seems that

1) MC model loading of the serialised package fails
2) it falls back on using MCStReader
3) which fails to load the .st file for the definition of 
TBlLayoutPropertiesOwner

Maybe loading trait definitions does not work in general with MCStReader?

Marcus


Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Critical change to compiler, needs testing

[Blondeau Vincent]

You right, I forget to load the first slice..

But I did not find errors by running some tests on the Moose Image.

Cheers,
Vincent


De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de 
Guillermo Polito
Envoyé : mardi 18 août 2015 11:49
À : Pharo Development List; Clément Bera
Objet : Re: [Pharo-dev] Critical change to compiler, needs testing

That moose image is based on the latest Pharo??? :) Because to me it looks like 
you don't have the OpalEncoder classes from slice 16199.

The order of loading is the following if on versions of pharo that are not 
latest 5.0:

- load slice 16199
- load slice 16250
- execute postload: CompiledMethod initialize

I tried that in moose 6.0, based on Pharo5.0 update: #50241 and It works fine.

El mar., 18 de ago. de 2015 a la(s) 11:32 a. m., Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> 
escribió:
Hi Guille,

I loaded your slice in the last Moose image, and it not possible to browse any 
source code through nautilus…

Maybe you should take a look?

Cheers,
Vincent

De : Pharo-dev 
[mailto:pharo-dev-boun...@lists.pharo.org<mailto:pharo-dev-boun...@lists.pharo.org>]
 De la part de Guillermo Polito
Envoyé : mardi 18 août 2015 11:13
À : Discusses Development of Pharo; Clément Bera
Objet : [Pharo-dev] Critical change to compiler, needs testing

Hi guys,

In the quest to remove the old compiler from the map, we need to replace the 
references to ParseNode. Thing is that right now, the bytecode encoders opal 
compiler uses are subclasses of this ParseNode guy.

To solve this, we are integrating this in several steps:

- Integrate a copy of the encoders that are not subclass of ParseNode
 Already integrated, with no real side effects on the system.
 https://pharo.fogbugz.com/f/cases/16199/Introduce-OpalEncoders

- Make the system use the new encoders
This change is critical as if the new encoders do not do the job, you may 
be unable to execute code again ^^.
We need help in testing this.
I ran the full tests of the image found some bugs but they do not look 
related. But, if you know some case, or you use the compiler in a special way, 
It would be good if you load the slice and test please :)
https://pharo.fogbugz.com/f/cases/16250/Activate-new-Encoders

- A final step will be to rename the OpalEncoders* to Encoder* again (removing 
the Opal prefix) to be compatible with Squeak. But this one is rather easy and 
may have no risk.

Guille



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Critical change to compiler, needs testing

[Blondeau Vincent]

Hi Guille,

I loaded your slice in the last Moose image, and it not possible to browse any 
source code through nautilus…

Maybe you should take a look?

Cheers,
Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de 
Guillermo Polito
Envoyé : mardi 18 août 2015 11:13
À : Discusses Development of Pharo; Clément Bera
Objet : [Pharo-dev] Critical change to compiler, needs testing

Hi guys,

In the quest to remove the old compiler from the map, we need to replace the 
references to ParseNode. Thing is that right now, the bytecode encoders opal 
compiler uses are subclasses of this ParseNode guy.

To solve this, we are integrating this in several steps:

- Integrate a copy of the encoders that are not subclass of ParseNode
 Already integrated, with no real side effects on the system.
 https://pharo.fogbugz.com/f/cases/16199/Introduce-OpalEncoders

- Make the system use the new encoders
This change is critical as if the new encoders do not do the job, you may 
be unable to execute code again ^^.
We need help in testing this.
I ran the full tests of the image found some bugs but they do not look 
related. But, if you know some case, or you use the compiler in a special way, 
It would be good if you load the slice and test please :)
https://pharo.fogbugz.com/f/cases/16250/Activate-new-Encoders

- A final step will be to rename the OpalEncoders* to Encoder* again (removing 
the Opal prefix) to be compatible with Squeak. But this one is rather easy and 
may have no risk.

Guille



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.


PharoDebug.log
Description: PharoDebug.log

Re: [Pharo-dev] World Menu associated mouse click

[Blondeau Vincent]

Hi,

There is a setting to have this consistence (deactivated by default):
Appearance>Desktop>Invert right click on world menu in Linux and Windows

By the way, the buttons are not inverted under Mac (conventional).

I agree that the context click should open the world menu by default..

Cheers,
Vincent

-Message d'origine-
De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Ben 
Coman
Envoyé : lundi 17 août 2015 15:52
À : Pharo Development List
Objet : [Pharo-dev] World Menu associated mouse click

A while back on reddit someone complained about the World Menu being associated 
with left-mouse-click.  I have come to agree.  The World Menu provides the 
actions available in the context of the World, i.e.
the World's context-menu - but its not invoked by the usual convention for 
context menus, which is the right-mouse-click.

By way of example, in a fresh image and open one Playground.

* First right-click the Playground. Up comes the Playground's context-menu as 
expected per industry wide conventions.

* Then right-click the background. Doh! Its not consistent, thats not the 
World's context-menu. "WTH is that?" says a newbie in surprise.
(Btw, who uses that list of open windows ? I *never* do and might suggest that 
function be moved to a meta-mouse-click.)

So can we discuss changing the World Menu to be invoked by the context-click 
(i.e. right-click) ?

cheers -ben



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Windows users, please test!

[Blondeau Vincent]

Seems to work!

I will use it to develop and keep you informed tomorrow.

Vincent


De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Esteban 
Lorenzano
Envoyé : lundi 3 août 2015 15:22
À : Pharo Development List
Objet : [Pharo-dev] Windows users, please test!

I made a new SLICE trying to fix the FT2 crash problem windows (and I think 
also linux?) are experiencing… can you please merge the SLICE for:

https://pharo.fogbugz.com/f/cases/15633

and test a bit… and inform any new problems?

I’m not a windows user but I tested the solution some time in a virtual image… 
but we all know that’s limited :)

thanks!
Esteban





Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Windows users, please test!

[Blondeau Vincent]

Thanks Esteban!
I will try :)

Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Esteban 
Lorenzano
Envoyé : lundi 3 août 2015 15:22
À : Pharo Development List
Objet : [Pharo-dev] Windows users, please test!

I made a new SLICE trying to fix the FT2 crash problem windows (and I think 
also linux?) are experiencing… can you please merge the SLICE for:

https://pharo.fogbugz.com/f/cases/15633

and test a bit… and inform any new problems?

I’m not a windows user but I tested the solution some time in a virtual image… 
but we all know that’s limited :)

thanks!
Esteban





Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Google Code Shutdown

[Blondeau Vincent]

That is a solution but not for long term. I don’t want to install linux to use 
pharo..
For now the solution is to use git as standalone app and filetree to export the 
code.
I use it and it works well while you don’t have to long paths.

Vincent


De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de 
Dimitris Chloupis
Envoyé : lundi 3 août 2015 13:42
À : Pharo Development List
Objet : ** SPAM scored: Med **Re: [Pharo-dev] Google Code Shutdown

A workaround if you absolutely want to use gitfiletree is to install linux 
using a VM like virtual box , Ubuntu for example works very well with pharo

https://www.virtualbox.org/
This way you avoid booting to another OS , you can also share your git folder 
to both windows and linux vm. This way you can use gitfiletree without ditching 
windows. Of course dual boot can work too if you dont need to use Pharo with 
windoom.
VM option works also if you want to install MacOS on your windows pc.

On Mon, Aug 3, 2015 at 1:13 PM Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:
Hi,

Sorry but I am using Windows… not because I want to but because I have to... So 
the therapy will not work ;)
Actually, the bugtracker of Moose can be on github, but the git user experience 
under Windows has to be improved if we want to use efficiently the other 
functionalities of github (pull requests, commit, branches,…).

Cheers,
Vincent

De : Pharo-dev 
[mailto:pharo-dev-boun...@lists.pharo.org<mailto:pharo-dev-boun...@lists.pharo.org>]
 De la part de Peter Uhnák
Envoyé : lundi 3 août 2015 11:56
À : Pharo Development List
Objet : Re: [Pharo-dev] Google Code Shutdown

As long as nobody on your team is using Windows, git(hub) is quite good. :)
(And if you have Windows user, then find him a therapy first, or push for 
libcgit :))

On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel 
mailto:alexandre.ber...@me.com>> wrote:
Github is indeed appealing.

Cheers,
Alexandre



> On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris 
> mailto:s...@clipperadams.com>> wrote:
>
> Tudor Girba-2 wrote
>> Would you like to help us move the moose-technology project?
>
> Sure. What do you have in mind? It seems exporting to GitHub is the easiest
> option. There are a few limitations, but I've had good experiences...
>
>
>
> -
> Cheers,
> Sean
> --
> View this message in context: 
> http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.






Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its 

Re: [Pharo-dev] Google Code Shutdown

[Blondeau Vincent]

Hi,

Sorry but I am using Windows… not because I want to but because I have to... So 
the therapy will not work ;)
Actually, the bugtracker of Moose can be on github, but the git user experience 
under Windows has to be improved if we want to use efficiently the other 
functionalities of github (pull requests, commit, branches,…).

Cheers,
Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Peter 
Uhnák
Envoyé : lundi 3 août 2015 11:56
À : Pharo Development List
Objet : Re: [Pharo-dev] Google Code Shutdown

As long as nobody on your team is using Windows, git(hub) is quite good. :)
(And if you have Windows user, then find him a therapy first, or push for 
libcgit :))

On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel 
mailto:alexandre.ber...@me.com>> wrote:
Github is indeed appealing.

Cheers,
Alexandre



> On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris 
> mailto:s...@clipperadams.com>> wrote:
>
> Tudor Girba-2 wrote
>> Would you like to help us move the moose-technology project?
>
> Sure. What do you have in mind? It seems exporting to GitHub is the easiest
> option. There are a few limitations, but I've had good experiences...
>
>
>
> -
> Cheers,
> Sean
> --
> View this message in context: 
> http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.







Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] [Pharo-users] [ANN] RProjectConnector V1.0

[Blondeau Vincent]

Hi Juampi,

I know that the libraries are difficult to configure. We will improve that.
I don’t have a Mac, but as far as I know, you need to put the R libraries where 
are the Pharo ones like “libAsynchFilePlugin.dylib”.

If you didn’t do it, you need to restart the Pharo image at each time you 
change the library location and you need to install R (to copy the libraries 
seems not enough).

If it works, inspect “self nbGetSymbolAddress: 'Rf_initEmbeddedR' module: #R” 
should show you a NBExternalAddress instead of nil.

Furthermore, you need to use the 32 bits R libraries, Pharo doesn’t not support 
yet the 64 bit libs.

I hope that will be helpful,

Regards,

Vincent

De : Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] De la part de 
Juan Pablo Sandoval Alcocer
Envoyé : vendredi 13 mars 2015 23:20
À : Any question about pharo is welcome
Cc : Pharo Development List
Objet : Re: [Pharo-users] [ANN] RProjectConnector V1.0

Hi,

I was trying to use RProjectConnector in my Mac (1.9.1) and i have some issues 
:(.

I have copied the dynamic libraries of R to /usr/lib directory (.i.e. 
libR.dylib). But PharoVM does not find the libraries. For instance, this line 
of code returns always nil.

  self nbGetSymbolAddress: 'Rf_initEmbeddedR' module: #R
  "copied from the project"

I also tried copying the libraries to folder Pharo.app/Contents/MacOS/Plugins. 
or passing the library name as parameter like:

  self nbGetSymbolAddress: 'Rf_initEmbeddedR' module: 'libR.dylib'
or

  self nbGetSymbolAddress: 'Rf_initEmbeddedR' module: 
'/usr/lib/libR.dylib'

But i had not success. Could someone help me? I am doing something wrong?

Thanks,
Juampi






2014-12-08 11:10 GMT-03:00 Blondeau Vincent 
mailto:vincent.blond...@worldline.com>>:
Hello everyone,

I am glad to announce the first version of the RProjectConnector, a binding 
between Pharo and R using NativeBoost.

You can now call directly your R methods from Pharo:
data := (1 to: 1000) collect: #yourself.
res := (#acf asRFunctionWith: {data}) eval

To use it, you should copy the R libraries near the Pharo VM (see the 
documentation on SmalltalkHub to see how to proceed) and

Gofer it

smalltalkhubUser: 'VincentBlondeau' project: 'RProjectConnector';

configuration;

loadStable
Don’t forget to relaunch Pharo after the installation to be able to use the 
connector.

The sources are available on Smalltalkhub:
http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector

if you want to participate, just ask me!

Cheers,

Vincent BLONDEAU



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.



--
Saludos,
Juan Pablo



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet,

Re: [Pharo-dev] Recover lost changes | Where are class definitions?

[Blondeau Vincent]

Hi,

It is a known bug: 
https://pharo.fogbugz.com/f/cases/13290/Recover-lost-changes-doesn-t-recover-classes-created
There are not only the classes but all the refactorings are not saved in the 
"recent changes".
You can't display them or having them back.

I think that it is a pity that is doesn't work...

You can use Epicea instead or save more frequently...

Regards,
Vincent


-Message d'origine-
De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Noury 
Bouraqadi
Envoyé : mercredi 28 janvier 2015 16:13
À : Pharo Development List
Objet : [Pharo-dev] Recover lost changes | Where are class definitions?

Hi,

I tried recovering code lost when an image quits without saving.
But, in the "Recent changes", I don't see class definitions.

I tesed this in Pharo 3 latest and in Pharo 4 latest too.

Is there an option to display them? I guess they are hidden with other "DoIts", 
but I can't figure out  how to display them back.

Thanx,
Noury


Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Wrapping RegQueryValueExA in NativeBoost

[Blondeau Vincent]

Hi,

Happy new year too!

I succeeded to have a working example. I wrote the code but I can't commit it. 
Can you add me on the project please?

Just to give some indications for the code I changed.

Globally the primitive call is good. But when you pass 'nil' as argument for 
the primitive, it will not be converted to 'null' ('null' have for value 0). To 
have the 0, either you change nil into 0 or you add the option 
#optCoerceNilToNull in the call (because it is not the default...) (See 
'NBNativeCodeGen class>>defaultOptions' for the others). It is the mainly 
problem!

Concerning the arguments allocation there is some tips:
'NativeBoost allocate: ' allocates a memory segment of the size given 
by  and return the address to it.
But it is better to use 'NativeBoost allocate:  (NBExternalType sizeOf: 
'ulong')' or 'NativeBoost allocate:  (NBExternalType sizeOf: 'DWORD')' for both 
dwType and lSize arguments.

With some advance, you will see in the example4 that the RegQueryValueExA 
doesn't return a valid error value... I don't know why...

I hope it will be helpful,

Cheers,
Vincent

-Message d'origine-
De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Torsten 
Bergmann
Envoyé : dimanche 4 janvier 2015 21:43
À : Pharo Development List
Objet : [Pharo-dev] Wrapping RegQueryValueExA in NativeBoost

Hi,

Happy new year!

I try to wrap some API methods using NativeBoost to access Win32 Registry and 
broaden the Pharo support for Windows. Currently I'm already able to

 - create registry keys (RegCreateKeyA API)
 - open registry keys (RegOpenKeyExA API)
 - delete registry keys (RegDeleteKeyA API)
 - close registry key handles (RegCloseKey API)

Now I additionally want to query some keys using the "RegQueryValueExA" API 
(http://msdn.microsoft.com/en-us/library/windows/desktop/ms724911%28v=vs.85%29.aspx).

As I tried an example in an elder Smalltalk/MT first (see attached) I know it 
is working from the Win32 API side.

My NativeBoost definition in Pharo for wrapping the function looks like this 
(similar to MSDN):

   regQueryValueExA: hKey with: lpValueName with: lpReserved with: lpType with: 
lpData with: lpcbData


^ self nbCall: #(LONG RegQueryValueExA(
 HKEY hKey,
 LPCTSTR lpValueName,
 LPDWORD lpReserved,
 LPDWORD lpType,
 LPBYTE lpData,
 LPDWORD lpcbData)) module: #advapi32

But when I call it I get a "Generic error" thrown by NB and independent how 
hard I try I can not get this call to work in NativeBoost. I checked all 
arguments, checked the type definitions (pool WinTypes which is similar to 
NBWinTypes), played with options, ... but was not able to find out what I'm 
doing wrong in Pharo. Meanwhile after investing several days of my spare time 
it looks like I cant "see the wood because of all the trees".

I would really appreciate if someone with enough knowledge of NativeBoost could 
have a second look to point my into the right direction.

To reproduce:
=
  - use a fresh Pharo4.0 Latest update: #40428
  - open World menu -> Configuration Browser and load "OSWindows" project
  - go to class WinRegistry
   - there is the NativeBoost API definition in method 
#regQueryValueExA:with:with:with:with:with:
   - and a method #example2 that calls this in a similar way as in my 
Smalltalk/MT example
 (if you try this example you get the "Generic error")

Many thanks in advance!

Bye
T.



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] NativeBoost libraries hosting

[Blondeau Vincent]

Hi,

Some of us are developing some applications by using NativeBoost, which is a 
great tool for Pharo.
But when we want to distribute our application, we have to give the libraries 
with it.
We can integrate the library in the package, give a link to download an 
application and copy the libraries near the Pharo VM, or put it on dropbox, but 
it seems that are not good solutions.

Maybe we should have a hosting platform for these libraries?
Does http://smalltalkhub.com or http://files.pharo.org/ can do the hosting?

Cheers,

Vincent




Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Pharo-dev Digest, Vol 20, Issue 158

[Blondeau Vincent]

-Message d'origine-
De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de 
csra...@bol.com.br
Envoyé : mardi 16 décembre 2014 18:48
À : pharo-dev@lists.pharo.org
Objet : Re: [Pharo-dev] Pharo-dev Digest, Vol 20, Issue 158

Hi Vincent,

 > > GoferitsmalltalkhubUser:   'VincentBlondeau'project:
> > > 'RProjectConnector'; configuration;  loadStable Don't  forget to
> > > relaunch  Pharo after  the installation  to be  able to  use the
> > > connector.
> >  After the succesfully install via Gofer, the relaunching of Pharo
> > with the image containing  RProjectConnector never starts, and for
> > the worse  no messages are  availble (even  in the stderr  file in
> > image directory).  [snipped] How can I troubleshooted this?
> >
>  That seems  strange...  Do  you have  a crash.dmp  in the  Pharo VM
> folder?

No I don't find any signal of activity for this (nor in the Windows task 
manager to see if the Pharo.exe became zombie.

> Which  is the version of  Pharo you are using  ? (Pharo 4.0 and  3.0
> are  good)  Is  the  image is  even  running  but  in  the background?

I'm running Windows 8.1, Pharo3.0 Latest update: #30862.

The path for Pharo is C:\Users\csrabak\Fuba\H\Pharo3.0 and this is its content:

FT2Plugin.dll
Pharo.exe
Pharo.ini
Pharo3.0.changes
Pharo3.0.image
Pharo3.0.working.changes
Pharo3.0.working.image
PharoV30.sources
R.dll
README.txt
RProjectConnector.changes
RProjectConnector.image
Rblas.dll
Rgraphapp.dll
Riconv.dll
Rlapack.dll
Rzlib.dll
SqueakFFIPrims.dll
SqueakSSL.dll
gtoolkit.changes
gtoolkit.image
libcairo-2.dll
libeay32.dll
libfreetype-6.dll
libgit2.dll
libpixman-1-0.dll
libpng-3.dll
libssh2-1.dll
ssleay32.dll
stderr
stdout
zlib1.dll

>  Also check if the VM folder contains some blanks, maybe it can be a
> problem...

As you can see above, the path has no blanks in its entire pathname.

>  If  you  miss  something  in  the  config,  you  should  receive  a
> PostMortem  error:  'The  R  session  is  not  well  initialized  at
> startUp...'
>

I cannot arrive at this point... is there any VM or image switch that could 
help in this case?

>startUp
< - Try to restart the image
< - Re-execute in the order: RSession checkLibs. RSession checkSession. 
RSession checkWorking
< - Try to launch some tests
< Regards,
< Vincent

Regards,

--
Cesar Rabak


Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] [ANN] RProjectConnector V1.0

[Blondeau Vincent]

-Message d'origine-
De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de 
csra...@bol.com.br
Envoyé : mardi 16 décembre 2014 15:14
À : pharo-dev@lists.pharo.org
Objet : Re: [Pharo-dev] [ANN] RProjectConnector V1.0

Vincent BLONDEAU a ecrit:

>  Hello everyone,
>  I am glad to announce the first version of the RProjectConnector, a
> binding between Pharo and R using NativeBoost.
>  You can now call directly your R methods from Pharo: data := (1 to:
> 1000)  collect: #yourself.   res :=  (#acf asRFunctionWith:  {data})
> eval
>  To use it, you  should copy the R libraries near  the Pharo VM (see
> the documentation on SmalltalkHub to see how to proceed) and

I attempted to follow the directions at SmalltalkHub, but the instructions 
there call for copying some DLLs, and in particular the "grid.dll" is not 
available in the present R for Win (3.1.2) installation.


<"grid.dll" seems not required to do it working.


>  Gofer it
>  smalltalkhubUser: 'VincentBlondeau' project: 'RProjectConnector';
> configuration;  loadStable
>
> Don't forget to relaunch Pharo after the installation to be able to use
> the connector.

After the succesfully install via Gofer, the relaunching of Pharo with the 
image containing RProjectConnector never starts, and for the worse no messages 
are availble (even in the stderr file in image directory).

[snipped]

How can I troubleshooted this?

Re: [Pharo-dev] Excel binding

[Blondeau Vincent]

Nice!

Can I extend your project to add the .xlsx reading?

Regards,

Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de  
?
Envoyé : mercredi 10 décembre 2014 01:16
À : Pharo Development List
Objet : Re: [Pharo-dev] Excel binding

Yes, including this, but not limited to this.

I.e. not only generation, but also reading. Generation is just somewhat simpler 
- so I started from this point.

I announced it some tim ago, it's http://ss3.gemstone.com/ss/Tabular.html

2014-12-09 20:49 GMT+03:00 Esteban A. Maringolo 
mailto:emaring...@gmail.com>>:
El Tue Dec 09 2014 at 2:22:32 PM, Юрий Мироненко 
mailto:assargad...@gmail.com>> escribió:
I'm working on XLSX / ODS support code just now.
Nothing done on reading the data yet, but it may be easily switched.

But my plans do not includes support of (binary) XLS format.



Are you working on OpenXML (.xlsx) file generation?

Regards!




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Excel binding

[Blondeau Vincent]

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Markus 
Fritsche
Envoyé : lundi 8 décembre 2014 19:26
À : Pharo Development List
Objet : Re: [Pharo-dev] Excel binding

Replies inline
On 08.12.2014 17:07, Blondeau Vincent wrote:


De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Esteban 
A. Maringolo
Envoyé : lundi 8 décembre 2014 16:01
À : Pharo Development List
Objet : Re: [Pharo-dev] Excel binding

El Mon Dec 08 2014 at 11:41:23 AM, Markus Fritsche 
mailto:mfrits...@reauktion.de>> escribió:
On 2014-12-08 15:22, Blondeau Vincent wrote:
> Does someone know if there is a mean to access Excel sheets from Pharo
> to get data?

> I don't want to use .csv files but .xls/.xlsx files.

If you're just going to use .xlsx files, it might be possible to unzip
the file and peek the xml representation of that table (not that I've
done it though).
By unzip the file you actually see the xml, but I will complicated to use the 
values of the formula cells and to differentiate the sheets...
Yup - I don't know the excel xml format, just remembered that it might be an 
option...



If you're going to support .xls / Excel < 2003 files, you will probably
need a COM-bridge. I remember that I've seen it for Squeak in the past,
I don't recall having seen it for Pharo.

It is only Excel > 2003.


Another kind of hackish solution could be setting up an ODBC driver for
Excel files and then using DBXTalk/ODBC or the ConfigurationOfODBC-based 
package.



I have tried.

But when I launch the DBXTalk tests it asked me to choose a DBXODBX*Facility... 
Which one should I choose?

here is how I connect to an access database on windows:

execute once per session:
OpenDBX current: NBPharoOpenDBX new.

then (access):

| aRow conn settings result |
settings := DBXConnectionSettings host: '' port: '' database: 
'' userName: '' userPassword: ''.
conn := ((DBXConnection new settings: settings) platform: DBXOdbcBackend new) 
connect.
conn open.
result := conn execute: 'SELECT * FROM '.
aRow := result nextRow.
[ aRow notNil ] whileTrue: [
aRow values do: [ :value | Transcript show: value; show: $; ]. Transcript 
cr. aRow := result nextRow ].
conn close.

Everything in <> brackets needs to be replaced by actual values. Also, the ODBC 
backend doesn't support many types => which will probably break too :-(

And you will need libopendbx-1.dll, libopendbxplus-1.dll and 
opendbx\libodbcbackend-1.dll in your image directory.

That all being said - before I'll dive into that, I would probably just whip up 
a vba script to convert the excel tables to text files in bulk.

Thanks.



Should I install some plugins?

And in ConfigurationOfODBC there is no tests and doc so I don't know how to 
launch it...
I think there are tests in the monticello repository next to the ODBC package 
(there's probably a script command to install them, but I am usually faster 
just installing the package from Monticello manually).
Nope… Unfortunally there is nothing in 
http://smalltalkhub.com/mc/PharoExtras/ODBC/main …

ODBC seems actually not be a good solution. I have to create one ODBC 
connection by Excel file and I have many of them…

I thinks that in my case OLE seems better.

Regards,

Vincent


Kind regards
  Markus



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Excel binding

[Blondeau Vincent]

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Esteban 
A. Maringolo
Envoyé : lundi 8 décembre 2014 16:01
À : Pharo Development List
Objet : Re: [Pharo-dev] Excel binding

El Mon Dec 08 2014 at 11:41:23 AM, Markus Fritsche 
mailto:mfrits...@reauktion.de>> escribió:
On 2014-12-08 15:22, Blondeau Vincent wrote:
> Does someone know if there is a mean to access Excel sheets from Pharo
> to get data?

> I don't want to use .csv files but .xls/.xlsx files.

If you're just going to use .xlsx files, it might be possible to unzip
the file and peek the xml representation of that table (not that I've
done it though).

If you're going to support .xls / Excel < 2003 files, you will probably
need a COM-bridge. I remember that I've seen it for Squeak in the past,
I don't recall having seen it for Pharo.
I see it here: 
http://ss3.gemstone.com/ss/COM.html/Overview?_s=nm1ShYEJFkyZYmBY&_k=rAHtcYsTEzWiJL5n
Could I have access to the code please?
Thanks in advance,
Vincent


Another kind of hackish solution could be setting up an ODBC driver for
Excel files and then using DBXTalk/ODBC or the ConfigurationOfODBC-based
package.

All of this assuming you're running Pharo in Windows.

 Regards!



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Excel binding

[Blondeau Vincent]

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Esteban 
A. Maringolo
Envoyé : lundi 8 décembre 2014 16:01
À : Pharo Development List
Objet : Re: [Pharo-dev] Excel binding

El Mon Dec 08 2014 at 11:41:23 AM, Markus Fritsche 
mailto:mfrits...@reauktion.de>> escribió:
On 2014-12-08 15:22, Blondeau Vincent wrote:
> Does someone know if there is a mean to access Excel sheets from Pharo
> to get data?

> I don't want to use .csv files but .xls/.xlsx files.

If you're just going to use .xlsx files, it might be possible to unzip
the file and peek the xml representation of that table (not that I've
done it though).
By unzip the file you actually see the xml, but I will complicated to use the 
values of the formula cells and to differentiate the sheets...


If you're going to support .xls / Excel < 2003 files, you will probably
need a COM-bridge. I remember that I've seen it for Squeak in the past,
I don't recall having seen it for Pharo.

It is only Excel > 2003.


Another kind of hackish solution could be setting up an ODBC driver for
Excel files and then using DBXTalk/ODBC or the ConfigurationOfODBC-based 
package.



I have tried.

But when I launch the DBXTalk tests it asked me to choose a DBXODBX*Facility... 
Which one should I choose? Should I install some plugins?

And in ConfigurationOfODBC there is no tests and doc so I don't know how to 
launch it...



I heard about OLE (Object Linking and Embedding) to interact with Windows 
objects. Do you know it and what is the difference?

All of this assuming you're running Pharo in Windows.

 Regards!




Of course !



Regards,

Vincent




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] Excel binding

[Blondeau Vincent]

Hi,

Does someone know if there is a mean to access Excel sheets from Pharo to get 
data?
I don't want to use .csv files but .xls/.xlsx files.

Thanks in advance

Cheers,

Vincent BLONDEAU




Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] [ANN] RProjectConnector V1.0

[Blondeau Vincent]

Hello everyone,

I am glad to announce the first version of the RProjectConnector, a binding 
between Pharo and R using NativeBoost.

You can now call directly your R methods from Pharo:
data := (1 to: 1000) collect: #yourself.
res := (#acf asRFunctionWith: {data}) eval

To use it, you should copy the R libraries near the Pharo VM (see the 
documentation on SmalltalkHub to see how to proceed) and

Gofer it

smalltalkhubUser: 'VincentBlondeau' project: 'RProjectConnector';

configuration;

loadStable
Don't forget to relaunch Pharo after the installation to be able to use the 
connector.

The sources are available on Smalltalkhub:
http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector

if you want to participate, just ask me!

Cheers,

Vincent BLONDEAU



Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Code retrieval on primitive failed

[Blondeau Vincent]

Finally, I succeeded to retrieve my code !

I tried with the Cog VM Simulator to open my image.
It opened my crashed image in the simulator without any problem (it seems that 
the failing primitive has been caught).
But I cannot interact with the image through the simulator workspace and the 
morph.
It seems that you can launch some code by doit to export a package named 
MyPackage:

cos systemAttributes
   at: 2 put: '-doit';
   at: 3 put:(‘RPackage named:’’MYPackage’) 
fileout ’]

But this did not work because my code contains shared pools and it cannot be 
filed out…


In parallel, I tried the other solution of Clement by changing the bytecode in 
the .image itself.

If the problem comes from a native boost primitive, you should use a cogvm : 
(e.g. http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip) 
to launch the failing image.
After that, you should see the crash log and see which are the code that is 
failing (apparently one of the top method in the stack).
The best is to have the Smalltalk code of this method because you have to 
retrieve the associated bytecode. Else either you try to remember exactly the 
content of the method or you take another method in the stack where you have 
the code.

Once you have  identified the method, extract the bytecode:
on Pharo4 with the right click on the method name and by printing ‘self 
bytecode hex’
on Pharo3 inspect the class containing the method, find the right compiled 
method and print ‘self bytecode hex’

After that open the broken image with a hexadecimal editor (I use HxD under w7) 
(do a COPY before).
Find the bytecode of the method and replace it by several 120 (78 in hex).
As the bytecodes are not unique, it is possible to do several replacements. If 
you don’t want that, you can find another bytecode available in the stack 
trace. Longest is the bytecode, less will be the number of finding matches.

Try to reopen your image with the cogwm. If it doesn’t work either you broke a 
critical method of your image (so try again with another bytecode) either you 
have another failure so you start again to find the good method.

Once you can open it. Save your code!!!
The file out didn’t work for me so I commited with Monticello in local and it 
worked!

So don’t forget to commit!

Vincent


De : Blondeau Vincent
Envoyé : mercredi 3 décembre 2014 18:41
À : Pharo Development List
Objet : RE: [Pharo-dev] Code retrieval on primitive failed



De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Clément 
Bera
Envoyé : mercredi 3 décembre 2014 17:54
À : Pharo Development List
Objet : Re: [Pharo-dev] Code retrieval on primitive failed

Please send the full stack trace. You don't have only three lines, do you ?

No, indeed (the full stack is attached).

There's one solution that Igor does sometimes that you can try...For that you 
need to remember what code you changed that now crashes the image in smalltalk. 
Do you know what code crash your image ?
Could you rewrite it (exactly the same code) in a fresh image ?
If so the process is as follow:
- rewrite the crashing code in a fresh image
- extract the bytecode from the compiled method
- open a copy of your image with an hexadecimal editor, look for the bytecode 
pattern, replace it by returnself (byte 120 the number of times needed)
- try open your copy. Do as little things as possible (typically, only file out 
your packages, monticello will most probably not work)

Ok I will try this but this is more a generic printing method that is the 
problem (see trace)… And not a specific method…
I tried but it seems not adapted to my case…

The alternative is to open your image on top of the cog simulator. Word has 
been that there's a Pharo 3 image running the cog simulator, you can use that 
to debug the code and fix it. Alternatively use a squeak vmmaker image that you 
can build with this script:
$ svn co http://www.squeakvm.org/svn/squeak/branches/Cog/image
$ cd ./image
$ ./buildsqueaktrunkvmmakerimage.sh
 You put a halt on the implementation of primitive 117 in the simulator (named 
primitives call such as NB calls) to catch the crash and fix it from there in 
the simulator.

That seems better ! I am trying this way.

Good luck and have fun :-)

Thanks :)


2014-12-03 17:04 GMT+01:00 Blondeau Vincent 
mailto:vincent.blond...@worldline.com>>:
Hello everyone,

I am doing some developments with NativeBoost and unfortunaly I succeed to save 
my image in a unstable state.
I am using the last moose image i.e.: Pharo3.0 - Latest update: #30860.

So when I want to launch my image, I get a primitive faillure.
The interesting part of the stack trace is :
Stack backtrace:
[07EE7A1B] ??? + 0 in (null)
[00539AB5] ??? + 1284789 in Pharo.exe

Smalltalk stack dump:
  0x2410b8 M NBFFICallout class(NBNativeCodeGen class)>retrySend:  0x4c70b4c: 
a(n) NBFFICallout cla

Re: [Pharo-dev] Code retrieval on primitive failed

[Blondeau Vincent]

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Clément 
Bera
Envoyé : mercredi 3 décembre 2014 17:54
À : Pharo Development List
Objet : Re: [Pharo-dev] Code retrieval on primitive failed

Please send the full stack trace. You don't have only three lines, do you ?

No, indeed (the full stack is attached).

There's one solution that Igor does sometimes that you can try...For that you 
need to remember what code you changed that now crashes the image in smalltalk. 
Do you know what code crash your image ?
Could you rewrite it (exactly the same code) in a fresh image ?
If so the process is as follow:
- rewrite the crashing code in a fresh image
- extract the bytecode from the compiled method
- open a copy of your image with an hexadecimal editor, look for the bytecode 
pattern, replace it by returnself (byte 120 the number of times needed)
- try open your copy. Do as little things as possible (typically, only file out 
your packages, monticello will most probably not work)

Ok I will try this but this is more a generic printing method that is the 
problem (see trace)… And not a specific method…
I tried but it seems not adapted to my case…

The alternative is to open your image on top of the cog simulator. Word has 
been that there's a Pharo 3 image running the cog simulator, you can use that 
to debug the code and fix it. Alternatively use a squeak vmmaker image that you 
can build with this script:
$ svn co http://www.squeakvm.org/svn/squeak/branches/Cog/image
$ cd ./image
$ ./buildsqueaktrunkvmmakerimage.sh
 You put a halt on the implementation of primitive 117 in the simulator (named 
primitives call such as NB calls) to catch the crash and fix it from there in 
the simulator.

That seems better ! I am trying this way.

Good luck and have fun :-)

Thanks :)


2014-12-03 17:04 GMT+01:00 Blondeau Vincent 
mailto:vincent.blond...@worldline.com>>:
Hello everyone,

I am doing some developments with NativeBoost and unfortunaly I succeed to save 
my image in a unstable state.
I am using the last moose image i.e.: Pharo3.0 - Latest update: #30860.

So when I want to launch my image, I get a primitive faillure.
The interesting part of the stack trace is :
Stack backtrace:
[07EE7A1B] ??? + 0 in (null)
[00539AB5] ??? + 1284789 in Pharo.exe

Smalltalk stack dump:
  0x2410b8 M NBFFICallout class(NBNativeCodeGen class)>retrySend:  0x4c70b4c: 
a(n) NBFFICallout class
  0x2410ec I NBFFICallout class(NBNativeCodeGen class)>retrySend:  0x4c70b4c: 
a(n) NBFFICallout class
0x78a0d90 s RDoubleVector(OrderedCollection)>at:

Then I wanted to retrieve my changes on a new image but, as the doIts are not 
recorded, I have neither the method deletions nor all the operations on classes 
nor the trait methods that are recorded as Doits with preamble:  Trait method.

I tried to launch my image with squeak (which doesn’t support NativeBoost) to 
hope saving or commit my code. But as I am calling a primitive at startup of 
the image to initialize the external environement. I got the following trace :
[31m Startup Error: PrimitiveFailed: primitive #isEnabled in NativeBoost 
class failed
[0mNativeBoost class(Object)>>primitiveFailed:
NativeBoost class(Object)>>primitiveFailed
NativeBoost class>>isEnabled
NativeBoost class>>forCurrentPlatform
NativeBoost class>>loadSymbol:fromModule:
RSession class(Object)>>nbGetSymbolAddress:module:

So what can I do to retrieve all my code without loose a day to rewrite it?

Thanks in advance

Vincent




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.




Ce message et les pièces jointes sont confidentiels et réservés à l&#

[Pharo-dev] Code retrieval on primitive failed

[Blondeau Vincent]

Hello everyone,

I am doing some developments with NativeBoost and unfortunaly I succeed to save 
my image in a unstable state.
I am using the last moose image i.e.: Pharo3.0 - Latest update: #30860.

So when I want to launch my image, I get a primitive faillure.
The interesting part of the stack trace is :
Stack backtrace:
[07EE7A1B] ??? + 0 in (null)
[00539AB5] ??? + 1284789 in Pharo.exe

Smalltalk stack dump:
  0x2410b8 M NBFFICallout class(NBNativeCodeGen class)>retrySend:  0x4c70b4c: 
a(n) NBFFICallout class
  0x2410ec I NBFFICallout class(NBNativeCodeGen class)>retrySend:  0x4c70b4c: 
a(n) NBFFICallout class
0x78a0d90 s RDoubleVector(OrderedCollection)>at:

Then I wanted to retrieve my changes on a new image but, as the doIts are not 
recorded, I have neither the method deletions nor all the operations on classes 
nor the trait methods that are recorded as Doits with preamble:  Trait method.

I tried to launch my image with squeak (which doesn't support NativeBoost) to 
hope saving or commit my code. But as I am calling a primitive at startup of 
the image to initialize the external environement. I got the following trace :
[31m Startup Error: PrimitiveFailed: primitive #isEnabled in NativeBoost 
class failed
[0mNativeBoost class(Object)>>primitiveFailed:
NativeBoost class(Object)>>primitiveFailed
NativeBoost class>>isEnabled
NativeBoost class>>forCurrentPlatform
NativeBoost class>>loadSymbol:fromModule:
RSession class(Object)>>nbGetSymbolAddress:module:

So what can I do to retrieve all my code without loose a day to rewrite it?

Thanks in advance

Vincent




Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] [Vm-dev] Re: How to check whether the handle is always valid with NativeBoost ?

[Blondeau Vincent]

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de 
Blondeau Vincent
Envoyé : lundi 17 novembre 2014 16:41
À : Pharo Development List
Cc : Squeak Virtual Machine Development Discussion
Objet : Re: [Pharo-dev] [Vm-dev] Re: How to check whether the handle is always 
valid with NativeBoost ?

Hi

Thanks a lot for your answers !
It is very helpful.

But how can I launch a script at the startup or shutdown of the image 
especially for Pharo ?

Implement in the class side :
>>initialize
>>  Smalltalk addToStartUpList: self.

And
>>startUp
“some code”
>>shutDown
“some code”


Vincent



De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Igor 
Stasenko
Envoyé : jeudi 13 novembre 2014 23:40
À : Squeak Virtual Machine Development Discussion
Cc : Pharo Development List
Objet : Re: [Pharo-dev] [Vm-dev] Re: How to check whether the handle is always 
valid with NativeBoost ?



On 13 November 2014 18:37, Eliot Miranda 
mailto:eliot.mira...@gmail.com>> wrote:

Hi Vincent,

   one way, used in VisualWorks, is to ensure that only valid handles exist.  
So very early at startup the system does some allInstances invocations on the 
classes of handles and invalidates all the handles found.  This doesn't fix 
handles stored as raw integers anywhere, but provided the system is designed to 
have specific objects for external handles (and I hope it is) this shouldn't 
happen.

Since snapshot is relatively rare and start-up relatively frequent (at least in 
e.g. a web deployment context), one performance improvement is to do the 
allInstances before snapshot, and then merely enumerate the collection of 
handles, rather than use allInstances.


Just to add:
 - (re)validating external resources could vary depending on library or how 
short/long-lived the resource is etc.
As you described, one of the scenarios is to flush invalid handles at system 
startup.
In NB i using session checking, to do it lazily, once there's an attempt to use 
external resource.
But all that, of course, doesn't addresses the problem when external resource 
get invalidated, for one or another reason, during same session.
Using proxy to control each and every access to external resource is, of 
course, an ultimate solution, but alas, quite expensive since imposes high 
overhead. I would call it a brute-force solution.
To minimize overhead, my approach often is to place a check at key entry part 
of algorithm,
so if check passed, then rest of algorithm can run safely without excessive 
checking.
But that really depends on design of external library/framework, whether it 
possible or not.
Usually, if you cleverly organize the access to services, it is possible to do 
it without using brute-force proxyfying.

On Thu, Nov 13, 2014 at 9:05 AM, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:
Hi !

I am doing a binding to the R library with NativeBoost.
So I create some external objects and apply some functions on them.

If the handle to the object is not valid, either the function crashes or gives 
a bad result.

How can I ensure to have a valid pointer at anytime ?

I see two solutions:

-  Either check at any NativeBoost call that the handle is valid (by 
checking the session id)

-  Or do a proxy that checks the session and recreate the external 
object.

What do you think ?

Thanks in advance,

Cheers,
Vincent BLONDEAU




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.



--
best,
Eliot




--
Best regards,
Igor Stasenko.



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. 

Re: [Pharo-dev] [Vm-dev] Re: How to check whether the handle is always valid with NativeBoost ?

[Blondeau Vincent]

Hi

Thanks a lot for your answers !
It is very helpful.

But how can I launch a script at the startup or shutdown of the image 
especially for Pharo ?

Vincent



De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Igor 
Stasenko
Envoyé : jeudi 13 novembre 2014 23:40
À : Squeak Virtual Machine Development Discussion
Cc : Pharo Development List
Objet : Re: [Pharo-dev] [Vm-dev] Re: How to check whether the handle is always 
valid with NativeBoost ?



On 13 November 2014 18:37, Eliot Miranda 
mailto:eliot.mira...@gmail.com>> wrote:

Hi Vincent,

   one way, used in VisualWorks, is to ensure that only valid handles exist.  
So very early at startup the system does some allInstances invocations on the 
classes of handles and invalidates all the handles found.  This doesn't fix 
handles stored as raw integers anywhere, but provided the system is designed to 
have specific objects for external handles (and I hope it is) this shouldn't 
happen.

Since snapshot is relatively rare and start-up relatively frequent (at least in 
e.g. a web deployment context), one performance improvement is to do the 
allInstances before snapshot, and then merely enumerate the collection of 
handles, rather than use allInstances.


Just to add:
 - (re)validating external resources could vary depending on library or how 
short/long-lived the resource is etc.
As you described, one of the scenarios is to flush invalid handles at system 
startup.
In NB i using session checking, to do it lazily, once there's an attempt to use 
external resource.
But all that, of course, doesn't addresses the problem when external resource 
get invalidated, for one or another reason, during same session.
Using proxy to control each and every access to external resource is, of 
course, an ultimate solution, but alas, quite expensive since imposes high 
overhead. I would call it a brute-force solution.
To minimize overhead, my approach often is to place a check at key entry part 
of algorithm,
so if check passed, then rest of algorithm can run safely without excessive 
checking.
But that really depends on design of external library/framework, whether it 
possible or not.
Usually, if you cleverly organize the access to services, it is possible to do 
it without using brute-force proxyfying.

On Thu, Nov 13, 2014 at 9:05 AM, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:
Hi !

I am doing a binding to the R library with NativeBoost.
So I create some external objects and apply some functions on them.

If the handle to the object is not valid, either the function crashes or gives 
a bad result.

How can I ensure to have a valid pointer at anytime ?

I see two solutions:

-  Either check at any NativeBoost call that the handle is valid (by 
checking the session id)

-  Or do a proxy that checks the session and recreate the external 
object.

What do you think ?

Thanks in advance,

Cheers,
Vincent BLONDEAU




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.



--
best,
Eliot




--
Best regards,
Igor Stasenko.



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabili

[Pharo-dev] How to check whether the handle is always valid with NativeBoost ?

[Blondeau Vincent]

Hi !

I am doing a binding to the R library with NativeBoost.
So I create some external objects and apply some functions on them.

If the handle to the object is not valid, either the function crashes or gives 
a bad result.

How can I ensure to have a valid pointer at anytime ?

I see two solutions:

-  Either check at any NativeBoost call that the handle is valid (by 
checking the session id)

-  Or do a proxy that checks the session and recreate the external 
object.

What do you think ?

Thanks in advance,

Cheers,
Vincent BLONDEAU




Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Time Series in Smalltalk

[Blondeau Vincent]

Dear Hernán,

I will put the code in my own repo with a configuration that you can import.
NumericalMethods package seems to contains the same things that Scismalltalk. 
So there is no timeseries methods.

Cheers,
Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Hernán 
Morales Durand
Envoyé : vendredi 31 octobre 2014 14:42
À : Pharo Development List
Objet : Re: [Pharo-dev] Time Series in Smalltalk



2014-10-31 6:50 GMT-03:00 Blondeau Vincent 
mailto:vincent.blond...@worldline.com>>:
Dear Serge,

That's nice but I will need more statistical functions to calculate 
autocorrelations.

Have you checked NumericalMethods package? (is available from the Configuration 
Browser)

These functions are already implemented in R (http://www.r-project.org/).
So, there is two solutions:
- As the sources are open, implement them in Pharo (but it is some thousands of 
lines...)
- With nativeboost, use the R libs (written in C)

As I prefer the second solution, I began to write some code with native boost 
and it seems to work well.
I can add them in SciSmalltalk package if I have the rights. But I don't know 
how to package the R libraries for the different OS...

I would ask you if you can put this code into its own repository, so we can use 
the R binding without need to load the whole SciSmalltalk, and SciSmalltalk 
could import your Configuration.
Cheers,
Hernán

Regards,

Vincent Blondeau

-Message d'origine-
De : Pharo-dev 
[mailto:pharo-dev-boun...@lists.pharo.org<mailto:pharo-dev-boun...@lists.pharo.org>]
 De la part de Serge Stinckwich
Envoyé : vendredi 24 octobre 2014 09:56
À : Pharo Development List
Objet : Re: [Pharo-dev] Time Series in Smalltalk


> On 23 Oct 2014, at 14:52, Blondeau Vincent 
> mailto:vincent.blond...@worldline.com>> wrote:
>
> Hi !
>

Dear Vincent,

>
>
> I am looking for a time series library available for Pharo.
>
> Serge Stinckwich asked the same thing a year ago 
> (http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-February/074796.html),
>  and I would know whether any improvement has been made since?
>
>

We started a really simple implementation of time series. Look at the class : 
KETimeSeries and KETimeSeriesTest in this repository: 
http://smalltalkhub.com/#!/~UMMISCO/Kendrick

Please feel free to extract these classes and extend them. Maybe we can move 
them in the SciSmalltalk repository.

Regards,
--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://doesnotunderstand.org/

Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours t

Re: [Pharo-dev] Time Series in Smalltalk

[Blondeau Vincent]

> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Serge Stinckwich
> Envoyé : vendredi 31 octobre 2014 11:39
> À : Pharo Development List
> Objet : Re: [Pharo-dev] Time Series in Smalltalk
>
>
> > On 31 Oct 2014, at 10:50, Blondeau Vincent
>  wrote:
> >
> > Dear Serge,
> >
>
> Bonjour Vincent,
>
> > That's nice but I will need more statistical functions to calculate
> autocorrelations.
> Yes having some statistical functions and tests is definitively something we
> are looking for SciSmalltalk.
>
> > These functions are already implemented in R (http://www.r-project.org/).
> > So, there is two solutions:
> > - As the sources are open, implement them in Pharo (but it is some
> > thousands of lines...)
>
> This is R code ? Do you have a link to this source ?
This is C code: you can download it here: http://cran.r-project.org/sources.html
> I'm also interested to have a native solution in Pharo. Maybe we can join our
> forces ;-)

I look at the sources a little and it seems costly to translate them. Maybe we 
can select a few. Statistical Tests looks simpler.

>
> > - With nativeboost, use the R libs (written in C)
> >
> > As I prefer the second solution, I began to write some code with native
> boost and it seems to work well.
>
> I'm a little bit worried with performance issue for the second solution ;-) 
> or R
> libs are not written in R ?

R libs are in C. So I think that the performances are not the problem.
>
> > I can add them in SciSmalltalk package if I have the rights. But I
> > don't know how to package the R libraries for the different OS...
> >
>
> Yes, this is a nice idea. We can give you access to the SciSmalltalk repo.
> Please join the ml: https://groups.google.com/forum/#!forum/scismalltalk
> What could be nice is write tests so we can use this tests latter if we want 
> to
> have a native solution.

That's what I planned to do ;)

Thanks,

Regards,
Vincent
>
> Thank you.
> Regards,
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://doesnotunderstand.org/


Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Time Series in Smalltalk

[Blondeau Vincent]

Dear Serge,

That's nice but I will need more statistical functions to calculate 
autocorrelations.
These functions are already implemented in R (http://www.r-project.org/).
So, there is two solutions:
- As the sources are open, implement them in Pharo (but it is some thousands of 
lines...)
- With nativeboost, use the R libs (written in C)

As I prefer the second solution, I began to write some code with native boost 
and it seems to work well.
I can add them in SciSmalltalk package if I have the rights. But I don't know 
how to package the R libraries for the different OS...

Regards,

Vincent Blondeau

-Message d'origine-
De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Serge 
Stinckwich
Envoyé : vendredi 24 octobre 2014 09:56
À : Pharo Development List
Objet : Re: [Pharo-dev] Time Series in Smalltalk


> On 23 Oct 2014, at 14:52, Blondeau Vincent  
> wrote:
>
> Hi !
>

Dear Vincent,

>
>
> I am looking for a time series library available for Pharo.
>
> Serge Stinckwich asked the same thing a year ago 
> (http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-February/074796.html),
>  and I would know whether any improvement has been made since?
>
>

We started a really simple implementation of time series. Look at the class : 
KETimeSeries and KETimeSeriesTest in this repository: 
http://smalltalkhub.com/#!/~UMMISCO/Kendrick

Please feel free to extract these classes and extend them. Maybe we can move 
them in the SciSmalltalk repository.

Regards,
--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://doesnotunderstand.org/


Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] Time Series in Smalltalk

[Blondeau Vincent]

Hi !

I am looking for a time series library available for Pharo.
Serge Stinckwich asked the same thing a year ago 
(http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-February/074796.html),
 and I would know whether any improvement has been made since?

Thanks

Cheers,

Vincent BLONDEAU




Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] [Moose-dev] [Solved] Pharo image corruption and fatal VM error with Roassal

[Blondeau Vincent]

Hi Alexandre,

The patch doesn't seems to be commited in Roassal2 repo...

Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de 
Alexandre Bergel
Envoyé : mercredi 6 août 2014 21:44
À : Moose-related development
Cc : Pharo Development List
Objet : Re: [Pharo-dev] [Moose-dev] [Solved] Pharo image corruption and fatal 
VM error with Roassal

Thanks Vincent!
It seems to work well.

Included in Roassal!

Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




On Aug 6, 2014, at 12:29 PM, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:


Solved !

You will found the changes in the attached .mcz.

I added some sessions guards where some Athens external objects are used.  Stef 
you were right ;)
Particularly for checking the IV TRCanvas>>canvas and on TRShape>>path that 
relies on Athens external objects.

It seems to works for me. If it is the case for you, it we be nice to integrate 
it quickly to be able to work fine :)

Thanks

Vincent

-Message d'origine-
De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de stepharo
Envoyé : jeudi 31 juillet 2014 22:58
À : Pharo Development List
Objet : Re: [Pharo-dev] [Moose-dev] Pharo image corruption and fatal VM error 
with Roassal

Alexandre

may be you should try to understand what is a session.
Because this is about 2 lines of code.

When you open an image you save 2 min ago or 2 years ago, how the system knows 
that an OS ressources is valid?
By checking the session id...

Stef

On 31/7/14 16:09, Alexandre Bergel wrote:

Yes, and this is a mess.
I've spent quite some time in getting the session working with Roassal2 and it 
still does not work. I would appreciate help on this.

Alexandre


On Jul 31, 2014, at 8:58 AM, Nicolai Hess 
mailto:nicolaih...@web.de>> wrote:


It looks like Trachel does not recreate athens external resources.
There is an example in AthensSceneView, on how to check and reload an
AthensSurface.


2014-07-31 12:51 GMT+02:00 Usman Bhatti 
mailto:usman.bha...@gmail.com>>:



On Thu, Jul 31, 2014 at 11:17 AM, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:
Yes it is. But I will not do

TRMorph allInstances do: #delete

In command line every day...


It is only intended to recover your lost work in the image not for everyday use 
:).




Vincent



De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part
de Usman Bhatti Envoyé : jeudi 31 juillet 2014 10:59 À : Pharo
Development List Cc : Moose-related development


Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error
with Roassal



This may be related to this known issue reported a few days back.

https://code.google.com/p/moose-technology/issues/detail?id=1084



And there is a possible solution to recover your image.



usman



On Thu, Jul 31, 2014 at 10:50 AM, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:

Hi,



Yesterday, I was using GraphET (a part of Roassal) to do some charts and, 
today, when I wanted to reopen the image.

And I got that :



It is *very* unpleasant...



To reproduce the bug:

1 - You can do either:

| builder |

builder := GET2Line data: (0 to: 100) .

builder

y: [ :x | x*x ].



builder open.

Or

WorldMenu -> Roassal examples -> choose an item -> click on a graph . A TRMorph 
should be opened.

2 - don't close the graph and save the pharo image.

3 - Close the pharo image

4 - Reopen it



I am under W7 x64 with the latest moose image and the VM available on the 
pharo.org website (http://files.pharo.org/platform/Pharo3.0-win.zip) from the 
10 july.

You will find the crash dump attached.





Thankfully, I managed to open the image with a latest VM 
(http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip).

Thanks a lot Eliot ! :)



And I got this:





Thanks in advance



Cheers,

Vincent BLONDEAU






Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely f

[Pharo-dev] [Solved] Pharo image corruption and fatal VM error with Roassal

[Blondeau Vincent]

Solved !

You will found the changes in the attached .mcz.

I added some sessions guards where some Athens external objects are used.  Stef 
you were right ;)
Particularly for checking the IV TRCanvas>>canvas and on TRShape>>path that 
relies on Athens external objects.

It seems to works for me. If it is the case for you, it we be nice to integrate 
it quickly to be able to work fine :)

Thanks

Vincent

-Message d'origine-
De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de stepharo
Envoyé : jeudi 31 juillet 2014 22:58
À : Pharo Development List
Objet : Re: [Pharo-dev] [Moose-dev] Pharo image corruption and fatal VM error 
with Roassal

Alexandre

may be you should try to understand what is a session.
Because this is about 2 lines of code.

When you open an image you save 2 min ago or 2 years ago, how the system knows 
that an OS ressources is valid?
By checking the session id...

Stef

On 31/7/14 16:09, Alexandre Bergel wrote:
> Yes, and this is a mess.
> I've spent quite some time in getting the session working with Roassal2 and 
> it still does not work. I would appreciate help on this.
>
> Alexandre
>
>
> On Jul 31, 2014, at 8:58 AM, Nicolai Hess  wrote:
>
>> It looks like Trachel does not recreate athens external resources.
>> There is an example in AthensSceneView, on how to check and reload an
>> AthensSurface.
>>
>>
>> 2014-07-31 12:51 GMT+02:00 Usman Bhatti :
>>
>>
>>
>> On Thu, Jul 31, 2014 at 11:17 AM, Blondeau Vincent 
>>  wrote:
>> Yes it is. But I will not do
>>
>> TRMorph allInstances do: #delete
>>
>> In command line every day...
>>
>>
>> It is only intended to recover your lost work in the image not for everyday 
>> use :).
>>
>>
>>
>>
>> Vincent
>>
>>
>>
>> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part
>> de Usman Bhatti Envoyé : jeudi 31 juillet 2014 10:59 À : Pharo
>> Development List Cc : Moose-related development
>>
>>
>> Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error
>> with Roassal
>>
>>
>>
>> This may be related to this known issue reported a few days back.
>>
>> https://code.google.com/p/moose-technology/issues/detail?id=1084
>>
>>
>>
>> And there is a possible solution to recover your image.
>>
>>
>>
>> usman
>>
>>
>>
>> On Thu, Jul 31, 2014 at 10:50 AM, Blondeau Vincent 
>>  wrote:
>>
>> Hi,
>>
>>
>>
>> Yesterday, I was using GraphET (a part of Roassal) to do some charts and, 
>> today, when I wanted to reopen the image.
>>
>> And I got that :
>>
>> 
>>
>> It is *very* unpleasant...
>>
>>
>>
>> To reproduce the bug:
>>
>> 1 - You can do either:
>>
>>  | builder |
>>
>>  builder := GET2Line data: (0 to: 100) .
>>
>>  builder
>>
>>  y: [ :x | x*x ].
>>
>>
>>
>>  builder open.
>>
>> Or
>>
>> WorldMenu -> Roassal examples -> choose an item -> click on a graph . A 
>> TRMorph should be opened.
>>
>> 2 - don't close the graph and save the pharo image.
>>
>> 3 - Close the pharo image
>>
>> 4 - Reopen it
>>
>>
>>
>> I am under W7 x64 with the latest moose image and the VM available on the 
>> pharo.org website (http://files.pharo.org/platform/Pharo3.0-win.zip) from 
>> the 10 july.
>>
>> You will find the crash dump attached.
>>
>>
>>
>>
>>
>> Thankfully, I managed to open the image with a latest VM 
>> (http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip).
>>
>> Thanks a lot Eliot ! :)
>>
>>
>>
>> And I got this:
>>
>> 
>>
>>
>>
>> Thanks in advance
>>
>>
>>
>> Cheers,
>>
>> Vincent BLONDEAU
>>
>>
>>
>>
>>
>>
>> Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
>> exclusif de ses destinataires. Il peut également être protégé par le secret 
>> professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
>> immédiatement l'expéditeur et de le détruire. L'intégrité du message ne 
>> pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra 
>> être rec

Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal

[Blondeau Vincent]

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de stepharo
Envoyé : jeudi 31 juillet 2014 22:55
À : Pharo Development List
Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal

vincent

you can take an image/change copy
your change as the change of the new image
and do recovery last changes and you get all your changes back.
Ok that is cool. But the things that I wrote in the Workspace, I can't get them 
back?
Vincent



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal

[Blondeau Vincent]

Yes it is. But I will not do
TRMorph allInstances do: #delete
In command line every day…

Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Usman 
Bhatti
Envoyé : jeudi 31 juillet 2014 10:59
À : Pharo Development List
Cc : Moose-related development
Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal

This may be related to this known issue reported a few days back.
https://code.google.com/p/moose-technology/issues/detail?id=1084

And there is a possible solution to recover your image.

usman

On Thu, Jul 31, 2014 at 10:50 AM, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:
Hi,

Yesterday, I was using GraphET (a part of Roassal) to do some charts and, 
today, when I wanted to reopen the image.
And I got that :
[cid:image001.png@01CFACAF.C4370C70]
It is *very* unpleasant…

To reproduce the bug:
1 - You can do either:
| builder |
builder := GET2Line data: (0 to: 100) .
builder
y: [ :x | x*x ].

builder open.
Or
WorldMenu -> Roassal examples -> choose an item -> click on a graph . A TRMorph 
should be opened.
2 - don’t close the graph and save the pharo image.
3 – Close the pharo image
4 - Reopen it

I am under W7 x64 with the latest moose image and the VM available on the 
pharo.org<http://pharo.org> website 
(http://files.pharo.org/platform/Pharo3.0-win.zip) from the 10 july.
You will find the crash dump attached.


Thankfully, I managed to open the image with a latest VM 
(http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip).
Thanks a lot Eliot ! :)

And I got this:
[cid:image002.png@01CFACAF.C4370C70]

Thanks in advance

Cheers,
Vincent BLONDEAU




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal

[Blondeau Vincent]

The Eliot VM doesn't comes with libCairo and Roassal doesn't work into. But 
it's helpful to reopen the image to retrieve the work done !

-Message d'origine-
De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Hilaire
Envoyé : jeudi 31 juillet 2014 10:54
À : pharo-dev@lists.pharo.org
Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal

Looks like Cairo can't be loaded.
Does the Eliot VM comes with libCairo?

Hilaire

Le 31/07/2014 16:50, Blondeau Vincent a écrit :
> Hi,
>
> Yesterday, I was using GraphET (a part of Roassal) to do some charts
> and, today, when I wanted to reopen the image.
>
> And I got that :
>
> It is **very** unpleasant...
>
> To reproduce the bug:
>
> 1 - You can do either:
>
>  | builder |
>
>  builder := GET2Line data: (0 to: 100) .
>
>  builder
>
>  y: [ :x | x*x ].
>
>  builder open.
>
> Or
>
> WorldMenu -> Roassal examples -> choose an item -> click on a graph .
> A TRMorph should be opened.
>
> 2 - don't close the graph and save the pharo image.
>
> 3 - Close the pharo image
>
> 4 - Reopen it
>
> I am under W7 x64 with the latest moose image and the VM available on
> the pharo.org website
> (http://files.pharo.org/platform/Pharo3.0-win.zip)
> from the 10 july.
>
> You will find the crash dump attached.
>
> Thankfully, I managed to open the image with a latest VM
> (http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip).
>
> Thanks a lot Eliot ! :)
>
> And I got this:
>
> Thanks in advance
>
> Cheers,
>
> Vincent BLONDEAU
>
>
> --
> --
>
> Ce message et les pièces jointes sont confidentiels et réservés à
> l'usage exclusif de ses destinataires. Il peut également être protégé
> par le secret professionnel. Si vous recevez ce message par erreur,
> merci d'en avertir immédiatement l'expéditeur et de le détruire.
> L'intégrité du message ne pouvant être assurée sur Internet, la
> responsabilité de Worldline ne pourra être recherchée quant au contenu
> de ce message. Bien que les meilleurs efforts soient faits pour
> maintenir cette transmission exempte de tout virus, l'expéditeur ne
> donne aucune garantie à cet égard et sa responsabilité ne saurait être
> recherchée pour tout dommage résultant d'un virus transmis.
>
> This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive
> this e-mail in error, please notify the sender immediately and destroy
> it. As its integrity cannot be secured on the Internet, the Worldline
> liability cannot be triggered for the message content. Although the
> sender endeavours to maintain a computer virus-free network, the
> sender does not warrant that this transmission is virus-free and will
> not be liable for any damages resulting from any virus transmitted.


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




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] Pharo image corruption and fatal VM error with Roassal

[Blondeau Vincent]

Hi,

Yesterday, I was using GraphET (a part of Roassal) to do some charts and, 
today, when I wanted to reopen the image.
And I got that :
[cid:image001.png@01CFACAA.E0CB2060]
It is *very* unpleasant...

To reproduce the bug:
1 - You can do either:
| builder |
builder := GET2Line data: (0 to: 100) .
builder
y: [ :x | x*x ].

builder open.
Or
WorldMenu -> Roassal examples -> choose an item -> click on a graph . A TRMorph 
should be opened.
2 - don't close the graph and save the pharo image.
3 - Close the pharo image
4 - Reopen it

I am under W7 x64 with the latest moose image and the VM available on the 
pharo.org website (http://files.pharo.org/platform/Pharo3.0-win.zip) from the 
10 july.
You will find the crash dump attached.


Thankfully, I managed to open the image with a latest VM 
(http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip).
Thanks a lot Eliot ! :)

And I got this:
[cid:image002.png@01CFACAD.350D7DB0]

Thanks in advance

Cheers,
Vincent BLONDEAU




Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.


crash.dmp
Description: crash.dmp

Re: [Pharo-dev] Headless mode loss of focus under windows 7

[Blondeau Vincent]

Hi Eliot,

I tried with the latest vm from your website 
(http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip -> 
SqueakConsole.exe). But unfortunately the problem is still there…

Vincent

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Eliot 
Miranda
Envoyé : mardi 29 juillet 2014 21:08
À : Pharo Development List
Objet : Re: [Pharo-dev] Headless mode loss of focus under windows 7

Hi Vincent,

use one if the console VMs from my website.  They don't open up another 
window.  Open up a recent cogwin zip and use SqueakConsole.exe

Eliot (phone)

On Jul 29, 2014, at 4:01 AM, Blondeau Vincent 
mailto:vincent.blond...@worldline.com>> wrote:
Hello everyone,

Currently I use a batch script where a moose image (based on pharo) load a 
model, export some data and close itself without saving and that several times.

I do it under windows 7 by this kind of loop in a .bat file:
FOR /L %%i IN (1,1,10) DO (
"Pharo.exe --headless sdco-sa-tooling-ci-5.image eval ‘'
)

The problem is that at each execution of pharo, I lose focus from the window 
where I was currently working (a notepad by example).
How can I do to solve it?

Thanks in advance!

Cheers,

Vincent BLONDEAU





Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

[Pharo-dev] Headless mode loss of focus under windows 7

[Blondeau Vincent]

Hello everyone,

Currently I use a batch script where a moose image (based on pharo) load a 
model, export some data and close itself without saving and that several times.

I do it under windows 7 by this kind of loop in a .bat file:
FOR /L %%i IN (1,1,10) DO (
"Pharo.exe --headless sdco-sa-tooling-ci-5.image eval ''
)

The problem is that at each execution of pharo, I lose focus from the window 
where I was currently working (a notepad by example).
How can I do to solve it?

Thanks in advance!

Cheers,

Vincent BLONDEAU



Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre 
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] [Moose-dev] Re: Re: Fwd: Font problem is still there

[Blondeau Vincent]

De : moose-dev-boun...@iam.unibe.ch [mailto:moose-dev-boun...@iam.unibe.ch] De 
la part de Stéphane Ducasse
Envoyé : vendredi 28 mars 2014 15:39
À : Pharo Development List
Cc : Moose-related development
Objet : [Moose-dev] Re: [Pharo-dev] Re: Fwd: Font problem is still there

In Pharo 3.0 this is is normal because FreeSans does not exist.

I think that we should embed a default FT font and use is as default.

Isn't the StandardFonts defaultFont ?

Vincent

Now since embedded fonts are lost when reloading Freetrype fonts.
The reloading of FreeType should be fixed.

Stef

And :
AthensSceneView new scene: [ :canvas | |s|
 canvas setFont: (LogicalFont familyName: 'FreeSans' pointSize: 
20).
s:= String newFrom: ($A to: $Z),($a to: $z), ($0 to: $9).

canvas pathTransform restoreAfter: [
   canvas pathTransform translateX: 0 Y: 50.
   canvas setPaint: Color black.
   canvas drawString:s ]

];openInWindow

And I got :



And under a fresh Pharo 3.0 :



Vincent

De : moose-dev-boun...@iam.unibe.ch 
[mailto:moose-dev-boun...@iam.unibe.ch] De la part de Tudor Girba
Envoyé : vendredi 28 mars 2014 14:28
À : Moose-related development
Objet : [Moose-dev] Re: Fwd: [Pharo-dev] Font problem is still there

Hi,

This was discussed before both on the Moose and on the Pharo mailing list. We 
are loading explicitly an older version of Athens because we could not work at 
all with the one that came from Pharo, and nobody reacted at the time to the 
font issue:

GTImageSetupCommandLineHandler>>loadOlderAthensPackagesToCorrectTheFontCachingProblem
"
This is a workaround fir the bug described here:
https://pharo.fogbugz.com/f/cases/12777/Athens-font-cacheing-bug
"
Gofer new
smalltalkhubUser: 'Pharo' project: 'Pharo30';
package: 'Athens-Cairo' constraint: [ :version |
version author = 'MarcusDenker' and: [ version versionNumber = 51 ] ];
package: 'Athens-Core' constraint: [ :version |
version author = 'MarcusDenker' and: [ version versionNumber = 34 ] ];
load

Now it's great that you are looking at it. So, I now removed it from the setup 
and the image is now relying on the latest Pharo 3.0. The build is running now:
https://ci.inria.fr/moose/job/moose-5.0/1008/

Cheers,
Doru



On Fri, Mar 28, 2014 at 2:18 PM, Stéphane Ducasse 
mailto:stephane.duca...@inria.fr>> wrote:
Hi guys.

This is strange that moose is using a so old version of Athens.

Stef


Begin forwarded message:



From: Igor Stasenko mailto:siguc...@gmail.com>>
Subject: Re: [Pharo-dev] Font problem is still there
Date: 28 Mar 2014 14:03:17 GMT+1
To: Pharo Development List 
mailto:pharo-dev@lists.pharo.org>>
Reply-To: Pharo Development List 
mailto:pharo-dev@lists.pharo.org>>

so, i checked both in 4.9 and 5.0 Moose images on linux...
got weird results and sometimes crashes.
in 5.0 image the version is:
Athens-Cairo-MarcusDenker.51

- this one uses pretty old code, which renders text using 'toy' cairo api for 
text rendering.

in my working image, where i work every day it is:

Athens-Cairo-SvenVanCaekenberghe.64

and there's also couple important fixes since .51 as well as different font 
rendering code which no longer using toy api..
so, guys, if you want me to continue, please try using latest versions and 
report problems about it,
because it makes no sense to find a fix in something which outdated and thrown 
away many months ago.

Load the latest dev version of Athens from smalltalkhub (it is version 2.5)
ConfigurationOfAthens loadDevelopment.
try it out.


Here's what i got on latest fresh vanilla out of the box Pharo 3.0 image on 
linux system:



P.S. i am not saying that it is *impossible* that there is problems in new 
version, just asking you to report problems with that version,
not one which year(s) old.

--
Best regards,
Igor Stasenko.


___
Moose-dev mailing list
moose-...@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--
www.tudorgirba.com

"Every thing has its own flow"



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee