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

Re: [Pharo-project] Stumped on splitters

by Schwab,Wilhelm K

Gary, Thanks again for the examples. I was defeating the automatic mechanism with some extra morphs intended to aid in the layout. Take careful aim at foot; pull trigger ~:) Bill

Jan. 8, 2010

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

by Alexandre Bergel

I have to go now and I still do not have internet at home. I will work on this on Monday. Cheers, Alexandre On 8 Jan 2010, at 17:19, StÃ©phane Ducasse wrote: > 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 8, 2010

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

by Schwab,Wilhelm K

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

Jan. 8, 2010

Re: [Pharo-project] [ANN] Hudson continuous integration server support

by Lukas Renggli

> So here's a new idea. Keep the package-cache from the previous build, > and make sure the build image can make use of it -- I'm not sure of the > Gofer/Monticello details. Yeah, Gofer would benefit from the package cache. As far as I know Hudson however cleans the workspace with every new build. I don't know how the package cache could be saved over. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 8, 2010

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

by laurent laffont

> > > Btw, the laughing was because I've done that too many times to recount > myself :P > I suggest giving the Save/Discard/Cancel options instead. > +1 Laurent > > 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. 8, 2010

Re: [Pharo-project] [ANN] Hudson continuous integration server support

by Yanni Chiu

Lukas Renggli wrote: > I really don't want to repeat the same build multiple times. > Downloading and installing Monticello files is just dead slow. I find building from a local directory is quite fast. E.g. Gofer new directory: '/public/repo'; "squeaksource: 'KomHttpServer';" package: 'DynamicBindings'; package: 'KomServices'; package: 'KomHttpServer'; load. After a successful build, I copied the package-cache to the local repo directory. This was okay for debugging the build scripts, but doesn't work for building from the latest .mcz's. One idea, I've not tried yet, is to use rsync to pull the latest .mcz's down into the local repo. Then, for .mcz's that have no newer version, nothing has to be downloaded. Now that I think about, if you don't have control of the squeak source repository machine, then you can't do this. Also, to avoid filling up the local disk, some rsync filters would be needed, as well as a cron script to remove all but the latest version. Now it's getting too complicated. Following on that thought was to have Hudson monitor the repositories for new packages, and then kick off a build. I've not yet checked whether Hudson can do this. So here's a new idea. Keep the package-cache from the previous build, and make sure the build image can make use of it -- I'm not sure of the Gofer/Monticello details. -- Yanni

Jan. 8, 2010

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

by Henrik Sperre Johansen

On 08.01.2010 22:40, 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 > > Btw, the laughing was because I've done that too many times to recount myself :P I suggest giving the Save/Discard/Cancel options instead. Cheers, Henry

Jan. 8, 2010

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

by Henrik Sperre Johansen

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

Jan. 8, 2010

Re: [Pharo-project] Full Screen Margin Settings

by Alain Plantec

SLICE-Issue1762_FullScreenMarginMinShouldBe-5 is in InBox Alain Gary Chambers a Ã©crit : > I'll leave it to you then. BTW, nice job with the settings browser. > When I get a chance to put in the last Polymorph fixes it should help > with the drop-lists etc... > > Regards, Gary > > ----- Original Message ----- From: "Alain Plantec" > <alain.plantec(a)free.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Friday, January 08, 2010 8:13 PM > Subject: Re: [Pharo-project] Full Screen Margin Settings > > > Gary Chambers a Ã©crit : >> Alain, any chance of changing the range for Full screen margin in >> settings to start at -5? > Hi Gary, > No problem, its ok for me. > Alain >> That would really maxmise space by putting the window borders outside >> the World (and avoiding inadvertent resizing on maximised windows). >> >> Regards, Gary >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> 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] GUI how to screencast available

by laurent laffont

The ( not intuitive ) thing I spent a full hour to understand is on : LayoutFrame fractions: (0(a)0.99 corner: 1@1) 0.99 means "do not show splitter" as in SystemWindow>>addMorph:fullFrame: aLayoutFrame topFraction = 0 ifTrue: [aLayoutFrame topOffset: top] ifFalse: [aLayoutFrame topFraction = 1 ifFalse: [ aLayoutFrame topOffset: top + ProportionalSplitterMorph splitterWidth]]. May be PluggablePanelMorph>>addMorph:fullFrame: should have an equivalent implementation as in SystemWindow for more consistency .... but I've just start learning morphic so I think there's better ways to achieve the same layout as in the screencast. Laurent On Fri, Jan 8, 2010 at 9:58 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > I found that the addMorph: fullFrame: nil > to indicate that the button expand into it container is not really a sexy > interface. > > > 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 > > > _______________________________________________ > 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