- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Loading Nautilus / Spec in 1.4

by Benjamin

On Jul 31, 2012, at 2:53 PM, Patrik Sundberg wrote: > On Tue, Jul 31, 2012 at 11:33 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Jul 31, 2012, at 11:47 AM, Benjamin wrote: > > > The last version loads in 1.4 if I remove the inst var duplication > > yes but for example we wanted to load versionner and this is not the client (the guy loading the other packages) that > have to know. > Anyway having duplicated instance variables is a bug so we should fix it. > > Try RPackageOrganizer initialize :) Ben > Btw, I quickly ran into problems - renaming a method throws DNU etc. Seems we're at an unfortunate point where 2.0 is at a point of instability (I run into metacello and announcement issues), and 1.4 doesn't play nicely with Nautilus. The bits I was hoping to use was nautilus and metacello and my code would use SystemAnnouncements :/ > > Perhaps I'll go with 1.4 and the old events for now. > > > Stef > > > > > > > Ben > > > > On Jul 31, 2012, at 9:47 AM, StÃ©phane Ducasse wrote: > > > >> > >> On Jul 31, 2012, at 4:14 AM, Benjamin wrote: > >> > >>> I will but when I publish a Spec version from 2.0, I can't know this kind of bug > >> > >> if you give me access to the spec repo I can do it. > >> The point is that for 1.4 do you want to publish the newest version? I would not I would simply take the old version > >> and make sure that it loads in 1.4 > >> > >> Stef > >>> > >>> Ben > >>> > >>> On Jul 30, 2012, at 11:15 PM, StÃ©phane Ducasse wrote: > >>> > >>>> ben > >>>> may be you should just fix the problem as I did and publish a stable version that load in 1.4 > >>>> This way people can load spec (the stable version for 1.4) in 1.4. > >>>> we can do it together. Now going to bed > >>>> > >>>> Stef > >>>> > >>>> On Jul 30, 2012, at 10:55 PM, Benjamin wrote: > >>>> > >>>>> NautilusRefactoring depends on Spec for the UI, that's all. > >>>>> > >>>>> But the problem is that in 2.0 a subclass can have an inst var named like ones of its superclasses ... > >>>>> > >>>>> Ben > >>>>> > >>>>> > >>>>> On Jul 30, 2012, at 10:22 PM, StÃ©phane Ducasse wrote: > >>>>> > >>>>>> > >>>>>> On Jul 30, 2012, at 9:54 PM, Benjamin wrote: > >>>>>> > >>>>>>> > >>>>>>> On Jul 30, 2012, at 7:22 PM, StÃ©phane Ducasse wrote: > >>>>>>> > >>>>>>>> Yes I got bitten by that today this is a problem you should remove the instance variable from the superclass then load and remove it from buttonModel > >>>>>>>> and add it to its superclass. > >>>>>>>> Now I suggest not to use nautilus for 1.4. > >>>>>>> > >>>>>>> Why ? > >>>>>> > >>>>>> Indeed nautilus is not base on spec. > >>>>>> Still let us focus on 2.0 > >>>>>> > >>>>>> Stef > >>>>>> > >>>>>>> > >>>>>>> Ben > >>>>>>> > >>>>>>>> > >>>>>>>> Stef > >>>>>>>> > >>>>>>>> On Jul 30, 2012, at 7:02 PM, Patrik Sundberg wrote: > >>>>>>>> > >>>>>>>>> Hi, > >>>>>>>>> > >>>>>>>>> Loading nautilus #stable in 1.4 I get: > >>>>>>>>> DuplicatedVariableError: helpHolder is already defined in AbstractBasicWidget > >>>>>>>>> > >>>>>>>>> Looks to come when loading the dependency Spec-Widgets-BenjaminVanRyseghem.48. > >>>>>>>>> > >>>>>>>>> Any ideas? > >>>>>>>>> > >>>>>>>>> I can provide more of the stack trace if it's useful (I'd assume so), but would like a pointer what the best way to get that info in an emailable format (not obvious to me how I can just copy-paste it). > >>>>>>>>> > >>>>>>>>> This is the summer release. > >>>>>>>>> > >>>>>>>>> Thanks, > >>>>>>>>> Patrik > >>>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>> > >>>> > >>> > >>> > >> > >> > > > > > > >

July 31, 2012

Re: [Pharo-project] Loading Nautilus / Spec in 1.4

by Patrik Sundberg

On Tue, Jul 31, 2012 at 11:33 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > > On Jul 31, 2012, at 11:47 AM, Benjamin wrote: > > > The last version loads in 1.4 if I remove the inst var duplication > > yes but for example we wanted to load versionner and this is not the > client (the guy loading the other packages) that > have to know. > Anyway having duplicated instance variables is a bug so we should fix it. > > Btw, I quickly ran into problems - renaming a method throws DNU etc. Seems we're at an unfortunate point where 2.0 is at a point of instability (I run into metacello and announcement issues), and 1.4 doesn't play nicely with Nautilus. The bits I was hoping to use was nautilus and metacello and my code would use SystemAnnouncements :/ Perhaps I'll go with 1.4 and the old events for now. > Stef > > > > > > > Ben > > > > On Jul 31, 2012, at 9:47 AM, StÃ©phane Ducasse wrote: > > > >> > >> On Jul 31, 2012, at 4:14 AM, Benjamin wrote: > >> > >>> I will but when I publish a Spec version from 2.0, I can't know this > kind of bug > >> > >> if you give me access to the spec repo I can do it. > >> The point is that for 1.4 do you want to publish the newest version? I > would not I would simply take the old version > >> and make sure that it loads in 1.4 > >> > >> Stef > >>> > >>> Ben > >>> > >>> On Jul 30, 2012, at 11:15 PM, StÃ©phane Ducasse wrote: > >>> > >>>> ben > >>>> may be you should just fix the problem as I did and publish a stable > version that load in 1.4 > >>>> This way people can load spec (the stable version for 1.4) in 1.4. > >>>> we can do it together. Now going to bed > >>>> > >>>> Stef > >>>> > >>>> On Jul 30, 2012, at 10:55 PM, Benjamin wrote: > >>>> > >>>>> NautilusRefactoring depends on Spec for the UI, that's all. > >>>>> > >>>>> But the problem is that in 2.0 a subclass can have an inst var named > like ones of its superclasses ... > >>>>> > >>>>> Ben > >>>>> > >>>>> > >>>>> On Jul 30, 2012, at 10:22 PM, StÃ©phane Ducasse wrote: > >>>>> > >>>>>> > >>>>>> On Jul 30, 2012, at 9:54 PM, Benjamin wrote: > >>>>>> > >>>>>>> > >>>>>>> On Jul 30, 2012, at 7:22 PM, StÃ©phane Ducasse wrote: > >>>>>>> > >>>>>>>> Yes I got bitten by that today this is a problem you should > remove the instance variable from the superclass then load and remove it > from buttonModel > >>>>>>>> and add it to its superclass. > >>>>>>>> Now I suggest not to use nautilus for 1.4. > >>>>>>> > >>>>>>> Why ? > >>>>>> > >>>>>> Indeed nautilus is not base on spec. > >>>>>> Still let us focus on 2.0 > >>>>>> > >>>>>> Stef > >>>>>> > >>>>>>> > >>>>>>> Ben > >>>>>>> > >>>>>>>> > >>>>>>>> Stef > >>>>>>>> > >>>>>>>> On Jul 30, 2012, at 7:02 PM, Patrik Sundberg wrote: > >>>>>>>> > >>>>>>>>> Hi, > >>>>>>>>> > >>>>>>>>> Loading nautilus #stable in 1.4 I get: > >>>>>>>>> DuplicatedVariableError: helpHolder is already defined in > AbstractBasicWidget > >>>>>>>>> > >>>>>>>>> Looks to come when loading the dependency > Spec-Widgets-BenjaminVanRyseghem.48. > >>>>>>>>> > >>>>>>>>> Any ideas? > >>>>>>>>> > >>>>>>>>> I can provide more of the stack trace if it's useful (I'd assume > so), but would like a pointer what the best way to get that info in an > emailable format (not obvious to me how I can just copy-paste it). > >>>>>>>>> > >>>>>>>>> This is the summer release. > >>>>>>>>> > >>>>>>>>> Thanks, > >>>>>>>>> Patrik > >>>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>> > >>>> > >>> > >>> > >> > >> > > > > > > >

July 31, 2012

[Pharo-project] [update 2.0] #20237

by Esteban Lorenzano

20237 ----- Issue 6451: New version of Spec http://code.google.com/p/pharo/issues/detail?id=6451 Issue 5661: Clean morphic EventHandler http://code.google.com/p/pharo/issues/detail?id=5661 Issue 6454: UndeclaredVariableWarning does not show location http://code.google.com/p/pharo/issues/detail?id=6454 Issue 6455: New version of CI http://code.google.com/p/pharo/issues/detail?id=6455 Issue 6471: Remove RMockSystemAnnouncer http://code.google.com/p/pharo/issues/detail?id=6471 Issue 6473: update comment in vm parameterAt: http://code.google.com/p/pharo/issues/detail?id=6473 Issue 6474: Improve senders http://code.google.com/p/pharo/issues/detail?id=6474

July 31, 2012

[Pharo-project] Possible FFI issue

by Diego Lont

Hi all, I am working with Friedrich on the ODBC issue, that the doubles aren't read correctly, and this is the point where I got by following the code: in the class: 'ByteArray' the function "doubleAt:" is implemented as a FFI-Kernel primitive. <primitive:'primitiveFFIDoubleAt' module:'<SqeakFFIPrims>'> In a version based on the seaside one click (Pharo v 1.3) this results in the correct double, but in the Pharo one click v1.4, this results in a double that is way too small. Writing a C program that makes the "same" api calls in ODBC also results in the correct values, although it gives an funny value for sqlTypLen (53). But we are kinda stuck here. Can someone give us the code of FFI, so we can continue debugging here, and possibly making a fix here? Also: does someone know what has changed between v1.3 and v1.4 in FFI, because both are loaded with the same Configuration. Thanks in advance for all the help, Diego Lont

July 31, 2012

Re: [Pharo-project] Loading Nautilus / Spec in 1.4

by StÃ©phane Ducasse

On Jul 31, 2012, at 11:47 AM, Benjamin wrote: > The last version loads in 1.4 if I remove the inst var duplication yes but for example we wanted to load versionner and this is not the client (the guy loading the other packages) that have to know. Anyway having duplicated instance variables is a bug so we should fix it. Are you at the lab? Stef > > > Ben > > On Jul 31, 2012, at 9:47 AM, StÃ©phane Ducasse wrote: > >> >> On Jul 31, 2012, at 4:14 AM, Benjamin wrote: >> >>> I will but when I publish a Spec version from 2.0, I can't know this kind of bug >> >> if you give me access to the spec repo I can do it. >> The point is that for 1.4 do you want to publish the newest version? I would not I would simply take the old version >> and make sure that it loads in 1.4 >> >> Stef >>> >>> Ben >>> >>> On Jul 30, 2012, at 11:15 PM, StÃ©phane Ducasse wrote: >>> >>>> ben >>>> may be you should just fix the problem as I did and publish a stable version that load in 1.4 >>>> This way people can load spec (the stable version for 1.4) in 1.4. >>>> we can do it together. Now going to bed >>>> >>>> Stef >>>> >>>> On Jul 30, 2012, at 10:55 PM, Benjamin wrote: >>>> >>>>> NautilusRefactoring depends on Spec for the UI, that's all. >>>>> >>>>> But the problem is that in 2.0 a subclass can have an inst var named like ones of its superclasses ... >>>>> >>>>> Ben >>>>> >>>>> >>>>> On Jul 30, 2012, at 10:22 PM, StÃ©phane Ducasse wrote: >>>>> >>>>>> >>>>>> On Jul 30, 2012, at 9:54 PM, Benjamin wrote: >>>>>> >>>>>>> >>>>>>> On Jul 30, 2012, at 7:22 PM, StÃ©phane Ducasse wrote: >>>>>>> >>>>>>>> Yes I got bitten by that today this is a problem you should remove the instance variable from the superclass then load and remove it from buttonModel >>>>>>>> and add it to its superclass. >>>>>>>> Now I suggest not to use nautilus for 1.4. >>>>>>> >>>>>>> Why ? >>>>>> >>>>>> Indeed nautilus is not base on spec. >>>>>> Still let us focus on 2.0 >>>>>> >>>>>> Stef >>>>>> >>>>>>> >>>>>>> Ben >>>>>>> >>>>>>>> >>>>>>>> Stef >>>>>>>> >>>>>>>> On Jul 30, 2012, at 7:02 PM, Patrik Sundberg wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> Loading nautilus #stable in 1.4 I get: >>>>>>>>> DuplicatedVariableError: helpHolder is already defined in AbstractBasicWidget >>>>>>>>> >>>>>>>>> Looks to come when loading the dependency Spec-Widgets-BenjaminVanRyseghem.48. >>>>>>>>> >>>>>>>>> Any ideas? >>>>>>>>> >>>>>>>>> I can provide more of the stack trace if it's useful (I'd assume so), but would like a pointer what the best way to get that info in an emailable format (not obvious to me how I can just copy-paste it). >>>>>>>>> >>>>>>>>> This is the summer release. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Patrik >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >

July 31, 2012

Re: [Pharo-project] Loading Nautilus / Spec in 1.4

by Patrik Sundberg

On Tue, Jul 31, 2012 at 10:47 AM, Benjamin < benjamin.vanryseghem.pharo(a)gmail.com> wrote: > The last version loads in 1.4 if I remove the inst var duplication > > Yep, just built my image 1.4 image with Nautilus cleanly. Thanks!

July 31, 2012

Re: [Pharo-project] Loading Nautilus / Spec in 1.4

by Benjamin

The last version loads in 1.4 if I remove the inst var duplication Ben On Jul 31, 2012, at 9:47 AM, StÃ©phane Ducasse wrote: > > On Jul 31, 2012, at 4:14 AM, Benjamin wrote: > >> I will but when I publish a Spec version from 2.0, I can't know this kind of bug > > if you give me access to the spec repo I can do it. > The point is that for 1.4 do you want to publish the newest version? I would not I would simply take the old version > and make sure that it loads in 1.4 > > Stef >> >> Ben >> >> On Jul 30, 2012, at 11:15 PM, StÃ©phane Ducasse wrote: >> >>> ben >>> may be you should just fix the problem as I did and publish a stable version that load in 1.4 >>> This way people can load spec (the stable version for 1.4) in 1.4. >>> we can do it together. Now going to bed >>> >>> Stef >>> >>> On Jul 30, 2012, at 10:55 PM, Benjamin wrote: >>> >>>> NautilusRefactoring depends on Spec for the UI, that's all. >>>> >>>> But the problem is that in 2.0 a subclass can have an inst var named like ones of its superclasses ... >>>> >>>> Ben >>>> >>>> >>>> On Jul 30, 2012, at 10:22 PM, StÃ©phane Ducasse wrote: >>>> >>>>> >>>>> On Jul 30, 2012, at 9:54 PM, Benjamin wrote: >>>>> >>>>>> >>>>>> On Jul 30, 2012, at 7:22 PM, StÃ©phane Ducasse wrote: >>>>>> >>>>>>> Yes I got bitten by that today this is a problem you should remove the instance variable from the superclass then load and remove it from buttonModel >>>>>>> and add it to its superclass. >>>>>>> Now I suggest not to use nautilus for 1.4. >>>>>> >>>>>> Why ? >>>>> >>>>> Indeed nautilus is not base on spec. >>>>> Still let us focus on 2.0 >>>>> >>>>> Stef >>>>> >>>>>> >>>>>> Ben >>>>>> >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> On Jul 30, 2012, at 7:02 PM, Patrik Sundberg wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Loading nautilus #stable in 1.4 I get: >>>>>>>> DuplicatedVariableError: helpHolder is already defined in AbstractBasicWidget >>>>>>>> >>>>>>>> Looks to come when loading the dependency Spec-Widgets-BenjaminVanRyseghem.48. >>>>>>>> >>>>>>>> Any ideas? >>>>>>>> >>>>>>>> I can provide more of the stack trace if it's useful (I'd assume so), but would like a pointer what the best way to get that info in an emailable format (not obvious to me how I can just copy-paste it). >>>>>>>> >>>>>>>> This is the summer release. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Patrik >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >

July 31, 2012

Re: [Pharo-project] Loading Nautilus / Spec in 1.4

by StÃ©phane Ducasse

On Jul 31, 2012, at 4:14 AM, Benjamin wrote: > I will but when I publish a Spec version from 2.0, I can't know this kind of bug if you give me access to the spec repo I can do it. The point is that for 1.4 do you want to publish the newest version? I would not I would simply take the old version and make sure that it loads in 1.4 Stef > > Ben > > On Jul 30, 2012, at 11:15 PM, StÃ©phane Ducasse wrote: > >> ben >> may be you should just fix the problem as I did and publish a stable version that load in 1.4 >> This way people can load spec (the stable version for 1.4) in 1.4. >> we can do it together. Now going to bed >> >> Stef >> >> On Jul 30, 2012, at 10:55 PM, Benjamin wrote: >> >>> NautilusRefactoring depends on Spec for the UI, that's all. >>> >>> But the problem is that in 2.0 a subclass can have an inst var named like ones of its superclasses ... >>> >>> Ben >>> >>> >>> On Jul 30, 2012, at 10:22 PM, StÃ©phane Ducasse wrote: >>> >>>> >>>> On Jul 30, 2012, at 9:54 PM, Benjamin wrote: >>>> >>>>> >>>>> On Jul 30, 2012, at 7:22 PM, StÃ©phane Ducasse wrote: >>>>> >>>>>> Yes I got bitten by that today this is a problem you should remove the instance variable from the superclass then load and remove it from buttonModel >>>>>> and add it to its superclass. >>>>>> Now I suggest not to use nautilus for 1.4. >>>>> >>>>> Why ? >>>> >>>> Indeed nautilus is not base on spec. >>>> Still let us focus on 2.0 >>>> >>>> Stef >>>> >>>>> >>>>> Ben >>>>> >>>>>> >>>>>> Stef >>>>>> >>>>>> On Jul 30, 2012, at 7:02 PM, Patrik Sundberg wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Loading nautilus #stable in 1.4 I get: >>>>>>> DuplicatedVariableError: helpHolder is already defined in AbstractBasicWidget >>>>>>> >>>>>>> Looks to come when loading the dependency Spec-Widgets-BenjaminVanRyseghem.48. >>>>>>> >>>>>>> Any ideas? >>>>>>> >>>>>>> I can provide more of the stack trace if it's useful (I'd assume so), but would like a pointer what the best way to get that info in an emailable format (not obvious to me how I can just copy-paste it). >>>>>>> >>>>>>> This is the summer release. >>>>>>> >>>>>>> Thanks, >>>>>>> Patrik >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >

July 31, 2012

Re: [Pharo-project] Loading Nautilus / Spec in 1.4

by Benjamin

I will but when I publish a Spec version from 2.0, I can't know this kind of bug Ben On Jul 30, 2012, at 11:15 PM, StÃ©phane Ducasse wrote: > ben > may be you should just fix the problem as I did and publish a stable version that load in 1.4 > This way people can load spec (the stable version for 1.4) in 1.4. > we can do it together. Now going to bed > > Stef > > On Jul 30, 2012, at 10:55 PM, Benjamin wrote: > >> NautilusRefactoring depends on Spec for the UI, that's all. >> >> But the problem is that in 2.0 a subclass can have an inst var named like ones of its superclasses ... >> >> Ben >> >> >> On Jul 30, 2012, at 10:22 PM, StÃ©phane Ducasse wrote: >> >>> >>> On Jul 30, 2012, at 9:54 PM, Benjamin wrote: >>> >>>> >>>> On Jul 30, 2012, at 7:22 PM, StÃ©phane Ducasse wrote: >>>> >>>>> Yes I got bitten by that today this is a problem you should remove the instance variable from the superclass then load and remove it from buttonModel >>>>> and add it to its superclass. >>>>> Now I suggest not to use nautilus for 1.4. >>>> >>>> Why ? >>> >>> Indeed nautilus is not base on spec. >>> Still let us focus on 2.0 >>> >>> Stef >>> >>>> >>>> Ben >>>> >>>>> >>>>> Stef >>>>> >>>>> On Jul 30, 2012, at 7:02 PM, Patrik Sundberg wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Loading nautilus #stable in 1.4 I get: >>>>>> DuplicatedVariableError: helpHolder is already defined in AbstractBasicWidget >>>>>> >>>>>> Looks to come when loading the dependency Spec-Widgets-BenjaminVanRyseghem.48. >>>>>> >>>>>> Any ideas? >>>>>> >>>>>> I can provide more of the stack trace if it's useful (I'd assume so), but would like a pointer what the best way to get that info in an emailable format (not obvious to me how I can just copy-paste it). >>>>>> >>>>>> This is the summer release. >>>>>> >>>>>> Thanks, >>>>>> Patrik >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >

July 31, 2012

Re: [Pharo-project] Loading Nautilus / Spec in 1.4

by Patrik Sundberg

it'd be appreciated, I think I'll have to stick to 1.4 along side 2.0 until I am more able to fix things in 2.0 myself. seems a waste to not learn cautious for me as I get started though since it's the future (given I'm starting from scratch). thanks for the workaround, ties me over but I'm automating my image building so manual steps I'm trying to avoid completely hence updated package would be great. On Jul 30, 2012 10:16 PM, "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> wrote: > ben > may be you should just fix the problem as I did and publish a stable > version that load in 1.4 > This way people can load spec (the stable version for 1.4) in 1.4. > we can do it together. Now going to bed > > Stef > > On Jul 30, 2012, at 10:55 PM, Benjamin wrote: > > > NautilusRefactoring depends on Spec for the UI, that's all. > > > > But the problem is that in 2.0 a subclass can have an inst var named > like ones of its superclasses ... > > > > Ben > > > > > > On Jul 30, 2012, at 10:22 PM, StÃ©phane Ducasse wrote: > > > >> > >> On Jul 30, 2012, at 9:54 PM, Benjamin wrote: > >> > >>> > >>> On Jul 30, 2012, at 7:22 PM, StÃ©phane Ducasse wrote: > >>> > >>>> Yes I got bitten by that today this is a problem you should remove > the instance variable from the superclass then load and remove it from > buttonModel > >>>> and add it to its superclass. > >>>> Now I suggest not to use nautilus for 1.4. > >>> > >>> Why ? > >> > >> Indeed nautilus is not base on spec. > >> Still let us focus on 2.0 > >> > >> Stef > >> > >>> > >>> Ben > >>> > >>>> > >>>> Stef > >>>> > >>>> On Jul 30, 2012, at 7:02 PM, Patrik Sundberg wrote: > >>>> > >>>>> Hi, > >>>>> > >>>>> Loading nautilus #stable in 1.4 I get: > >>>>> DuplicatedVariableError: helpHolder is already defined in > AbstractBasicWidget > >>>>> > >>>>> Looks to come when loading the dependency > Spec-Widgets-BenjaminVanRyseghem.48. > >>>>> > >>>>> Any ideas? > >>>>> > >>>>> I can provide more of the stack trace if it's useful (I'd assume > so), but would like a pointer what the best way to get that info in an > emailable format (not obvious to me how I can just copy-paste it). > >>>>> > >>>>> This is the summer release. > >>>>> > >>>>> Thanks, > >>>>> Patrik > >>>>> > >>>> > >>>> > >>> > >>> > >> > >> > > > > > > >

July 30, 2012