Re: [Pharo-dev] ConfigurationOfAthens-TudorGirba.87 does not load in latest 60

[stepharo]

I tried to see if it was the name usage but this is a problem I do not 
get :)


When I interrupted the program it was

open: fileName forWrite: writeMode
"Open the file with the given name. If writeMode is true, allow 
writing, otherwise open the file in read-only mode."

| f |
f := fileName asVmPathName.

fileID := StandardFileStream retryWithGC:[self primOpen: f 
writable: writeMode]


  here.

 until:[:id| id notNil]
forFileNamed: fileName.
fileID ifNil: [^ nil].  "allows sender to detect failure"
name := fileName.
self register.
rwmode := writeMode.
buffer1 := String new: 1.
self enableReadBuffering

and now going to bed.



Le 3/7/16 à 23:41, stepharo a écrit :

Hi doru

I'm not sure that you know that ConfigurationOfAthens-TudorGirba.87 
does not load in latest 60


It seems a problem with Object>>name usage (deprecation leading to an 
problem).


In Pharo 60 we have MarcusDenker.82 and the latest stable in the repo 
is ConifgurationOfAthens-TudorGirba.87


Stef

[Pharo-dev] ConfigurationOfAthens-TudorGirba.87 does not load in latest 60

[stepharo]

Hi doru

I'm not sure that you know that ConfigurationOfAthens-TudorGirba.87 does 
not load in latest 60


It seems a problem with Object>>name usage (deprecation leading to an 
problem).


In Pharo 60 we have MarcusDenker.82 and the latest stable in the repo is 
ConifgurationOfAthens-TudorGirba.87


Stef

Re: [Pharo-dev] AthensCairoSurface not getting garbage collected

[Nicolai Hess]

Hi Jeff,

if you use forms to paint on an AthensCairoCanvas, they are cached in the
CairoBackendCache,
can you try to flush that cache whith
CairoBackendCache flush.


2016-06-18 18:36 GMT+02:00 J.F. Rick :

> I'm using Athens rendering for my multi-touch applications on Pharo5. As
> part of that, I create a surface:
> surface := AthensCairoSurface extent: bounds extent asIntegerPoint.
>
> Though the object creating that surface is deleted, the surface sticks
> around. So, each time I run the app, I get another instance of
> AthensCairoSurface hanging around. That means all the forms stick around as
> well. So my image can quickly grow towards the 1GB size.
>
>  Is there anything I can do about that? Can I manually get the surface to
> delete itself?
>
> Cheers,
>
> Jeff
>

[Pharo-dev] GTDebugger - class variables

[Ben Coman]

I just noticed it seems class variables are not shown in Variables
pane of GTDebugger.  It confused me for a while, and I expect it would
be troubling for newcomers.  Is this due to copying the previous
Debugger functionality here, or some other design decision?Any
reason to not display class variables in the Variable pane?

cheers -ben

Re: [Pharo-dev] Bug in MailA

[Ben Coman]

On Sun, Jul 3, 2016 at 7:25 PM, Bernhard Pieber  wrote:
> Done!

Thanks Bernhard, but I can't find the issue in the tracker. Can you
paste a link?


On Sun, Jul 3, 2016 at 7:41 PM, Bernhard Pieber  wrote:
> I wonder about the process for fixes for Pharo 4.0? Is it the same? If I’d 
> put the equivalent fix into the Pharo40Inbox, would it be integrated?

I am not familiar with the release process, but apparently there is a
fair amount of manual work to do each release.  Typically it seems
each major release is followed by one minor point release about 6
months later.  So 4.0 is probably too far back for another release.

It would be good however if there was some community process to manage
fixes for very old releases.  Perhaps there could be a tag like
"Pharo4-hotfix" in Fogbugz, so users of their own accord could search
for community fixes contributed long after the main development focus
has moved on - to be used at own risk.  This might provide better
sustainability for older releases without drawing resources from the
latest version.  That is, Pharo 4.0 users would need to rely on review
by other Pharo 4.0 user to review and promote their fixes to "hotfix"
- but at least the Fogbugz facilitates the collaboration.  This might
also work for 5.0 fixes as a state between Work Needed and Closed Fix
Integrated while they are waiting to be rolled up into the point
release.

cheers -ben

>
> Cheers,
> Bernhard
>
>> Am 03.07.2016 um 08:46 schrieb stepharo :
>>
>> Thanks Bernhard
>>
>> - can you open a bug entry?
>>
>> - publish a slice? (press slice + bug number)
>>
>> Our integration tool and process work this way
>>
>> Stef
>>
>> Le 2/7/16 à 21:16, Bernhard Pieber a écrit :
>>> Hi,
>>>
>>> The following code goes into an endless loop:
>>> MailAddressParser addressesIn: 'romeo@verona.it‘
>>>
>>> It’s because of the ampersand. The fix is trivial, because the bug just was 
>>> a typo.
>>>
>>> Fix and test are in the Pharo50Inbox:
>>> Network-Mail-BernhardPieber.46.mcz
>>> Network-Tests-BernhardPieber.14.mcz
>
>

