- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Re: Trying to install Magma r41.1throughtMonticello installation 1.5+

by Gary Chambers

Probably! Regards, Gary. ----- Original Message ----- From: "Hilaire Fernandes" <hilaire(a)ofset.org> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, December 02, 2008 4:43 PM Subject: Re: [Pharo-project] Re: Trying to install Magma r41.1throughtMonticello installation 1.5+ > Thanks Gary. > In the mean time I applied the suggested solution from Damien. Is that ok? > > Hilaire > > 2008/12/2 Gary Chambers <gazzaguru2(a)btinternet.com>: >> In the modalMorph method of PSUIManager change the line in the middle to >> the >> following... >> >> >> receiver == World and: [sender selector == #handleEvent: or: [sender >> selector == #findWindow:]]]]) >> >> That should help things.. >> >> Regards, Gary. >> >> ----- Original Message ----- From: "Hilaire Fernandes" >> <hilaire(a)ofset.org> >> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> >> Sent: Tuesday, December 02, 2008 3:19 PM >> Subject: Re: [Pharo-project] Re: Trying to install Magma r41.1 >> throughtMonticello installation 1.5+ >> >> >>> Yes, it is attached to a comment following the bug issue you opened >>> previously :) >>> >>> Damien, thanks to point me to the Seaisde related issue. >>> I trace the bug, and for me the problem seems to come from >>> PSUIManager>>modalMorph, in the loop searching for a Morph to attach >>> to a modal morph. I don't thought how to fix it. >>> >>> Hilaire >>> >>> 2008/12/2 Adrian Lienhard <adi(a)netstyle.ch>: >>>> >>>> Hi Hilaire, >>>> >>>> Just as a side note, instead of sending a screenshot it is more useful >>>> to >>>> send the SqueakDebug.log file that is created when a debugger pops up >>>> in >>>> the >>>> same directory as your squeak image is located. This file contains more >>>> information and requires less space. >>>> >>>> Cheers, >>>> Adrian >>>> >>>> On Dec 2, 2008, at 15:43 , Hilaire Fernandes wrote: >>>> >>>>> I try to load Magma with the patched MC >>>>> (MonticelloConfigurations-cmm.44.mcz and >>>>> Monticello-SR.315.mcz). >>>>> It results on an MNU error PastUpMorph does not undersand >>>>> #description >>>>> >>>>> Hilaire >>>>> >>>>> >>>>> 2008/12/2 Hilaire Fernandes <hilaire(a)ofset.org>: >>>>>> >>>>>> I am CC to the Magma list as it may be more a problem from SqueakMap >>>>>> dependencies. >>>>>> >>>>>> On a fresh update Pharo image, I install Magma r41.1 with: >>>>>> >>>>>> Installer universe install: 'Magma 1.41(r41.1)'. >>>>>> >>>>>> At first MC1.5+ is first installed, at it is marked as a prerequisit. >>>>>> >>>>>> But an error ius raised, indeed it looks like MC1.5+ override of the >>>>>> method >>>>>> >>>>>> httpGetDocument: url args: args accept: mimeType request: >>>>>> requestString >>>>>> >>>>>> is incompatible with Pharo >>>>>> >>>>>> -- >>>>>> http://blog.ofset.org/hilaire >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> http://blog.ofset.org/hilaire >>>>> <install-magma-pharo.png>_______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> http://blog.ofset.org/hilaire >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > http://blog.ofset.org/hilaire > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 2, 2008

Re: [Pharo-project] Re: Trying to install Magma r41.1 throughtMonticello installation 1.5+

by Hilaire Fernandes

Thanks Gary. In the mean time I applied the suggested solution from Damien. Is that ok? Hilaire 2008/12/2 Gary Chambers <gazzaguru2(a)btinternet.com>: > In the modalMorph method of PSUIManager change the line in the middle to the > following... > > > receiver == World and: [sender selector == #handleEvent: or: [sender > selector == #findWindow:]]]]) > > That should help things.. > > Regards, Gary. > > ----- Original Message ----- From: "Hilaire Fernandes" <hilaire(a)ofset.org> > To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, December 02, 2008 3:19 PM > Subject: Re: [Pharo-project] Re: Trying to install Magma r41.1 > throughtMonticello installation 1.5+ > > >> Yes, it is attached to a comment following the bug issue you opened >> previously :) >> >> Damien, thanks to point me to the Seaisde related issue. >> I trace the bug, and for me the problem seems to come from >> PSUIManager>>modalMorph, in the loop searching for a Morph to attach >> to a modal morph. I don't thought how to fix it. >> >> Hilaire >> >> 2008/12/2 Adrian Lienhard <adi(a)netstyle.ch>: >>> >>> Hi Hilaire, >>> >>> Just as a side note, instead of sending a screenshot it is more useful to >>> send the SqueakDebug.log file that is created when a debugger pops up in >>> the >>> same directory as your squeak image is located. This file contains more >>> information and requires less space. >>> >>> Cheers, >>> Adrian >>> >>> On Dec 2, 2008, at 15:43 , Hilaire Fernandes wrote: >>> >>>> I try to load Magma with the patched MC >>>> (MonticelloConfigurations-cmm.44.mcz and >>>> Monticello-SR.315.mcz). >>>> It results on an MNU error PastUpMorph does not undersand #description >>>> >>>> Hilaire >>>> >>>> >>>> 2008/12/2 Hilaire Fernandes <hilaire(a)ofset.org>: >>>>> >>>>> I am CC to the Magma list as it may be more a problem from SqueakMap >>>>> dependencies. >>>>> >>>>> On a fresh update Pharo image, I install Magma r41.1 with: >>>>> >>>>> Installer universe install: 'Magma 1.41(r41.1)'. >>>>> >>>>> At first MC1.5+ is first installed, at it is marked as a prerequisit. >>>>> >>>>> But an error ius raised, indeed it looks like MC1.5+ override of the >>>>> method >>>>> >>>>> httpGetDocument: url args: args accept: mimeType request: requestString >>>>> >>>>> is incompatible with Pharo >>>>> >>>>> -- >>>>> http://blog.ofset.org/hilaire >>>>> >>>> >>>> >>>> >>>> -- >>>> http://blog.ofset.org/hilaire >>>> <install-magma-pharo.png>_______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> http://blog.ofset.org/hilaire >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://blog.ofset.org/hilaire

Dec. 2, 2008

Re: [Pharo-project] Removing a trait from a class

by Hilaire Fernandes

2008/12/2 Adrian Lienhard <adi(a)netstyle.ch>: > > On Dec 2, 2008, at 17:23 , Hilaire Fernandes wrote: > >> it looks like traits can be removed with just writing "uses: {}" > > yes, that is the expected way to do it. > >> Better check some documentation > > does this resolve your problem? So far it seems so. Hilaire

Dec. 2, 2008

Re: [Pharo-project] Re: Trying to install Magma r41.1 throughtMonticello installation 1.5+

by Gary Chambers

In the modalMorph method of PSUIManager change the line in the middle to the following... receiver == World and: [sender selector == #handleEvent: or: [sender selector == #findWindow:]]]]) That should help things.. Regards, Gary. ----- Original Message ----- From: "Hilaire Fernandes" <hilaire(a)ofset.org> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, December 02, 2008 3:19 PM Subject: Re: [Pharo-project] Re: Trying to install Magma r41.1 throughtMonticello installation 1.5+ > Yes, it is attached to a comment following the bug issue you opened > previously :) > > Damien, thanks to point me to the Seaisde related issue. > I trace the bug, and for me the problem seems to come from > PSUIManager>>modalMorph, in the loop searching for a Morph to attach > to a modal morph. I don't thought how to fix it. > > Hilaire > > 2008/12/2 Adrian Lienhard <adi(a)netstyle.ch>: >> Hi Hilaire, >> >> Just as a side note, instead of sending a screenshot it is more useful to >> send the SqueakDebug.log file that is created when a debugger pops up in >> the >> same directory as your squeak image is located. This file contains more >> information and requires less space. >> >> Cheers, >> Adrian >> >> On Dec 2, 2008, at 15:43 , Hilaire Fernandes wrote: >> >>> I try to load Magma with the patched MC >>> (MonticelloConfigurations-cmm.44.mcz and >>> Monticello-SR.315.mcz). >>> It results on an MNU error PastUpMorph does not undersand #description >>> >>> Hilaire >>> >>> >>> 2008/12/2 Hilaire Fernandes <hilaire(a)ofset.org>: >>>> >>>> I am CC to the Magma list as it may be more a problem from SqueakMap >>>> dependencies. >>>> >>>> On a fresh update Pharo image, I install Magma r41.1 with: >>>> >>>> Installer universe install: 'Magma 1.41(r41.1)'. >>>> >>>> At first MC1.5+ is first installed, at it is marked as a prerequisit. >>>> >>>> But an error ius raised, indeed it looks like MC1.5+ override of the >>>> method >>>> >>>> httpGetDocument: url args: args accept: mimeType request: requestString >>>> >>>> is incompatible with Pharo >>>> >>>> -- >>>> http://blog.ofset.org/hilaire >>>> >>> >>> >>> >>> -- >>> http://blog.ofset.org/hilaire >>> <install-magma-pharo.png>_______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > http://blog.ofset.org/hilaire > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 2, 2008

Re: [Pharo-project] Removing a trait from a class

by Adrian Lienhard

On Dec 2, 2008, at 17:23 , Hilaire Fernandes wrote: > it looks like traits can be removed with just writing "uses: {}" yes, that is the expected way to do it. > Better check some documentation does this resolve your problem? Adrian > > > Hilaire > > > 2008/12/2 Hilaire Fernandes <hilaire(a)ofset.org>: >> Okay, recheck with a fresh 10185, I can't remove the trait from my >> class. >> What I do, from OB I change the class definition (remove the line >> with >> the trait) then save. The trait just gets back. Is it the right way >> to >> do it? >> >> Which paper is appropriate to read, I saw several references in the >> squeak wiki? >> >> Hilaire >> >> 2008/12/2 Adrian Lienhard <adi(a)netstyle.ch>: >>> Hi Hilaire, >>> >>> Which UI tools do you use? Omnibrowser or the old browser that is >>> shipped >>> with the Core image. >>> Could you try to reproduce the problem in a newer version of >>> Pharo? (10050 >>> is *very* old). >>> >>> I'd like to take a look then. It's strange because we have been >>> using traits >>> for two years now without seeing this problem. So it may indeed be >>> a problem >>> related to the UI that somehow brings traits into an inconsistent >>> state. >>> >>> Adrian >>> >>> >>> On Dec 2, 2008, at 11:08 , Hilaire Fernandes wrote: >>> >>>> I can't remove a trait from a class using UI tools. (pharo 10050) >>>> How can I remove it programmatically ? >>>> >>>> Next with this same class, message from this trait are not >>>> reachable, >>>> the MNU is raised but the hierarchy is not right as IFIETayage1 >>>> is not >>>> a subclass of IFIExoMorph. However IFIExoMorph is using the same >>>> trait >>>> as IFIEtayage. >>>> It looks like there is mismatch in the classes with traits. (see >>>> screenshot) >>>> >>>> Now I realize my last istoa release suffer from this problem :) >>>> >>>> Hilaire >>>> >>>> -- >>>> http://blog.ofset.org/hilaire >>>> <bug-trait.png>_______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> http://blog.ofset.org/hilaire >> > > > > -- > http://blog.ofset.org/hilaire > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 2, 2008

Re: [Pharo-project] Removing a trait from a class

by Hilaire Fernandes

it looks like traits can be removed with just writing "uses: {}" Better check some documentation Hilaire 2008/12/2 Hilaire Fernandes <hilaire(a)ofset.org>: > Okay, recheck with a fresh 10185, I can't remove the trait from my class. > What I do, from OB I change the class definition (remove the line with > the trait) then save. The trait just gets back. Is it the right way to > do it? > > Which paper is appropriate to read, I saw several references in the squeak wiki? > > Hilaire > > 2008/12/2 Adrian Lienhard <adi(a)netstyle.ch>: >> Hi Hilaire, >> >> Which UI tools do you use? Omnibrowser or the old browser that is shipped >> with the Core image. >> Could you try to reproduce the problem in a newer version of Pharo? (10050 >> is *very* old). >> >> I'd like to take a look then. It's strange because we have been using traits >> for two years now without seeing this problem. So it may indeed be a problem >> related to the UI that somehow brings traits into an inconsistent state. >> >> Adrian >> >> >> On Dec 2, 2008, at 11:08 , Hilaire Fernandes wrote: >> >>> I can't remove a trait from a class using UI tools. (pharo 10050) >>> How can I remove it programmatically ? >>> >>> Next with this same class, message from this trait are not reachable, >>> the MNU is raised but the hierarchy is not right as IFIETayage1 is not >>> a subclass of IFIExoMorph. However IFIExoMorph is using the same trait >>> as IFIEtayage. >>> It looks like there is mismatch in the classes with traits. (see >>> screenshot) >>> >>> Now I realize my last istoa release suffer from this problem :) >>> >>> Hilaire >>> >>> -- >>> http://blog.ofset.org/hilaire >>> <bug-trait.png>_______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > http://blog.ofset.org/hilaire > -- http://blog.ofset.org/hilaire

Dec. 2, 2008

Re: [Pharo-project] Removing a trait from a class

by Hilaire Fernandes

Okay, recheck with a fresh 10185, I can't remove the trait from my class. What I do, from OB I change the class definition (remove the line with the trait) then save. The trait just gets back. Is it the right way to do it? Which paper is appropriate to read, I saw several references in the squeak wiki? Hilaire 2008/12/2 Adrian Lienhard <adi(a)netstyle.ch>: > Hi Hilaire, > > Which UI tools do you use? Omnibrowser or the old browser that is shipped > with the Core image. > Could you try to reproduce the problem in a newer version of Pharo? (10050 > is *very* old). > > I'd like to take a look then. It's strange because we have been using traits > for two years now without seeing this problem. So it may indeed be a problem > related to the UI that somehow brings traits into an inconsistent state. > > Adrian > > > On Dec 2, 2008, at 11:08 , Hilaire Fernandes wrote: > >> I can't remove a trait from a class using UI tools. (pharo 10050) >> How can I remove it programmatically ? >> >> Next with this same class, message from this trait are not reachable, >> the MNU is raised but the hierarchy is not right as IFIETayage1 is not >> a subclass of IFIExoMorph. However IFIExoMorph is using the same trait >> as IFIEtayage. >> It looks like there is mismatch in the classes with traits. (see >> screenshot) >> >> Now I realize my last istoa release suffer from this problem :) >> >> Hilaire >> >> -- >> http://blog.ofset.org/hilaire >> <bug-trait.png>_______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://blog.ofset.org/hilaire

