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

Re: [Pharo-project] Notifications of windows opening/closing/focus

by Alexandre Bergel

Hi! In the PharoTaskForces SqueakSource repository I committed a new version of Morphic (Morphic-Alexandre_Bergel.393). This version includes the window announcement I have been working on for few months already. Here is an example of a unit test. -=-=-=-=-=-=-=-=-=-=-=-= MorphicWindowNotificationTest>>testWindowCreationAndDeletion | t window newWindowCreated r | t := 0. World announcer on: MorphicCreationWindowAnnouncement do: [:ann | t := t + 1. newWindowCreated := ann window]. World announcer on: MorphicClosingWindowAnnouncement do: [:ann | t := t + 10. newWindowCreated := ann window]. window := SystemWindow labelled: 'foo'. window openInWorld. self assert: (t = 1). self assert: (window == newWindowCreated). window delete. self assert: (t = 11). self assert: (window == newWindowCreated). -=-=-=-=-=-=-=-=-=-=-=-= If everybody agrees on this, it would be cool to include it in Pharo soon. At each new version of Morphic, I will have to update this, and this is boring. The comment of the .mcz is -=-=-=-=-=-=-=-=-=-=-=-= This new version extends Morphic with a window event mechanism. It add a variables to SystemWindow (thus implies a recompilation of all subclasses of SystemWindow). It does some overrides in: - SystemWindow: for deletion, resize, ... - ScrollPane: notification for scrolling. This part is probably not nicely designed, but it works - PasteUpMorph: World can now emit event for window creation and deletion The method SystemWindow>>openAsIsIn: is overriden. The new version belongs to Morphic, before it belonged to Polymorph. Loading this version make Polymorph dirty therefore. 5 test methods are provided in MorphicWindowNotificationTest. All tests are green in a pharo1.0-10502-rc1dev09.12.2 -=-=-=-=-=-=-=-=-=-=-=-= Comments are welcome Cheers, Alexandre On 7 Jan 2010, at 10:58, Gary Chambers wrote: > Fair enough. Perhaps the "global" announcer could be accessed via the > class-side of SystemWindow. > > Lots of evil ways of manipulating morphs too. Just thought about > hide/show > etc. > > Regards, Gary > > ----- Original Message ----- > From: "Henrik Johansen" <henrik.s.johansen(a)veloxit.no> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Thursday, January 07, 2010 1:28 PM > Subject: Re: [Pharo-project] Notifications of windows opening/ > closing/focus > > >> >> On Jan 7, 2010, at 2:10 04PM, Gary Chambers wrote: >> >>> That is one option, though it does seem to be burdensome on the >>> announcement >>> consumers to (depending upon requirements) possibly have to track >>> all >>> windows themselves. >>> >>> Regards, GaryI am not talking about Announcers, but where the >>> Announcement is created. >> >> I'm not talking about letting the window be the announcer, but >> where the >> announcement is made. >> >> So you'd do >> openAsIsIn: aWorld >> "current implementation" >> someAnnouncer announce: (WindowOpened for: self in: self world) >> >> someAnnouncer could be a global announcer for all window events. >> >> Cheers, >> Henry >> _______________________________________________ >> 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 7, 2010

Re: [Pharo-project] Fix to PackageOrganizer>>packageOfClass:

by Mariano Martinez Peck

On Thu, Jan 7, 2010 at 8:51 PM, Danie Roux <lists+pharo(a)danieroux.com<lists%2Bpharo(a)danieroux.com> > wrote: > 2010/1/7 Mariano Martinez Peck : > > I think we should wrote somewhere how to submit an issue > > I followed http://code.google.com/p/pharo/wiki/HowToContribute :-) > I missed the step to set the status to "Fixed" though. > > Thank you!!! I was looking for that link and I didn't find it. > > it's name and the trick of the dirty packages... > > "The trick of the dirty packages". Sounds like a crime novel. But > seriously, what is this trick? > Sorry for the confusion, you did exactly the correct. The trick is the following (I think it is the same that is explained there...) When you have changed several packages, you have to create another package called SLICE-IssueXXX-DeCRIPTION and then, you have to put to that package, the packages that you modified, as "requierd". Then, when you commit the slice package, it also commits the requiered packages, and thus, all of them are loaded when someone else load that slice package in another image. The trick is that most of the times, all the requiered packages are those who you have modified. So, there is an option (right button in a package) which says "add dirty package as requiered". Dirty in this case means modified. That's all :) Thank you very much! Mariano > > -- > Danie Roux *shuffle* Adore Unix - http://danieroux.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 7, 2010