Re: [Pharo-dev] Bug in MailA

[Sven Van Caekenberghe]

Thank you.

> On 03 Jul 2016, at 13:25, Bernhard Pieber  wrote:
> 
> Done!
> 
> Cheers,
> Bernhard
> 
>> Am 03.07.2016 um 00:08 schrieb Ben Coman :
>> 
>> On Sun, Jul 3, 2016 at 3:16 AM, Bernhard Pieber  wrote:
>>> Hi,
>>> 
>>> The following code goes into an endless loop:
>>> MailAddressParser addressesIn: 'romeo@verona.it‘
>>> 
>>> It’s because of the ampersand. The fix is trivial, because the bug just was 
>>> a typo.
>>> 
>>> Fix and test are in the Pharo50Inbox:
>>> Network-Mail-BernhardPieber.46.mcz
>>> Network-Tests-BernhardPieber.14.mcz
>>> 
>>> Cheers,
>>> Bernhard
>> 
>> Thanks Bernhard.
>> Can you log an issue for it on
>> and submit this in Slice format.
>> Instructions at http://pharo.org/contribute-propose-fix
>> This makes it easier to review and the integration system only works
>> with Slices & Configurations.
>> 
>> cheers -ben
> 
> 

Re: [Pharo-dev] Bug in MailA

[Bernhard Pieber]

I wonder about the process for fixes for Pharo 4.0? Is it the same? If I’d put 
the equivalent fix into the Pharo40Inbox, would it be integrated?

Cheers,
Bernhard

> Am 03.07.2016 um 08:46 schrieb stepharo :
> 
> Thanks Bernhard
> 
> - can you open a bug entry?
> 
> - publish a slice? (press slice + bug number)
> 
> Our integration tool and process work this way
> 
> Stef
> 
> Le 2/7/16 à 21:16, Bernhard Pieber a écrit :
>> Hi,
>> 
>> The following code goes into an endless loop:
>> MailAddressParser addressesIn: 'romeo@verona.it‘
>> 
>> It’s because of the ampersand. The fix is trivial, because the bug just was 
>> a typo.
>> 
>> Fix and test are in the Pharo50Inbox:
>> Network-Mail-BernhardPieber.46.mcz
>> Network-Tests-BernhardPieber.14.mcz

Re: [Pharo-dev] Bug in MailA

[Bernhard Pieber]

Done!

Cheers,
Bernhard

> Am 03.07.2016 um 00:08 schrieb Ben Coman :
> 
> On Sun, Jul 3, 2016 at 3:16 AM, Bernhard Pieber  wrote:
>> Hi,
>> 
>> The following code goes into an endless loop:
>> MailAddressParser addressesIn: 'romeo@verona.it‘
>> 
>> It’s because of the ampersand. The fix is trivial, because the bug just was 
>> a typo.
>> 
>> Fix and test are in the Pharo50Inbox:
>> Network-Mail-BernhardPieber.46.mcz
>> Network-Tests-BernhardPieber.14.mcz
>> 
>> Cheers,
>> Bernhard
> 
> Thanks Bernhard.
> Can you log an issue for it on
> and submit this in Slice format.
> Instructions at http://pharo.org/contribute-propose-fix
> This makes it easier to review and the integration system only works
> with Slices & Configurations.
> 
> cheers -ben

Re: [Pharo-dev] Bug in MailA

[Ben Coman]

On Sun, Jul 3, 2016 at 6:08 AM, Ben Coman  wrote:
> On Sun, Jul 3, 2016 at 3:16 AM, Bernhard Pieber  wrote:
>> Hi,
>>
>> The following code goes into an endless loop:
>> MailAddressParser addressesIn: 'romeo@verona.it‘
>>
>> It’s because of the ampersand. The fix is trivial, because the bug just was 
>> a typo.
>>
>> Fix and test are in the Pharo50Inbox:
>> Network-Mail-BernhardPieber.46.mcz
>> Network-Tests-BernhardPieber.14.mcz
>>
>> Cheers,
>> Bernhard
>>
>>
>>
>
> Thanks Bernhard.
> Can you log an issue for it on
> and submit this in Slice format.
> Instructions at http://pharo.org/contribute-propose-fix
> This makes it easier to review and the integration system only works
> with Slices & Configurations.
>
> cheers -ben

P.S. Once your Slice is integrated, see instructions at the bottom of
[1] to get yourself added to the contributors page.
[1] http://pharo.org/about

cheers -ben

Re: [Pharo-dev] Bug in MailA

[stepharo]

Thanks Bernhard

- can you open a bug entry?

- publish a slice? (press slice + bug number)

Our integration tool and process work this way

Stef

Le 2/7/16 à 21:16, Bernhard Pieber a écrit :

Hi,

The following code goes into an endless loop:
MailAddressParser addressesIn: 'romeo@verona.it‘

It’s because of the ampersand. The fix is trivial, because the bug just was a 
typo.

Fix and test are in the Pharo50Inbox:
Network-Mail-BernhardPieber.46.mcz
Network-Tests-BernhardPieber.14.mcz

Cheers,
Bernhard