December 2008 - Pharo-dev - lists.pharo.org

[Pharo-project] 10183 freeze on Gatesware

by Bill Schwab

I just downloaded 10183 to an XP machine, copied a VM and changes and dragged the image to the vm. It starts just fine, but the GUI is frozen. The VM system menu opens up and works. Unfortunately, the thread dump shows only the current thread, which appears to be the idle process: 155872232 >idleProcess 155871568 [] in >startUp 155871660 [] in BlockContext>newProcess Any ideas? Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

Dec. 3, 2008

[Pharo-project] some new issues for unimplemented calls

by Pavel Krivanek

Hi, I added several new simple issues for removing few unimplemented calls: http://code.google.com/p/pharo/issues/detail?id=373 http://code.google.com/p/pharo/issues/detail?id=374 http://code.google.com/p/pharo/issues/detail?id=375 http://code.google.com/p/pharo/issues/detail?id=376 http://code.google.com/p/pharo/issues/detail?id=377 http://code.google.com/p/pharo/issues/detail?id=378 http://code.google.com/p/pharo/issues/detail?id=379 -- Pavel

Dec. 3, 2008

Re: [Pharo-project] Polymorph password dialog enhancement

by StÃ©phane Ducasse

> > > The problem is that removing etoys is not a clean thing. We have > first methods > that are needed to be changed for both removing etoys *and* > polymorph. So that's > why the packages need to be in the pharo repository. > > In general, if you think about code quality or modularity in the > context of Squeak: > Think about the worst you can think of, then multiply it by a factor > of 100. Then > you get to what the current state is in Squeak. It's a mess of epic > proportions... Not that quite :) It is getting better every day. :) And I will really get better. Now this is true that etoy is a great idea with a bad implementation. Stef

Dec. 3, 2008

Re: [Pharo-project] Impressed, overwhelmed, and a little confused

by StÃ©phane Ducasse

There will be a pharo universe I imagine. Stef On Dec 3, 2008, at 10:12 AM, Damien Cassou wrote: > On Wed, Dec 3, 2008 at 7:24 AM, Bill Schwab <BSchwab(a)anest.ufl.edu> > wrote: >> As Pharo 1.0 takes shape, what is the plan for getting packages >> loaded >> the way each of us wants? Is Installer the preferred route? Would >> I be >> expected to script it (I find myself hoping so - load the latest of >> this, that, specific version of this other thing, etc.)? I tried to >> quickly load Shout and the SM package loader was not happy, but that >> could easily be my fault. >> >> More questions and comments, but first, I need to get some overdue >> sleep. > > The tools referenced at http://code.google.com/p/pharo/wiki/Packages > will be included by default (this includes Shout, eCompletion, OB...). > Installer and Universe will probably be both available to install > other things. > > -- > 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 >

Dec. 3, 2008

Re: [Pharo-project] about vm dropping privileges

by StÃ©phane Ducasse

then lukas what you wrote in the book does not describe the correct problem. Because when I read I thought it was a problem of the Smalltalk VM "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. " You write "Dedicated web servers such as Apache drop their root privileges after startup." So I was wondering why a SMalltalk VM cannot do the same? Stef On Dec 2, 2008, at 10:30 PM, Lukas Renggli wrote: >> my question was more how can the VM be fixed :) > > That's not a VM issue. It's not even a Smalltalk issue. It is just > common sense to not run anything reachable in public as root. There is > nothing to be fixed. As a developer you usually want to be able to > freely interact with the rest of the world (FFI, Aliens, OSProcess, > etc), but keep the risk of a system break-in as low as possible. > > Also see the recent discussion in the Squeak mailing-list about that: > <http://lists.squeakfoundation.org/pipermail/squeak-dev/2008-November/132679… > >. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 3, 2008

Re: [Pharo-project] Monticello configuration still broken

by StÃ©phane Ducasse

Yes but when we load a package we load the package and its extensions and in Pharo we take care about that. Stef On Dec 3, 2008, at 12:02 AM, Keith Hodges wrote: > StÃ©phane Ducasse wrote: >> It depends on what is inside MC1.5 > It should not. >> When you load a package you load all the extensions. > When you load a package like MC1.5 you are buying into to the > philosophy, you would be joining a collaborative venture to benefit > all. > > The philosophy being that it should work for as many people as > possible, > be as backwardly compatible as possible, incorporate as many fixes as > possible for everyone and provide a basis for moving forward. > > If within the actual code there is something you dont like then you > can > join in with the effort and fix it, because it is a collaborative > effort > moving forward. > > Keith > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 3, 2008

Re: [Pharo-project] Re: Missing #dispatchResultsIntoHistory

by Alexandre Bergel