Dec. 2, 2008

Re: [Pharo-project] Re: Trying to install Magma r41.1 throught Monticello installation 1.5+

by Hilaire Fernandes

Yes, it is attached to a comment following the bug issue you opened previously :) Damien, thanks to point me to the Seaisde related issue. I trace the bug, and for me the problem seems to come from PSUIManager>>modalMorph, in the loop searching for a Morph to attach to a modal morph. I don't thought how to fix it. Hilaire 2008/12/2 Adrian Lienhard <adi(a)netstyle.ch>: > Hi Hilaire, > > Just as a side note, instead of sending a screenshot it is more useful to > send the SqueakDebug.log file that is created when a debugger pops up in the > same directory as your squeak image is located. This file contains more > information and requires less space. > > Cheers, > Adrian > > On Dec 2, 2008, at 15:43 , Hilaire Fernandes wrote: > >> I try to load Magma with the patched MC >> (MonticelloConfigurations-cmm.44.mcz and >> Monticello-SR.315.mcz). >> It results on an MNU error PastUpMorph does not undersand #description >> >> Hilaire >> >> >> 2008/12/2 Hilaire Fernandes <hilaire(a)ofset.org>: >>> >>> I am CC to the Magma list as it may be more a problem from SqueakMap >>> dependencies. >>> >>> On a fresh update Pharo image, I install Magma r41.1 with: >>> >>> Installer universe install: 'Magma 1.41(r41.1)'. >>> >>> At first MC1.5+ is first installed, at it is marked as a prerequisit. >>> >>> But an error ius raised, indeed it looks like MC1.5+ override of the >>> method >>> >>> httpGetDocument: url args: args accept: mimeType request: requestString >>> >>> is incompatible with Pharo >>> >>> -- >>> http://blog.ofset.org/hilaire >>> >> >> >> >> -- >> http://blog.ofset.org/hilaire >> <install-magma-pharo.png>_______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://blog.ofset.org/hilaire

