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

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

by StÃ©phane Ducasse

what was the words they used? Stef On Jan 8, 2010, at 11:37 PM, Schwab,Wilhelm K wrote: > Another possibility is to leave off the tense. What we should avoid is WindowMoved while there is still an opportunity to veto it; WindowMove would be (mercifully) neutral. I hesitate to mention that Object Arts went through a high-profile change on this some time back, and had very good reasons for their choices. > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Henrik Sperre Johansen > Sent: Friday, January 08, 2010 4:26 PM > To: pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Notifications of windows opening/closing/focus > > On 08.01.2010 21:37, Gary Chambers wrote: >> If "after the fact" I'd vote for the "ed" suffix too. Make it match >> what is/has happening/happened. >> As a side note, WindowClosing is common to give a potential veto >> chance (i.e. deny close). Should also be a WindowClosed if it does get that far... >> >> Regards, Gary >> > I suggest having both ...ing/...ed versions of close, move and resize, and ...ed for the rest, at least for now. > > 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

Jan. 9, 2010

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

by StÃ©phane Ducasse

would be good too. Stef On Jan 8, 2010, at 10:27 PM, Benoit St-Jean wrote: > Why not something like : > > #aboutToClose and #closed ? > > > ----------------- > Benoit St-Jean > Yahoo! Messenger: bstjean > Blog: lamneth.wordpress.com > A standpoint is an intellectual horizon of radius zero. > (Albert Einstein) > > > From: Gary Chambers <gazzaguru2(a)btinternet.com> > To: Pharo-project(a)lists.gforge.inria.fr > Sent: Fri, January 8, 2010 3:37:39 PM > Subject: Re: [Pharo-project] Notifications of windows opening/closing/focus > > If "after the fact" I'd vote for the "ed" suffix too. Make it match what > is/has happening/happened. > As a side note, WindowClosing is common to give a potential veto chance > (i.e. deny close). Should also be a WindowClosed if it does get that far... > > Regards, Gary > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Friday, January 08, 2010 8:19 PM > Subject: Re: [Pharo-project] Notifications of windows opening/closing/focus > > > Alexandre > > as soon as we will got the names right publish, add a bug tracker item and > this will be integrated > now about the names > > Closing or Closed? > Collapsed? > WindowMoved? > > what is the convention? > when the event happens at the end I would prefer ed > when it occurs over a long action ing > > any english-oriented/design remarks? > ? > > > > > > Alexandre > > > > > > <Picture 3.png> > > > > > > On 8 Jan 2010, at 08:57, Henrik Johansen wrote: > > > >> On Jan 8, 2010, at 11:56 18AM, Gary Chambers wrote: > >> > >>> Looks ok to me. > >>> > >>> Regards, Gary > >>> > >>> ----- Original Message ----- > >>> From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > >>> To: <Pharo-project(a)lists.gforge.inria.fr> > >>> Sent: Thursday, January 07, 2010 8:27 PM > >>> Subject: Re: [Pharo-project] Notifications of windows > >>> opening/closing/focus > >>> > >>> > >>>> > >>>>> 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]. > >> I don't particularly like the naming. > >> > >> - Why including Announcement at the end? > >> - Why does one contain a verb, and the other a > >> - When are they fired? Closing implies to me it's not been closed yet, > >> but fired somewhere after the closing has started, while CreationWindow I > >> have no idea what means. > >> > >> MorphicWindowOpen(ed/ing) > >> MorphicWindowClos(ed/ing) > >> > >> are both easier to read for me, shorter, and more in line with the naming > >> convention for Pragma announcements already in Pharo. > >> > >> Cheers, > >> Henry > >> _______________________________________________ > >> 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 > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > _______________________________________________ > > 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > All new Yahoo! Mail - Get a sneak peak at messages with a handy reading pane._______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 9, 2010

Re: [Pharo-project] GUI how to screencast available

by StÃ©phane Ducasse

send code :) On Jan 8, 2010, at 10:40 PM, Henrik Sperre Johansen wrote: > On 08.01.2010 21:01, laurent laffont wrote: >> Hi, >> >> as I'm beginning to understand how to write a GUI in Pharo, I've made >> a screencast to show basic layout techniques with panels and buttons: >> >> http://vimeo.com/8619593 >> >> Cheers, >> >> Laurent > > I had to laugh when you implemented the red button in debugger, clicked > proceed, then automatically pressed yes in the popup to save the > changes, then promply got a new debugger when clicking the button again, > since the dialog actually reads "Is it ok to discard these changes? Yes/No" > > Maybe we should change that? ;) > > Cheers, > Henry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 9, 2010

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

by StÃ©phane Ducasse

