June 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] amount of recheable objects from a root one?

by Mariano Martinez Peck

Hi folks. I need to do something and I am a little lazy to do it. Maybe someone already did it and can share it with me. I want to take an object X. That object has references to other objects and I imagine that as a graph. I need to traverse the graph, and get the final amount of reachable objects from the object X. I mean, the size of that graph. I need to avoid cycles and not count objects already counted. Maybe I can reuse part of SmartRefStream? Thanks for any tip. Mariano

June 27, 2010

Re: [Pharo-project] squeaksource is down (again ...)

by Lukas Renggli

>> Would you be able to at least make the image available somewhere so >> one knows about the loaded packages and applied patches. >> Maybe someone has a minute ... > > Nope, I don't have access to the server anymore. You'd have to ask Lukas > or Adrian. There's still the issue with "private" projects though. It is running the latest version from http://www.squeaksource.com/ss. Lukas -- Lukas Renggli www.lukas-renggli.ch

June 27, 2010

Re: [Pharo-project] Changing color/fillStyle by morph halo menu in 1.1rc2

by Denis Kudriashov

I can't see full morph appearance. I just see what color I select. But It's nothing because I need see my little changes in full morph appearance. For example color of button should satisfy color of pane. And when I change button color I want immediately see full picture of my application view. I think It is very important for UI design. 2010/6/27 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > I do not understand because you can see the selected color in the selected > color little pane. > Is it not what you need? > Stef] > On Jun 27, 2010, at 11:53 AM, Denis Kudriashov wrote: > > > I try last Pharo 1.1 rc2 10.06.10. > > > > I found that tool for changing color by user is changed. ColorPickerMorph > is removed. Now I can't dynamically change color by mouse and see my changes > immediately. Now I must select color in new tool, press ok button. And after > that tool close and I must open it again if I dont like my changes. > > > > It is bad behavior compare with pharo 1.0/squeak. But I really like new > color picker morph. > > > > New tool is ColorSelectorDialogWindow. > > How I can hookup It for tracking color selection? > > Maybe I must add some event triggering in #basicSelectedColor: method. > > But I see many #changed: sends in #basicSelectedColor: method. And maybe > I already can implement some dependent class for needed stuff. > > > > What you think? > > _______________________________________________ > > 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 >

June 27, 2010

Re: [Pharo-project] squeaksource is down (again ...)

by Philippe Marschall

On 24.06.2010 15:10, Torsten Bergmann wrote: >> What could be done is moving to an up to date image/vm but this is a bit >> of work. > > Would you be able to at least make the image available somewhere so > one knows about the loaded packages and applied patches. > Maybe someone has a minute ... Nope, I don't have access to the server anymore. You'd have to ask Lukas or Adrian. There's still the issue with "private" projects though. What would probably be an easy fix is to use mod_xsendfile [1] to deliver the versions. That would take load off the image. It requires sever access though. [1] http://tn123.ath.cx/mod_xsendfile/ Cheers Philippe

June 27, 2010

Re: [Pharo-project] ESUG will sponsor the XMLRPC project!

by Philippe Marschall

On 26.06.2010 19:27, GermÃ¡n Arduino wrote: > Hi Folks, > > I'm very happy of announce that ESUG will be sponsoring my work to > develop a XMLRPC client interface, as I comment on my blog: > http://germanarduino.blogspot.com/2010/06/esug-will-sponsor-xmlrpc-project.…. > > I want to thank publicly to StÃ©phane Ducasse, Alain Plantec, Nuory > Bouraqadi and ESUG, as they are sponsoring this initiative under the > "support your project" program, described in > http://www.esug.org/Promotion/Project . Thanks you very much ESUG. > > Any comment or suggestion to this project is more than welcomed. WTF?! It's 2010 and you're implementing XMLRPC. Srsly guys? What's next CORBA? Cheers Philippe

June 27, 2010

Re: [Pharo-project] Changing color/fillStyle by morph halo menu in 1.1rc2

by StÃ©phane Ducasse

