Hi,
I've created the attached package on Mac (that library isn't finished yet) and attempted to load it into images on Windows. Loading the parcel seems to be successful. Unfortunately the image gets into an endless loop of opening exceptions notifiers with an MNU ( #from: ) if I use e.g. the browser. For example, try to create a new protocol in some class (not necessarily from this package) and the endless loop starts. I've absolutely no idea what's going on and debugging seems to be impossible. Even stranger, on Mac nothing like this happens. Please help! THX, Steffen _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc Archiv.zip (41K) Download Attachment |
Hi,
has anybody some ideas how I can investigate what's going on? Regards, Steffen Am 20.12.2010, 17:10 Uhr, schrieb Steffen Märcker <[hidden email]>: > Hi, > > I've created the attached package on Mac (that library isn't finished > yet) > and attempted to load it into images on Windows. Loading the parcel seems > to be successful. Unfortunately the image gets into an endless loop of > opening exceptions notifiers with an MNU ( #from: ) if I use e.g. the > browser. For example, try to create a new protocol in some class (not > necessarily from this package) and the endless loop starts. > I've absolutely no idea what's going on and debugging seems to be > impossible. Even stranger, on Mac nothing like this happens. > > Please help! > > THX, > Steffen vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Steffen,
I'd suggest, to create a source file-In from the parcel & file-in method by method - each time creating the activities to raise the error -to find the cause. Kind regards, L. Willmann ----- Original Message ----- From: "Steffen Märcker" <[hidden email]> To: "vwnc" <[hidden email]>; "Steffen Märcker" <[hidden email]> Sent: Tuesday, December 21, 2010 9:55 AM Subject: Re: [vwnc] MNU in tools after loading parcel Hi, has anybody some ideas how I can investigate what's going on? Regards, Steffen Am 20.12.2010, 17:10 Uhr, schrieb Steffen Märcker <[hidden email]>: > Hi, > > I've created the attached package on Mac (that library isn't finished > yet) > and attempted to load it into images on Windows. Loading the parcel seems > to be successful. Unfortunately the image gets into an endless loop of > opening exceptions notifiers with an MNU ( #from: ) if I use e.g. the > browser. For example, try to create a new protocol in some class (not > necessarily from this package) and the endless loop starts. > I've absolutely no idea what's going on and debugging seems to be > impossible. Even stranger, on Mac nothing like this happens. > > Please help! > > THX, > Steffen vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Hi,
I've got a step further. (Thanks to L. William!) The problems are caused by the following class I've defined: Class Smalltalk.Pattern Superclass: Core.Object ... It seems to interfere with either Graphics.Pattern or XML.Pattern on Windows. This seems odd to me because on Mac everything works smoothly. Is this a know bug or a limitation on Windows? Regards, Steffen Am 21.12.2010, 10:07 Uhr, schrieb Linus Willmann <[hidden email]>: > Steffen, > > I'd suggest, to create a source file-In from the parcel & file-in method > by method - each time creating the activities to raise the error -to > find the cause. > > Kind regards, > L. Willmann > > ----- Original Message ----- From: "Steffen Märcker" <[hidden email]> > To: "vwnc" <[hidden email]>; "Steffen Märcker" <[hidden email]> > Sent: Tuesday, December 21, 2010 9:55 AM > Subject: Re: [vwnc] MNU in tools after loading parcel > > > Hi, > > has anybody some ideas how I can investigate what's going on? > > Regards, > Steffen > > Am 20.12.2010, 17:10 Uhr, schrieb Steffen Märcker <[hidden email]>: > >> Hi, >> >> I've created the attached package on Mac (that library isn't finished >> yet) >> and attempted to load it into images on Windows. Loading the parcel >> seems >> to be successful. Unfortunately the image gets into an endless loop of >> opening exceptions notifiers with an MNU ( #from: ) if I use e.g. the >> browser. For example, try to create a new protocol in some class (not >> necessarily from this package) and the endless loop starts. >> I've absolutely no idea what's going on and debugging seems to be >> impossible. Even stranger, on Mac nothing like this happens. >> >> Please help! >> >> THX, >> Steffen > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
I tried on Windows 7:
- If I create the Pattern class as a subclass of Object in my private namespace there is no problem - If I create the Pattern class as a subclass of Object in the Smalltalk namespace I get on parcel publishing the infinite number of "MNU: #from:" as you are seeing on parcel load -----Ursprüngliche Nachricht----- Von: [hidden email] [mailto:[hidden email]] Im Auftrag von Steffen Märcker Gesendet: Dienstag, 21. Dezember 2010 11:54 An: vwnc Betreff: Re: [vwnc] MNU in tools after loading parcel Hi, I've got a step further. (Thanks to L. William!) The problems are caused by the following class I've defined: Class Smalltalk.Pattern Superclass: Core.Object ... It seems to interfere with either Graphics.Pattern or XML.Pattern on Windows. This seems odd to me because on Mac everything works smoothly. Is this a know bug or a limitation on Windows? Regards, Steffen Am 21.12.2010, 10:07 Uhr, schrieb Linus Willmann <[hidden email]>: > Steffen, > > I'd suggest, to create a source file-In from the parcel & file-in method > by method - each time creating the activities to raise the error -to > find the cause. > > Kind regards, > L. Willmann > > ----- Original Message ----- From: "Steffen Märcker" <[hidden email]> > To: "vwnc" <[hidden email]>; "Steffen Märcker" <[hidden email]> > Sent: Tuesday, December 21, 2010 9:55 AM > Subject: Re: [vwnc] MNU in tools after loading parcel > > > Hi, > > has anybody some ideas how I can investigate what's going on? > > Regards, > Steffen > > Am 20.12.2010, 17:10 Uhr, schrieb Steffen Märcker <[hidden email]>: > >> Hi, >> >> I've created the attached package on Mac (that library isn't finished >> yet) >> and attempted to load it into images on Windows. Loading the parcel >> seems >> to be successful. Unfortunately the image gets into an endless loop of >> opening exceptions notifiers with an MNU ( #from: ) if I use e.g. the >> browser. For example, try to create a new protocol in some class (not >> necessarily from this package) and the endless loop starts. >> I've absolutely no idea what's going on and debugging seems to be >> impossible. Even stranger, on Mac nothing like this happens. >> >> Please help! >> >> THX, >> Steffen > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Ok,
one step further I see several references to Graphics.Image which are not prefixed with the namespace 'Graphics'. I think the get resolved to my class at it doesn't reside inside a namespace other than 'Smalltalk'. If this observation is correct I suggest to correct the references in the base image in order to prevent those problems in general. Any opinions on this? Regards, Steffen Am 21.12.2010, 12:08 Uhr, schrieb Nowak, Helge <[hidden email]>: > I tried on Windows 7: > - If I create the Pattern class as a subclass of Object in my private > namespace there is no problem > - If I create the Pattern class as a subclass of Object in the Smalltalk > namespace I get on parcel publishing the infinite number of "MNU: > #from:" as you are seeing on parcel load > > > -----Ursprüngliche Nachricht----- > Von: [hidden email] [mailto:[hidden email]] Im > Auftrag von Steffen Märcker > Gesendet: Dienstag, 21. Dezember 2010 11:54 > An: vwnc > Betreff: Re: [vwnc] MNU in tools after loading parcel > > Hi, > > I've got a step further. (Thanks to L. William!) The problems are caused > by the following class I've defined: > > Class Smalltalk.Pattern > Superclass: Core.Object > ... > > It seems to interfere with either Graphics.Pattern or XML.Pattern on > Windows. This seems odd to me because on Mac everything works smoothly. > Is > this a know bug or a limitation on Windows? > > Regards, Steffen > > > > Am 21.12.2010, 10:07 Uhr, schrieb Linus Willmann <[hidden email]>: > >> Steffen, >> >> I'd suggest, to create a source file-In from the parcel & file-in method >> by method - each time creating the activities to raise the error -to >> find the cause. >> >> Kind regards, >> L. Willmann >> >> ----- Original Message ----- From: "Steffen Märcker" <[hidden email]> >> To: "vwnc" <[hidden email]>; "Steffen Märcker" <[hidden email]> >> Sent: Tuesday, December 21, 2010 9:55 AM >> Subject: Re: [vwnc] MNU in tools after loading parcel >> >> >> Hi, >> >> has anybody some ideas how I can investigate what's going on? >> >> Regards, >> Steffen >> >> Am 20.12.2010, 17:10 Uhr, schrieb Steffen Märcker <[hidden email]>: >> >>> Hi, >>> >>> I've created the attached package on Mac (that library isn't finished >>> yet) >>> and attempted to load it into images on Windows. Loading the parcel >>> seems >>> to be successful. Unfortunately the image gets into an endless loop of >>> opening exceptions notifiers with an MNU ( #from: ) if I use e.g. the >>> browser. For example, try to create a new protocol in some class (not >>> necessarily from this package) and the endless loop starts. >>> I've absolutely no idea what's going on and debugging seems to be >>> impossible. Even stranger, on Mac nothing like this happens. >>> >>> Please help! >>> >>> THX, >>> Steffen >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Sorry, my fault. I mean Graphics.Pattern, of course. -_-'
Steffen > Ok, > > one step further I see several references to Graphics.Image which are not > prefixed with the namespace 'Graphics'. I think the get resolved to my > class at it doesn't reside inside a namespace other than 'Smalltalk'. If > this observation is correct I suggest to correct the references in the > base image in order to prevent those problems in general. > Any opinions on this? > > Regards, Steffen > > > Am 21.12.2010, 12:08 Uhr, schrieb Nowak, Helge <[hidden email]>: > >> I tried on Windows 7: >> - If I create the Pattern class as a subclass of Object in my private >> namespace there is no problem >> - If I create the Pattern class as a subclass of Object in the Smalltalk >> namespace I get on parcel publishing the infinite number of "MNU: >> #from:" as you are seeing on parcel load >> >> >> -----Ursprüngliche Nachricht----- >> Von: [hidden email] [mailto:[hidden email]] Im >> Auftrag von Steffen Märcker >> Gesendet: Dienstag, 21. Dezember 2010 11:54 >> An: vwnc >> Betreff: Re: [vwnc] MNU in tools after loading parcel >> >> Hi, >> >> I've got a step further. (Thanks to L. William!) The problems are caused >> by the following class I've defined: >> >> Class Smalltalk.Pattern >> Superclass: Core.Object >> ... >> >> It seems to interfere with either Graphics.Pattern or XML.Pattern on >> Windows. This seems odd to me because on Mac everything works smoothly. >> Is >> this a know bug or a limitation on Windows? >> >> Regards, Steffen >> >> >> >> Am 21.12.2010, 10:07 Uhr, schrieb Linus Willmann <[hidden email]>: >> >>> Steffen, >>> >>> I'd suggest, to create a source file-In from the parcel & file-in >>> method >>> by method - each time creating the activities to raise the error -to >>> find the cause. >>> >>> Kind regards, >>> L. Willmann >>> >>> ----- Original Message ----- From: "Steffen Märcker" <[hidden email]> >>> To: "vwnc" <[hidden email]>; "Steffen Märcker" <[hidden email]> >>> Sent: Tuesday, December 21, 2010 9:55 AM >>> Subject: Re: [vwnc] MNU in tools after loading parcel >>> >>> >>> Hi, >>> >>> has anybody some ideas how I can investigate what's going on? >>> >>> Regards, >>> Steffen >>> >>> Am 20.12.2010, 17:10 Uhr, schrieb Steffen Märcker <[hidden email]>: >>> >>>> Hi, >>>> >>>> I've created the attached package on Mac (that library isn't finished >>>> yet) >>>> and attempted to load it into images on Windows. Loading the parcel >>>> seems >>>> to be successful. Unfortunately the image gets into an endless loop of >>>> opening exceptions notifiers with an MNU ( #from: ) if I use e.g. the >>>> browser. For example, try to create a new protocol in some class (not >>>> necessarily from this package) and the endless loop starts. >>>> I've absolutely no idea what's going on and debugging seems to be >>>> impossible. Even stranger, on Mac nothing like this happens. >>>> >>>> Please help! >>>> >>>> THX, >>>> Steffen >>> _______________________________________________ >>> vwnc mailing list >>> [hidden email] >>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >>> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
I think part of the point of the namespace mechanism is that if you're
introducing classes of your own which have names the same as those in basic Smalltalk, that you can put them in your own namespaces and they won't conflict with the base. The design which took everything out of the Smalltalk namespace and put it into sub-namespaces which were then all imported into Smalltalk so they might as well have been there anyway is questionable. But I certainly wouldn't want to see all references to base system classes need to be prefixed. In general, I'd like to avoid having to use prefixes. Why wouldn't you just create your class in an application namespace? I suspect the reason you see that on one platform but not on another might be because the order of lookup is not strictly deterministic, so you might get references resolving to one class on one platform and another on another. But that's complete speculation on my part, and I'm not sure what would make the order actually change if you just moved an image from one platform to another. On 2010-12-21 8:16 AM, Steffen Märcker wrote: > Sorry, my fault. I mean Graphics.Pattern, of course. -_-' > > Steffen > > >> Ok, >> >> one step further I see several references to Graphics.Image which are not >> prefixed with the namespace 'Graphics'. I think the get resolved to my >> class at it doesn't reside inside a namespace other than 'Smalltalk'. If >> this observation is correct I suggest to correct the references in the >> base image in order to prevent those problems in general. >> Any opinions on this? >> >> Regards, Steffen >> >> >> Am 21.12.2010, 12:08 Uhr, schrieb Nowak, Helge<[hidden email]>: >> >>> I tried on Windows 7: >>> - If I create the Pattern class as a subclass of Object in my private >>> namespace there is no problem >>> - If I create the Pattern class as a subclass of Object in the Smalltalk >>> namespace I get on parcel publishing the infinite number of "MNU: >>> #from:" as you are seeing on parcel load >>> >>> >>> -----Ursprüngliche Nachricht----- >>> Von: [hidden email] [mailto:[hidden email]] Im >>> Auftrag von Steffen Märcker >>> Gesendet: Dienstag, 21. Dezember 2010 11:54 >>> An: vwnc >>> Betreff: Re: [vwnc] MNU in tools after loading parcel >>> >>> Hi, >>> >>> I've got a step further. (Thanks to L. William!) The problems are caused >>> by the following class I've defined: >>> >>> Class Smalltalk.Pattern >>> Superclass: Core.Object >>> ... >>> >>> It seems to interfere with either Graphics.Pattern or XML.Pattern on >>> Windows. This seems odd to me because on Mac everything works smoothly. >>> Is >>> this a know bug or a limitation on Windows? >>> >>> Regards, Steffen >>> >>> >>> >>> Am 21.12.2010, 10:07 Uhr, schrieb Linus Willmann<[hidden email]>: >>> >>>> Steffen, >>>> >>>> I'd suggest, to create a source file-In from the parcel& file-in >>>> method >>>> by method - each time creating the activities to raise the error -to >>>> find the cause. >>>> >>>> Kind regards, >>>> L. Willmann >>>> >>>> ----- Original Message ----- From: "Steffen Märcker"<[hidden email]> >>>> To: "vwnc"<[hidden email]>; "Steffen Märcker"<[hidden email]> >>>> Sent: Tuesday, December 21, 2010 9:55 AM >>>> Subject: Re: [vwnc] MNU in tools after loading parcel >>>> >>>> >>>> Hi, >>>> >>>> has anybody some ideas how I can investigate what's going on? >>>> >>>> Regards, >>>> Steffen >>>> >>>> Am 20.12.2010, 17:10 Uhr, schrieb Steffen Märcker<[hidden email]>: >>>> >>>>> Hi, >>>>> >>>>> I've created the attached package on Mac (that library isn't finished >>>>> yet) >>>>> and attempted to load it into images on Windows. Loading the parcel >>>>> seems >>>>> to be successful. Unfortunately the image gets into an endless loop of >>>>> opening exceptions notifiers with an MNU ( #from: ) if I use e.g. the >>>>> browser. For example, try to create a new protocol in some class (not >>>>> necessarily from this package) and the endless loop starts. >>>>> I've absolutely no idea what's going on and debugging seems to be >>>>> impossible. Even stranger, on Mac nothing like this happens. >>>>> >>>>> Please help! >>>>> >>>>> THX, >>>>> Steffen >>>> _______________________________________________ >>>> vwnc mailing list >>>> [hidden email] >>>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >>>> >>> _______________________________________________ >>> vwnc mailing list >>> [hidden email] >>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc -- Alan Knight [|], Engineering Manager, Cincom Smalltalk [hidden email] [hidden email] http://www.cincom.com/smalltalk _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
>From my point of view you can never be sure that at any point in time the System will not have a class that has the same name as yours. Therefore I'd call it a good practice to have all my classes in my namespace.
Cheers Helge -----Ursprüngliche Nachricht----- Von: [hidden email] [mailto:[hidden email]] Im Auftrag von Alan Knight Gesendet: Dienstag, 21. Dezember 2010 16:37 An: [hidden email] Betreff: Re: [vwnc] MNU in tools after loading parcel I think part of the point of the namespace mechanism is that if you're introducing classes of your own which have names the same as those in basic Smalltalk, that you can put them in your own namespaces and they won't conflict with the base. The design which took everything out of the Smalltalk namespace and put it into sub-namespaces which were then all imported into Smalltalk so they might as well have been there anyway is questionable. But I certainly wouldn't want to see all references to base system classes need to be prefixed. In general, I'd like to avoid having to use prefixes. Why wouldn't you just create your class in an application namespace? I suspect the reason you see that on one platform but not on another might be because the order of lookup is not strictly deterministic, so you might get references resolving to one class on one platform and another on another. But that's complete speculation on my part, and I'm not sure what would make the order actually change if you just moved an image from one platform to another. On 2010-12-21 8:16 AM, Steffen Märcker wrote: > Sorry, my fault. I mean Graphics.Pattern, of course. -_-' > > Steffen > > >> Ok, >> >> one step further I see several references to Graphics.Image which are not >> prefixed with the namespace 'Graphics'. I think the get resolved to my >> class at it doesn't reside inside a namespace other than 'Smalltalk'. If >> this observation is correct I suggest to correct the references in the >> base image in order to prevent those problems in general. >> Any opinions on this? >> >> Regards, Steffen >> >> >> Am 21.12.2010, 12:08 Uhr, schrieb Nowak, Helge<[hidden email]>: >> >>> I tried on Windows 7: >>> - If I create the Pattern class as a subclass of Object in my private >>> namespace there is no problem >>> - If I create the Pattern class as a subclass of Object in the Smalltalk >>> namespace I get on parcel publishing the infinite number of "MNU: >>> #from:" as you are seeing on parcel load >>> >>> >>> -----Ursprüngliche Nachricht----- >>> Von: [hidden email] [mailto:[hidden email]] Im >>> Auftrag von Steffen Märcker >>> Gesendet: Dienstag, 21. Dezember 2010 11:54 >>> An: vwnc >>> Betreff: Re: [vwnc] MNU in tools after loading parcel >>> >>> Hi, >>> >>> I've got a step further. (Thanks to L. William!) The problems are caused >>> by the following class I've defined: >>> >>> Class Smalltalk.Pattern >>> Superclass: Core.Object >>> ... >>> >>> It seems to interfere with either Graphics.Pattern or XML.Pattern on >>> Windows. This seems odd to me because on Mac everything works smoothly. >>> Is >>> this a know bug or a limitation on Windows? >>> >>> Regards, Steffen >>> >>> >>> >>> Am 21.12.2010, 10:07 Uhr, schrieb Linus Willmann<[hidden email]>: >>> >>>> Steffen, >>>> >>>> I'd suggest, to create a source file-In from the parcel& file-in >>>> method >>>> by method - each time creating the activities to raise the error -to >>>> find the cause. >>>> >>>> Kind regards, >>>> L. Willmann >>>> >>>> ----- Original Message ----- From: "Steffen Märcker"<[hidden email]> >>>> To: "vwnc"<[hidden email]>; "Steffen Märcker"<[hidden email]> >>>> Sent: Tuesday, December 21, 2010 9:55 AM >>>> Subject: Re: [vwnc] MNU in tools after loading parcel >>>> >>>> >>>> Hi, >>>> >>>> has anybody some ideas how I can investigate what's going on? >>>> >>>> Regards, >>>> Steffen >>>> >>>> Am 20.12.2010, 17:10 Uhr, schrieb Steffen Märcker<[hidden email]>: >>>> >>>>> Hi, >>>>> >>>>> I've created the attached package on Mac (that library isn't finished >>>>> yet) >>>>> and attempted to load it into images on Windows. Loading the parcel >>>>> seems >>>>> to be successful. Unfortunately the image gets into an endless loop of >>>>> opening exceptions notifiers with an MNU ( #from: ) if I use e.g. the >>>>> browser. For example, try to create a new protocol in some class (not >>>>> necessarily from this package) and the endless loop starts. >>>>> I've absolutely no idea what's going on and debugging seems to be >>>>> impossible. Even stranger, on Mac nothing like this happens. >>>>> >>>>> Please help! >>>>> >>>>> THX, >>>>> Steffen >>>> _______________________________________________ >>>> vwnc mailing list >>>> [hidden email] >>>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >>>> >>> _______________________________________________ >>> vwnc mailing list >>> [hidden email] >>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc -- Alan Knight [|], Engineering Manager, Cincom Smalltalk [hidden email] [hidden email] http://www.cincom.com/smalltalk _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Dear Alan, Dear Helge,
of course it is advisable to put my classes into a namespace - which I actually did now. I just wonder why some of the base system classes are being used prefixed and others not. Perhaps there could be a warning or something similar when you create a class in Smalltalk with a name already used _and_ referenced without a prefix elsewhere. Regards, Steffen Am 21.12.2010, 18:44 Uhr, schrieb Nowak, Helge <[hidden email]>: >> From my point of view you can never be sure that at any point in time >> the System will not have a class that has the same name as yours. >> Therefore I'd call it a good practice to have all my classes in my >> namespace. > > Cheers > Helge > > -----Ursprüngliche Nachricht----- > Von: [hidden email] [mailto:[hidden email]] Im > Auftrag von Alan Knight > Gesendet: Dienstag, 21. Dezember 2010 16:37 > An: [hidden email] > Betreff: Re: [vwnc] MNU in tools after loading parcel > > I think part of the point of the namespace mechanism is that if you're > introducing classes of your own which have names the same as those in > basic Smalltalk, that you can put them in your own namespaces and they > won't conflict with the base. The design which took everything out of > the Smalltalk namespace and put it into sub-namespaces which were then > all imported into Smalltalk so they might as well have been there anyway > is questionable. But I certainly wouldn't want to see all references to > base system classes need to be prefixed. In general, I'd like to avoid > having to use prefixes. Why wouldn't you just create your class in an > application namespace? > > I suspect the reason you see that on one platform but not on another > might be because the order of lookup is not strictly deterministic, so > you might get references resolving to one class on one platform and > another on another. But that's complete speculation on my part, and I'm > not sure what would make the order actually change if you just moved an > image from one platform to another. > > On 2010-12-21 8:16 AM, Steffen Märcker wrote: >> Sorry, my fault. I mean Graphics.Pattern, of course. -_-' >> >> Steffen >> >> >>> Ok, >>> >>> one step further I see several references to Graphics.Image which are >>> not >>> prefixed with the namespace 'Graphics'. I think the get resolved to my >>> class at it doesn't reside inside a namespace other than 'Smalltalk'. >>> If >>> this observation is correct I suggest to correct the references in the >>> base image in order to prevent those problems in general. >>> Any opinions on this? >>> >>> Regards, Steffen >>> >>> >>> Am 21.12.2010, 12:08 Uhr, schrieb Nowak, Helge<[hidden email]>: >>> >>>> I tried on Windows 7: >>>> - If I create the Pattern class as a subclass of Object in my private >>>> namespace there is no problem >>>> - If I create the Pattern class as a subclass of Object in the >>>> Smalltalk >>>> namespace I get on parcel publishing the infinite number of "MNU: >>>> #from:" as you are seeing on parcel load >>>> >>>> >>>> -----Ursprüngliche Nachricht----- >>>> Von: [hidden email] [mailto:[hidden email]] Im >>>> Auftrag von Steffen Märcker >>>> Gesendet: Dienstag, 21. Dezember 2010 11:54 >>>> An: vwnc >>>> Betreff: Re: [vwnc] MNU in tools after loading parcel >>>> >>>> Hi, >>>> >>>> I've got a step further. (Thanks to L. William!) The problems are >>>> caused >>>> by the following class I've defined: >>>> >>>> Class Smalltalk.Pattern >>>> Superclass: Core.Object >>>> ... >>>> >>>> It seems to interfere with either Graphics.Pattern or XML.Pattern on >>>> Windows. This seems odd to me because on Mac everything works >>>> smoothly. >>>> Is >>>> this a know bug or a limitation on Windows? >>>> >>>> Regards, Steffen >>>> >>>> >>>> >>>> Am 21.12.2010, 10:07 Uhr, schrieb Linus Willmann<[hidden email]>: >>>> >>>>> Steffen, >>>>> >>>>> I'd suggest, to create a source file-In from the parcel& file-in >>>>> method >>>>> by method - each time creating the activities to raise the error -to >>>>> find the cause. >>>>> >>>>> Kind regards, >>>>> L. Willmann >>>>> >>>>> ----- Original Message ----- From: "Steffen Märcker"<[hidden email]> >>>>> To: "vwnc"<[hidden email]>; "Steffen Märcker"<[hidden email]> >>>>> Sent: Tuesday, December 21, 2010 9:55 AM >>>>> Subject: Re: [vwnc] MNU in tools after loading parcel >>>>> >>>>> >>>>> Hi, >>>>> >>>>> has anybody some ideas how I can investigate what's going on? >>>>> >>>>> Regards, >>>>> Steffen >>>>> >>>>> Am 20.12.2010, 17:10 Uhr, schrieb Steffen Märcker<[hidden email]>: >>>>> >>>>>> Hi, >>>>>> >>>>>> I've created the attached package on Mac (that library isn't >>>>>> finished >>>>>> yet) >>>>>> and attempted to load it into images on Windows. Loading the parcel >>>>>> seems >>>>>> to be successful. Unfortunately the image gets into an endless loop >>>>>> of >>>>>> opening exceptions notifiers with an MNU ( #from: ) if I use e.g. >>>>>> the >>>>>> browser. For example, try to create a new protocol in some class >>>>>> (not >>>>>> necessarily from this package) and the endless loop starts. >>>>>> I've absolutely no idea what's going on and debugging seems to be >>>>>> impossible. Even stranger, on Mac nothing like this happens. >>>>>> >>>>>> Please help! >>>>>> >>>>>> THX, >>>>>> Steffen >>>>> _______________________________________________ >>>>> vwnc mailing list >>>>> [hidden email] >>>>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >>>>> >>>> _______________________________________________ >>>> vwnc mailing list >>>> [hidden email] >>>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >>> _______________________________________________ >>> vwnc mailing list >>> [hidden email] >>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Free forum by Nabble | Edit this page |