[Pharo-project] Loading Nautilus / Spec in 1.4
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
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. 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
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 ? 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
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
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
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
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@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
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
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
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
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
On Tue, Jul 31, 2012 at 11:33 AM, Stéphane Ducasse < stephane.ducasse@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
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@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
participants (3)
-
Benjamin -
Patrik Sundberg -
Stéphane Ducasse