Re: [Pharo-project] Fix to PackageOrganizer>>packageOfClass:

by StÃ©phane Ducasse

On Jan 7, 2010, at 8:51 PM, Danie Roux wrote: > 2010/1/7 Mariano Martinez Peck : >> I think we should wrote somewhere how to submit an issue > > I followed http://code.google.com/p/pharo/wiki/HowToContribute :-) > I missed the step to set the status to "Fixed" though. > >> it's name and the trick of the dirty packages... > > "The trick of the dirty packages". Sounds like a crime novel. But > seriously, what is this trick? once you created a slice you can if you want and it makes sense for your image get all the dirty packages as dependent of your slice and like that publish in one shot all the changes and me integrate them :) > > -- > Danie Roux *shuffle* Adore Unix - http://danieroux.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 7, 2010

Re: [Pharo-project] Fix to PackageOrganizer>>packageOfClass:

by Danie Roux

2010/1/7 Mariano Martinez Peck : > I think we should wrote somewhere how to submit an issue I followed http://code.google.com/p/pharo/wiki/HowToContribute :-) I missed the step to set the status to "Fixed" though. > it's name and the trick of the dirty packages... "The trick of the dirty packages". Sounds like a crime novel. But seriously, what is this trick? -- Danie Roux *shuffle* Adore Unix - http://danieroux.com

Jan. 7, 2010

Re: [Pharo-project] [ANN] Icons for Mac users

by StÃ©phane Ducasse

> I noticed that tuesday on windows :) > Do you have an idea to make the distinction stronger between image and changes :) > > > Now I was thinking that, if you want, what you can do is to use for the .changes the same icon you see in the dock. Should that help ? which one :)

Jan. 7, 2010

Re: [Pharo-project] Fix to PackageOrganizer>>packageOfClass:

by Mariano Martinez Peck

I think we should wrote somewhere how to submit an issue (It is nothing agains Danie, thank you VERY much for the submit!!!). I mean, all that stuff about the Slice, it's name and the trick of the dirty packages... And then we add that to the website as we did with the issue tracker. On Thu, Jan 7, 2010 at 7:55 PM, Danie Roux <lists+pharo(a)danieroux.com<lists%2Bpharo(a)danieroux.com> > wrote: > On Thu, Jan 7, 2010 at 8:52 PM, StÃ©phane Ducasse wrote: > >> In the old implementation, #packageOfClass: would have returned the > >> first category that matches. It will now return the more specific > >> 'Collections-Text'. > > > > You mean with your fix? > > Yes, once that fix is applied it will return the more specific one. I > apologise for the confusion :-) > > -- > Danie Roux *shuffle* Adore Unix - http://danieroux.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 7, 2010

Re: [Pharo-project] [ANN] Icons for Mac users

by Mariano Martinez Peck