I will give a try to relax from anr writing project. On Jan 8, 2010, at 10:12 PM, Simon Denier wrote: > > On 8 janv. 2010, at 19:27, Mariano Martinez Peck wrote: > >> That's cooler, but you put a white background instead of transparency :( > > At least the body of the lighthouse should be white, otherwise it looks strange on dark background > > <Screen shot 2010-01-08 at 22.12.07.png> > > >> >> To convert a picture (png) for examplte to icns you can use the tool img2icns >> >> cheers >> >> 2010/1/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> I was playing with adding a bit of shadow so that the icon stand out. >> >> >> >> may be people with better tools can produce something better. >> >> >> Stef >> >> >> _______________________________________________ >> 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

Jan. 9, 2010

Re: [Pharo-project] [update 1.1] #11144

by StÃ©phane Ducasse

coool Everytimes this is the same but everytime we get updates I like it! > Issue 429: Pharo logo collapsed like window > Issue 1762: fullScreenMargin min should be -5 > Issue 1580: strange WeakKeyAssociation2 in SystemDictionary... > Issue 1760: Monticello enhancement: avoid removing a method when it does not belong to package anymore > Issue 1757: fix underscores Stef fixing latex and web stuff :( Wanna code.

Jan. 9, 2010

[Pharo-project] [update 1.1] #11144

by Marcus Denker

11144 ----- Issue 429: Pharo logo collapsed like window Issue 1762: fullScreenMargin min should be -5 Issue 1580: strange WeakKeyAssociation2 in SystemDictionary... Issue 1760: Monticello enhancement: avoid removing a method when it does not belong to package anymore Issue 1757: fix underscores

Jan. 9, 2010

[Pharo-project] Morphic (for gary :) and others)

by StÃ©phane Ducasse

Gary and others I really think that we should do an audit of Morphic. In 1.1 we are going already faster but I'm sure that there is plenty of space for improvements. I see several actions - checking squeak toolbuilder enhancements and using it for the tools - checking CUIS - juan did an excellent job remocving a lot of unnecessary code - juan optimize scrollbar - juan did a new texteditor morph - removing/cleaning extra widgets Pluggable/nonpluggable plague. - integrating better polymorph into the widgets layer. What do you think?

Jan. 9, 2010

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

by Henrik Sperre Johansen

On 09.01.2010 02:53, Schwab,Wilhelm K wrote: > Stef, > > Will do. What is the difference between PharoInBox and PharoTaskForces? I see many references to them, but nothing that clarifies what to use when. > PharoInbox is for fixes to issues on the issue tracker. PharoTaskForces is for work in progress, which others may want to load and have a look at. Cheers, Henry

Jan. 9, 2010

[Pharo-project] Fwd: dear contributors

by StÃ©phane Ducasse

Begin forwarded message: > From: pharo-project-owner(a)lists.gforge.inria.fr > Date: January 9, 2010 9:28:55 AM GMT+01:00 > To: stephane.ducasse(a)gmail.com > Subject: dear contributors > > You are not allowed to post to this mailing list, and your message has > been automatically rejected. If you think that your messages are > being rejected in error, contact the mailing list owner at > pharo-project-owner(a)lists.gforge.inria.fr. > > > From: stephane ducasse <stephane.ducasse(a)gmail.com> > Date: January 9, 2010 9:28:49 AM GMT+01:00 > To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr> > Subject: dear contributors > > > - First: THANKS! > - Second: don't forget to sign the license agreement > Even if by the simple act of publishing your code to the inbox you declare it under MIT > We collect, scan, archive Licenses > > http://code.google.com/p/pharo/wiki/LicenseAgreement > > here is the list of people which already signed it > http://code.google.com/p/pharo/wiki/ListOfOkCommitters > if you are not there either I forgot to update it :) or you did not send it > > Stef > > > >

Jan. 9, 2010

Re: [Pharo-project] GUI how to screencast available

by laurent laffont

On Sat, Jan 9, 2010 at 3:52 AM, Objectiveous <objectiveous(a)gmail.com> wrote: > > > Hi, > > > > as I'm beginning to understand how to write a GUI in Pharo, I've made a > screencast to show basic layout techniques with panels and buttons: > > > > http://vimeo.com/8619593 > > You rock! IMO, screencasts like these speak volumes and help newbies (like > me) not only understand the power of smalltalk but, more importantly, help > us make the shift away from our conditioning with respect to how software is > developed. > Thank you.... but I only show what developpers who really rocks have done ;). But I think screencasts are a good way to learn, especially in a Smalltalk environment. As Ramon Leon wrote on his blog "I'm still amazed by how many people think they can grok Smalltalk by seeing syntax examples." http://onsmalltalk.com/why-smalltalk So I'm going to start a Pharo screencast blog .... (a bit like http://railscasts.com/ which is really good). I need screencasts !! Send me links !! Laurent

Jan. 9, 2010