You're right, sorry about that. Fixed. Alexandre On 3 Dec 2008, at 16:59, David RÃ¶thlisberger wrote: > Thanks, Alex, but shouldn't it read: > > ifSUnitSupportHistory: aBlock > (TestResult includesSelector: #updateResultsInHistory) ifTrue: > [aBlock value] > > Because in your version aBlock never gets executed, not even when > #updateResultsInHistory exists. > Can you check? > > David > > >> The comment is: >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> Added: >> OBCmdSUnit>>ifSUnitSupportHistory: >> This is necessary to check whether the history feature is installed >> in the current SUnit framework in order to benefit from it and make >> sure that nothing break if not installed >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> Cheers, >> Alexandre >> On 3 Dec 2008, at 11:33, Damien Cassou wrote: >>> On Wed, Dec 3, 2008 at 3:29 PM, Alexandre Bergel <alexandre(a)bergel.eu >>> > wrote: >>>> I just downloaded Squeak3.10. How can I reproduce the problem you >>>> encountered ? >>> >>> Using Universe, install the "Squeak-dev image" package. Then, open a >>> browser, select a class and press ALT+t >>> >>> >>> -- >>> 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 3, 2008

Re: [Pharo-project] Re: Missing #dispatchResultsIntoHistory

by David RÃ¶thlisberger

Thanks, Alex, but shouldn't it read: ifSUnitSupportHistory: aBlock (TestResult includesSelector: #updateResultsInHistory) ifTrue: [aBlock value] Because in your version aBlock never gets executed, not even when #updateResultsInHistory exists. Can you check? David > The comment is: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Added: > OBCmdSUnit>>ifSUnitSupportHistory: > This is necessary to check whether the history feature is installed in > the current SUnit framework in order to benefit from it and make sure > that nothing break if not installed > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > Cheers, > Alexandre > > > On 3 Dec 2008, at 11:33, Damien Cassou wrote: > >> On Wed, Dec 3, 2008 at 3:29 PM, Alexandre Bergel <alexandre(a)bergel.eu> >> wrote: >>> I just downloaded Squeak3.10. How can I reproduce the problem you >>> encountered ? >> >> Using Universe, install the "Squeak-dev image" package. Then, open a >> browser, select a class and press ALT+t >> >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >

Dec. 3, 2008

[Pharo-project] Re: Missing #dispatchResultsIntoHistory

by Alexandre Bergel

OB-Enhancements-AlexandreBergel.262 is in OB@wiresong. The comment is: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Added: OBCmdSUnit>>ifSUnitSupportHistory: This is necessary to check whether the history feature is installed in the current SUnit framework in order to benefit from it and make sure that nothing break if not installed -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Cheers, Alexandre On 3 Dec 2008, at 11:33, Damien Cassou wrote: > On Wed, Dec 3, 2008 at 3:29 PM, Alexandre Bergel > <alexandre(a)bergel.eu> wrote: >> I just downloaded Squeak3.10. How can I reproduce the problem you >> encountered ? > > Using Universe, install the "Squeak-dev image" package. Then, open a > browser, select a class and press ALT+t > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 3, 2008

Re: [Pharo-project] Polymorph password dialog enhancement

by Marcus Denker

On 03.12.2008, at 15:49, Gary Chambers wrote: > Well, I will try to maintain things such that Polymorph is > compatible with both for now (an extra package for Squeak). If > Markus can let me know the differences I'll move the affected > methods out. > 1) FileList2 is gone. the method #morphicPatternPane is now in FileList 2) Morph>>#privateMoveBy: Here we removed all the code at the beginning related to Pen: extension ifNotNil: [extension player ifNotNil: ["Most cases eliminated fast by above test" self getPenDown ifTrue: ["If this is a costume for a player with its pen down, draw a line." self moveWithPenDownBy: delta]]]. That's it for now... in addition, the polymorph overrides did override some change of the etoy and preference cleanups. e.g. Debugger>>buildMorphicNotifierLabelled: label message: messageString has now again a check for "Preferences eToyFriendly". I am sure there are some more of these case. Marcus > As for the PasswordDialogWindow... just putting in now. Reworked to > be more in keeping with Polymorph. > > Regards, Gary. > > > ----- Original Message ----- From: "Torsten Bergmann" <astares(a)gmx.de> > To: <pharo-project(a)lists.gforge.inria.fr> > Sent: Wednesday, December 03, 2008 2:33 PM > Subject: [Pharo-project] Polymorph password dialog enhancement > > >> It's not a question of compatibility, the question is where will >> Polymorph be continued - in SqS/Pharo or SqS/UIEnhancements or both? >> >> I didnt notice (until now) that the integrated plymorph packages >> are now also >> in the SqS/Pharo repository. >> >> A new branch or just a move? Same question applies for other packages >> integrated later. >> >> Bye >> Torsten >> >> >> BTW: Will I have to open an issue when I just put something into >> the inbox >> (like a new ScriptLoader from today that fixes Seaside >> loading)? >> >> >> >> >> >> >> >> >> -- >> Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit >> allen: http://www.gmx.net/de/go/multimessenger >> >> _______________________________________________ >> 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 -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Dec. 3, 2008