On Thu, Jan 7, 2010 at 6:42 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > cool! > I noticed that tuesday on windows :) > Do you have an idea to make the distinction stronger between image and > changes :) > > Now I was thinking that, if you want, what you can do is to use for the .changes the same icon you see in the dock. Should that help ? > Stef > > On Jan 7, 2010, at 5:51 PM, Mariano Martinez Peck wrote: > > > Hi folks. Once month before I was happy with my Linux box and having my > Pharo icons for .sources, .changes, .image, and vm. Now I have a mac, and I > have the old squeak icons. So.....I created the ones for Pharo :) > > > > I attach a zip file with the files. What you have to do is: > > > > 1) Go to your vm (for example Squeak 4.2.2beta1U.app), and copy it > (backup) with another name in case you don't like the icons > > 2) Go to the original VM -> right button -> Show package content > > 3) Uncompress, copy and replace my attached files for the ones that are > in /Contents/Resources/ > > 4) A reboot may help to see all the changes > > > > That's all. I hope you like it. > > > > Cheers > > > > Mariano > > <macIcons.zip>_______________________________________________ > > 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 >

Jan. 7, 2010

Re: [Pharo-project] Notifications of windows opening/closing/focus

by Alexandre Bergel

> By the way Alex, is there a squeaksource project with your > extensions as regular methods and classes (not in a changeset)? Not yet. But a monticello package would be a bit ugly since: - it adds a variable to SystemWindow - it performs some overrides in ScrollPane and SystemWindow Creating a clean Monticello package is not easy. Cheers, Alexandre > > >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "Henrik Sperre Johansen" <henrik.s.johansen(a)veloxit.no> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Wednesday, January 06, 2010 9:53 PM >> Subject: Re: [Pharo-project] Notifications of windows opening/ >> closing/focus >> >> >>> On 06.01.2010 22:36, Simon Denier wrote: >>>> On 6 janv. 2010, at 18:42, Gary Chambers wrote: >>>> >>>> >>>>> Indeed. Would be nicer if there was a proper announcement >>>>> protocol for >>>>> such >>>>> things though. >>>>> >>>> I see, updateTasks is called everytime a change in layout happens >>>> then. >>>> Indeed, it looks like announcements will greatly simplified the >>>> trick. >>>> >>>> I am not sure where to do the announcement though. Does any top >>>> window >>>> uses openInWorld to add itself to World? >>>> >>>> >>> My guess would be that at the end of >>> SystemWindow>> openAsIsIn: >>> would be the the simplest place to put it. >>> >>> Cheers, >>> Henry >>> >>> _______________________________________________ >>> 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 > > -- > Simon > > > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 7, 2010

Re: [Pharo-project] Fix to PackageOrganizer>>packageOfClass:

by Danie Roux

On Thu, Jan 7, 2010 at 8:52 PM, StÃ©phane Ducasse wrote: >> In the old implementation, #packageOfClass: would have returned the >> first category that matches. It will now return the more specific >> 'Collections-Text'. > > You mean with your fix? Yes, once that fix is applied it will return the more specific one. I apologise for the confusion :-) -- Danie Roux *shuffle* Adore Unix - http://danieroux.com

Jan. 7, 2010

Re: [Pharo-project] Fix to PackageOrganizer>>packageOfClass:

by StÃ©phane Ducasse

> On Thu, Jan 7, 2010 at 8:14 PM, Nicolas Cellier wrote: >> Would it prevent merging squeak/trunk Collection ? >> If yes, I suggest a status quo. > > No, I checked and could merge both ways (adding methods to Text on > Squeak trunk, and Pharo, and "cherry-picking" them both ways). > > Monticello hangs on to the package name and index only by that - it > does not infer it from the class or method. > > The same problem exists in my Squeak trunk image, btw. In this case > only if the name of the shorter package is a symbol: > > (PackageOrganizer default packageNamed: #OB ifAbsent: [ self error: > 'hmm']) includesClass: OBMorphBuilder. > (PackageOrganizer default packageNamed: 'OB-Morphic' ifAbsent: [ self > error: 'hmm']) includesClass: OBMorphBuilder. > > I guess there is a biggest issue to be fixed here, namely the proper > maintenance of "PackageOrganizer default packages" :-) yes and imagine that I cleaned it because it was full of wrong and unused information. > In the old implementation, #packageOfClass: would have returned the > first category that matches. It will now return the more specific > 'Collections-Text'. You mean with your fix?

Jan. 7, 2010