Dec. 2, 2008

[Pharo-project] about vm dropping privileges

by StÃ©phane Ducasse

Hi all I was rereading our excellent forthcoming seaside book :) And lukas wrote "To listen on port 80, the standard port used by the HTTP protocol, the web server needs to run as root. Running a public service as root is a huge security issue. Dedicated web servers such as Apache drop their root privileges after startup. This allows them to listen to port 80 while not being root. Unfortunately this is not something that can be easily done from within the Smalltalk VM. " And I was wondering what is the exact problem? Stef

Dec. 2, 2008

Re: [Pharo-project] Polymorph password dialog enhancement

by Marcus Denker

Hi, Yes, please use the bugtracker. I try to delete emails as soon as possible... It is very likely that I will not save hundrets of emails with bug- reports/enhancements. (And I am sure nobody else does, either). This way, it is garanteed that such a report is lost. Marcus On 02.12.2008, at 15:52, Damien Cassou wrote: > Hi Torsten, > > please use the issue tracker. I have filled your issue at > http://code.google.com/p/pharo/issues/detail?id=369 > > Bye > > On Tue, Dec 2, 2008 at 3:23 PM, Torsten Bergmann <astares(a)gmx.de> > wrote: >> Hi Gary, >> >> since Polymorph is now in Pharo I tried the following: >> >> UIManager default requestPassword: 'Enter Password' >> >> This currently shows the old Morphic dialog. >> >> The attached changeset enhances Pharo to support a password dialog. >> >> It overrides #requestPassword: to provide a new PasswordDialogWindow >> using a password replaced font. >> >> Feel free to integrate it into polymorph. >> >> Thx >> Torsten >> >> >> -- >> Sensationsangebot verlÃ¤ngert: GMX FreeDSL - Telefonanschluss + DSL >> fÃ¼r nur 16,37 Euro/mtl.!* http://dsl.gmx.de/? >> ac=OM.AD.PD003K1308T4569a >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> > > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Dec. 2, 2008