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

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

by laurent laffont

Learn me, I will do ;) Laurent 2010/1/8 Gary Chambers <gazzaguru2(a)btinternet.com> > Very nice... just shows how quick things can be with Pharo... > Might be nice to do another, leveraging Polymorph helpers for something > more complex but just as easy ;-) > > Regards, Gary > > ----- Original Message ----- > *From:* laurent laffont <laurent.laffont(a)gmail.com> > *To:* An open mailing list to discuss any topics related to an > open-sourceSmalltalk <pharo-project(a)lists.gforge.inria.fr> > *Sent:* Friday, January 08, 2010 8:01 PM > *Subject:* [Pharo-project] GUI how to screencast available > > 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 > > (or on my blog :) with source code > http://magaloma.blogspot.com/2010/01/gui-et-pharo.html ) > > > It seems that several people have or plan to record screencasts on Pharo. > If you can send me links, I can put all of them on a single blog. For > example http://pharocasts.org ;). > > Cheers, > > Laurent > > ------------------------------ > > _______________________________________________ > 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. 8, 2010

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

by Benoit St-Jean

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 __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/

Jan. 8, 2010

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

by Henrik Sperre Johansen

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

Jan. 8, 2010

Re: [Pharo-project] Problems with Strike fonts

by Henrik Sperre Johansen

The problem with too narrow Italic was not caused by an old version of the bitmaps, which would be fixed by loading the ones on squeaksource. It was caused by "isSynthetic" being used for two purposes: 1) Deciding which fonts were safe to delete when cleaning cache 2) Deriving a custom baseKern for italic fonts calculated from a non-italic font. The two clash however, when you strikethrough/bold/underline an already custom italic font, since it would be both synthetic and have the italic property... My suggested hotfix was to remove the setting of fonts as synthetic when derived from custom italic fonts, although this will cause them to not be deleted when cleaning cache, it will make them render correctly. A better alternative, I think, is to introduce another synthetic setting (inst var type of StrikeFont, only 0 and 3 is currently used), indicating the font is synthetic in the sense it can be deleted from caches, but derived from an italic base font so no kern adjustment should be used. The issue that the paint rule for making derived bold/italic versions do not respect alpha values if they exist in the base font still remains unsolved by this. Cheers, Henry On 08.01.2010 21:05, StÃ©phane Ducasse wrote: > are you suggesting that we load your DejaVu package in pharodev? > > On Jan 8, 2010, at 6:02 PM, Alain Plantec wrote: > > >> Mariano Martinez Peck a Ã©crit : >> >>> Thanks Henrik. However, I tried what you told me and still is ugly :( >>> >> maybe you could try with the dejavu from www.squeaksource.com/DejaVu >> Alain >> >>> Any idea? >>> >>> Thanks >>> >>> Mariano >>> >> >> _______________________________________________ >> 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. 8, 2010

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

by Simon Denier

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 > > 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

Jan. 8, 2010

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

by Michael Roberts

ok, I don't mind the breakage so much, it's just a bit entertaining when trying to do continuous integration. We will need to agree what our expectations of a continuous integration solution are, because if you push out an update that can not launch scripts then we're stuffed. This is of course true to changes to the execution machinery and other fundamental areas. I'm interested in what you think about the future process. Mike On Fri, Jan 8, 2010 at 9:00 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jan 8, 2010, at 9:56 PM, Michael Roberts wrote: > >> unfortunately, it looks like this update has killed my build server. >> This image can no longer file in scripts from the command line. >> >> it looks like asUrl was removed from String. Â was this intentional? >> > > This is fixed in 11143... MC likes to omit methods that are recategorized. > > Â Â Â Â Marcus > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 8, 2010

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

by StÃ©phane Ducasse

no this is bug in MC that removed the method when moving between packages. Stef On Jan 8, 2010, at 9:56 PM, Michael Roberts wrote: > unfortunately, it looks like this update has killed my build server. > This image can no longer file in scripts from the command line. > > it looks like asUrl was removed from String. was this intentional? > > thanks, > Mike > > On Fri, Jan 8, 2010 at 10:37 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> 11139 >> ----- >> >> Issue 1753: results of cycle cleaning experiment >> >> on 7.1.2010 we used Jannik's tool to find cyclic dependencies between packages. We started to >> clean the easy ones. >> >> In addition, some unsent methods where removed: >> >> Array removeSelector: #evalStrings! >> Collection removeSelector: #chooseOne:! >> FileDirectory removeSelector: #directoryObject! >> FileDirectory removeSelector: #updateProjectInfoFor:! >> HTTPSocket class removeSelector: #httpShowGif:! >> HTTPSocket class removeSelector: #httpShowJpeg:! >> HTTPSocket class removeSelector: #retry:asking:ifGiveUp:! >> HTTPSocket class removeSelector: #showImage:named:! >> Preferences class removeSelector: #swapMouseButtons! >> String removeSelector: #asIRCLowercase! >> TextMorphEditor removeSelector: #selectAndScrollToTop! >> TextMorphEditor removeSelector: #selectForTopFrom:to:! >> TextMorphEditor removeSelector: #userHasNotEdited! >> PreferenceBrowserMorph class removeSelector: #updateBrowsers! >> WideString class removeSelector: #allMultiStringMethods! >> WideString class removeSelector: #allNonAsciiMethods! >> Utilities class removeSelector: #assureAvailabilityOfUnstableUpdateStream! >> Utilities class removeSelector: #broadcastUpdatesFrom:to:except:! >> Utilities class removeSelector: #fileInFromUpdatesFolder:! >> Utilities class removeSelector: #initializeClosures! >> Utilities class removeSelector: #openRecentSubmissionsBrowser! >> >> >> _______________________________________________ >> 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. 8, 2010

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

by StÃ©phane Ducasse

;) I like when we develop reflexes tx Stef On Jan 8, 2010, at 9:53 PM, Nicolas Cellier wrote: > http://code.google.com/p/pharo/issues/detail?id=1760

Jan. 8, 2010

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

by StÃ©phane Ducasse

Laurent you do not need () in mainPanel color: (Color blue) On Jan 8, 2010, at 9:01 PM, 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 > > (or on my blog :) with source code http://magaloma.blogspot.com/2010/01/gui-et-pharo.html ) > > > It seems that several people have or plan to record screencasts on Pharo. If you can send me links, I can put all of them on a single blog. For example http://pharocasts.org ;). > > Cheers, > > Laurent > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 8, 2010

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

by Marcus Denker

On Jan 8, 2010, at 9:56 PM, Michael Roberts wrote: > unfortunately, it looks like this update has killed my build server. > This image can no longer file in scripts from the command line. > > it looks like asUrl was removed from String. was this intentional? > This is fixed in 11143... MC likes to omit methods that are recategorized. Marcus

Jan. 8, 2010