I do not understand because you can see the selected color in the selected color little pane. Is it not what you need? Stef] On Jun 27, 2010, at 11:53 AM, Denis Kudriashov wrote: > I try last Pharo 1.1 rc2 10.06.10. > > I found that tool for changing color by user is changed. ColorPickerMorph is removed. Now I can't dynamically change color by mouse and see my changes immediately. Now I must select color in new tool, press ok button. And after that tool close and I must open it again if I dont like my changes. > > It is bad behavior compare with pharo 1.0/squeak. But I really like new color picker morph. > > New tool is ColorSelectorDialogWindow. > How I can hookup It for tracking color selection? > Maybe I must add some event triggering in #basicSelectedColor: method. > But I see many #changed: sends in #basicSelectedColor: method. And maybe I already can implement some dependent class for needed stuff. > > What you think? > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 27, 2010

Re: [Pharo-project] Changing color/fillStyle by morph halo menu in 1.1rc2

by StÃ©phane Ducasse

improvements are always welcome. We removed ColorPickerMorph because it was subclassing a giant and bad class. Stef On Jun 27, 2010, at 11:53 AM, Denis Kudriashov wrote: > I try last Pharo 1.1 rc2 10.06.10. > > I found that tool for changing color by user is changed. ColorPickerMorph is removed. Now I can't dynamically change color by mouse and see my changes immediately. Now I must select color in new tool, press ok button. And after that tool close and I must open it again if I dont like my changes. > > It is bad behavior compare with pharo 1.0/squeak. But I really like new color picker morph. > > New tool is ColorSelectorDialogWindow. > How I can hookup It for tracking color selection? > Maybe I must add some event triggering in #basicSelectedColor: method. > But I see many #changed: sends in #basicSelectedColor: method. And maybe I already can implement some dependent class for needed stuff. > > What you think? > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 27, 2010

[Pharo-project] Changing color/fillStyle by morph halo menu in 1.1rc2

by Denis Kudriashov

I try last Pharo 1.1 rc2 10.06.10. I found that tool for changing color by user is changed. ColorPickerMorph is removed. Now I can't dynamically change color by mouse and see my changes immediately. Now I must select color in new tool, press ok button. And after that tool close and I must open it again if I dont like my changes. It is bad behavior compare with pharo 1.0/squeak. But I really like new color picker morph. New tool is ColorSelectorDialogWindow. How I can hookup It for tracking color selection? Maybe I must add some event triggering in #basicSelectedColor: method. But I see many #changed: sends in #basicSelectedColor: method. And maybe I already can implement some dependent class for needed stuff. What you think?

June 27, 2010

[Pharo-project] GLORP in Pharo

by Alberto Bacchelli

Hi, What is the current situation of GLORP in Pharo? Is there any working porting? Otherwise are there reliable alternatives to it? Thank you. Cheers, Alberto

June 27, 2010

[Pharo-project] SUnit tests failures and errors

by Benoit St-Jean

If that helps (please say yes, it took HOURS to run!), here are the latest results of running all unit tests for: Image: Pharo-1.1-11400-rc2 Latest update: #11400 OS: Windows XP, SP3 VM version string: Squeak3.10.2 of ''5 June 2008'' [latest update: #7179] Hope this helps! ----------------- Benoit St-Jean A standpoint is an intellectual horizon of radius zero. (Albert Einstein) From: laurent.laffont(a)gmail.com Date: Sun, 27 Jun 2010 08:33:52 +0200 To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] SystemNavigation#allSendersOf: vs SystemNavigation#allReferencesTo: Hi, in Autotest I search for all senders of a method. The first version used SystemNavigation#allSendersOf: which sometimes returns wrong results (I think). For example: senders := (SystemNavigation default allSendersOf: #methodsFor:). senders size. "answers 18"senders collect: [:aReference| aReference compiledMethod]. debuggers open as ChangeSet#scanCategory doesn't exist (it's on the class side but allSendersOf: returns #scanCategory reference on class side and instance side). With #allReferencesTo: senders := (SystemNavigation default allReferencesTo: #methodsFor:).senders size. "answers 16" Is this a bug in #allSendersOf: or I don't understand ? Cheers,Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ _________________________________________________________________ Look 'em in the eye: FREE Messenger video chat http://go.microsoft.com/?linkid=9734386

June 27, 2010