- Pharo-dev - lists.pharo.org

Re: [Pharo-project] pharo on lion

by Esteban Lorenzano

Hi, yeah... I already have the fullscreen button working (not a hard work)... not on jenkins, because we need to update jenkins sdk to 10.7 before, but if anyone want to play with it, just ask for... I'm looking for "autosave" functionality... not sure it will work "as is", but I'm studying it... what you mean with "correct dock/menu handling", can you elaborate? cheers, Esteban El 08/09/2011, a las 11:35a.m., Sean P. DeNigris escribiÃ³: > I filed a Cog issue (http://code.google.com/p/cog/issues/detail?id=62) for > the following Lion fullscreen behavior: > * fullscreen button > * autosave > * correct dock/menu bar handling > > Sean > > -- > View this message in context: http://forum.world.st/pharo-on-lion-tp3682819p3798999.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Sept. 9, 2011

Re: [Pharo-project] Polymorph changes

by Gary Chambers

Just for reference, after (temporarily) fixing the system softowrare update issue (14023 ish) we have managed to get our product-under-development working with the latest updates. For anyone that is interested I can describe the potential issues and resloutions. Regards, Gary ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Friday, September 09, 2011 3:52 PM Subject: Re: [Pharo-project] Polymorph changes > Seems some stuff got missed out... attached .cs with remainder > > Also, if Igor is interested, I have some things to make corner rounding > and > shadows work properly (whilst still in the vein of the cleanup)... > > Regards, Gary > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, August 30, 2011 1:42 PM > Subject: Re: [Pharo-project] Polymorph changes > > > tx gary > is this for 1.4 (I guess). > I will integrate them. > > Stef > > On Aug 30, 2011, at 2:29 PM, Gary Chambers wrote: > >> Before I forget... >> A few changes to Polymorph and fixes for a few other packages attached. >> >> AlphaImageMorph supports #scaledAspect layout option (scales the image to >> fit whilst retaining aspect ratio) >> also class side accessor to set DefaultImage (I use the Pharo logo, >> appears in #exampleOtherControls) >> DialogItemsChooserUI centering rounded to avoid layout anomalies >> EditorFindReplaceDialogWindow initialized to position within usable area >> of display so not obscured by docks etc. >> GeneralScrollPane minWidth/minHeight when shrinkWrapping to target >> LazyListMorph mouse down row indication fixed >> PluggableListMorph fix for startDragExtended: mouse focus and wrapItem >> (when wrapSelector takes 0 args) >> ScrollPane will ignore mouse wheel iv not vertically scrollable (allows >> owners to handle) >> SystemWindow basicActivate no longer passivates old top window if no >> longer in world >> UITheme expander color no longer set to white by default >> nil labels for label groups now allow the associated control to fill >> whole width >> >> >> Also I've noticed that in latest updates, corner rounding no longer >> functions (affects scrollbars etc. in Watery 2 theme). >> >> Regards, Gary >> <PolymorphImprovements2.1.cs> > >

Sept. 9, 2011

[Pharo-project] Windows with nested menu

by Torsten Bergmann

Do we have examples for building windows with a top menu somewhere? Is there support for icons, checked menu items, accelerator keys, ...? Tx. Torsten -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone

Sept. 9, 2011

Re: [Pharo-project] Polymorph changes

by StÃ©phane Ducasse

thank I will integrate it. http://code.google.com/p/pharo/issues/detail?id=4781 Stef On Sep 9, 2011, at 4:52 PM, Gary Chambers wrote: > Seems some stuff got missed out... attached .cs with remainder > > Also, if Igor is interested, I have some things to make corner rounding and shadows work properly (whilst still in the vein of the cleanup)... > > Regards, Gary > > ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, August 30, 2011 1:42 PM > Subject: Re: [Pharo-project] Polymorph changes > > > tx gary > is this for 1.4 (I guess). > I will integrate them. > > Stef > > On Aug 30, 2011, at 2:29 PM, Gary Chambers wrote: > >> Before I forget... >> A few changes to Polymorph and fixes for a few other packages attached. >> >> AlphaImageMorph supports #scaledAspect layout option (scales the image to fit whilst retaining aspect ratio) >> also class side accessor to set DefaultImage (I use the Pharo logo, appears in #exampleOtherControls) >> DialogItemsChooserUI centering rounded to avoid layout anomalies >> EditorFindReplaceDialogWindow initialized to position within usable area of display so not obscured by docks etc. >> GeneralScrollPane minWidth/minHeight when shrinkWrapping to target >> LazyListMorph mouse down row indication fixed >> PluggableListMorph fix for startDragExtended: mouse focus and wrapItem (when wrapSelector takes 0 args) >> ScrollPane will ignore mouse wheel iv not vertically scrollable (allows owners to handle) >> SystemWindow basicActivate no longer passivates old top window if no longer in world >> UITheme expander color no longer set to white by default >> nil labels for label groups now allow the associated control to fill whole width >> >> >> Also I've noticed that in latest updates, corner rounding no longer functions (affects scrollbars etc. in Watery 2 theme). >> >> Regards, Gary >> <PolymorphImprovements2.1.cs> > > <MorePolymorphChanges.1.cs>

Sept. 9, 2011

Re: [Pharo-project] Immutability and Pharo

by StÃ©phane Ducasse

more bits on the object header and we will get it Note that JB already provided the code from newspeak. Stef On Sep 9, 2011, at 4:58 PM, Torsten Bergmann wrote: > ... comments? > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de >

Sept. 9, 2011

[Pharo-project] Immutability and Pharo

by Torsten Bergmann

... comments? -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

Sept. 9, 2011

Re: [Pharo-project] Polymorph changes

by Gary Chambers

Seems some stuff got missed out... attached .cs with remainder Also, if Igor is interested, I have some things to make corner rounding and shadows work properly (whilst still in the vein of the cleanup)... Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, August 30, 2011 1:42 PM Subject: Re: [Pharo-project] Polymorph changes tx gary is this for 1.4 (I guess). I will integrate them. Stef On Aug 30, 2011, at 2:29 PM, Gary Chambers wrote: > Before I forget... > A few changes to Polymorph and fixes for a few other packages attached. > > AlphaImageMorph supports #scaledAspect layout option (scales the image to > fit whilst retaining aspect ratio) > also class side accessor to set DefaultImage (I use the Pharo logo, > appears in #exampleOtherControls) > DialogItemsChooserUI centering rounded to avoid layout anomalies > EditorFindReplaceDialogWindow initialized to position within usable area > of display so not obscured by docks etc. > GeneralScrollPane minWidth/minHeight when shrinkWrapping to target > LazyListMorph mouse down row indication fixed > PluggableListMorph fix for startDragExtended: mouse focus and wrapItem > (when wrapSelector takes 0 args) > ScrollPane will ignore mouse wheel iv not vertically scrollable (allows > owners to handle) > SystemWindow basicActivate no longer passivates old top window if no > longer in world > UITheme expander color no longer set to white by default > nil labels for label groups now allow the associated control to fill > whole width > > > Also I've noticed that in latest updates, corner rounding no longer > functions (affects scrollbars etc. in Watery 2 theme). > > Regards, Gary > <PolymorphImprovements2.1.cs>

Sept. 9, 2011

Re: [Pharo-project] [Vm-beginners] Fwd: Oops - I put a halt in a startup method

by Sean P. DeNigris

Mariano Martinez Peck wrote: > > Sean: it may be difficult/impossible. But....you may want to try invoking > the function say printOop() from the XCode console. > Thanks Mariano. When I put a breakpoint in Xcode with this particular image, the image takes over my whole screen (may be because it's in fullscreen) and I have to hard reset. So instead of printing the class name, I'm trying to get it as a string, so I can put an if to skip on the desired call. I'm working on it, but my C is very rusty and I'm fumbling with the string handling. Mariano Martinez Peck wrote: > > If you read my post: > http://marianopeck.wordpress.com/2011/04/23/how-to-debug-the-vm/ > Very nice. I actually saw a lot of interesting VM-related info on your blog that I added to my reading list. -- View this message in context: http://forum.world.st/Re-Vm-beginners-Fwd-Oops-I-put-a-halt-in-a-startup-me… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 9, 2011

Re: [Pharo-project] [Seaside] Announcements/Seaside continuations collision in newer cog vm's

by StÃ©phane Ducasse

:) And this is already fixed and integrated :) Thanks you all. Stef On Sep 9, 2011, at 3:22 PM, Tudor Girba wrote: > Henrik provided a better answer than mine: > > On 9 Sep 2011, at 14:44, Henrik Sperre Johansen wrote: > >> Which is why it was changed, after discussion with Lukas. >> It only forks UnhandledErrors now, before delivering the remaining. >> As long as there is no abnormal termination, it will work just as before. >> If any subscribers would abnormally terminate though, the ifCurtailed: kicks in, and (was supposed to) ensure delivers to remaining subscribers. >> >> If something in Seaside relies on such behaviour (like terminating current process in order for subsequent subscribers to not receive the announcement) that will be broken. >> I don't think messing with announcement delivery should be considered a good control flow mechanism though. >> >> What Esteban encountered as an error on some VM's was a pure bug I made in the ifCurtailed: block (by using after: instead of copyAfter:), and had nothing to do with forking. >> Why some VM's considered the delivery abnormally terminated, while others didn't, I have no idea though... >> (The error he got only happens when the ifCurtailed block is invoked). >> >> Cheers, >> Henry > > Cheers, > Doru > > > On 9 Sep 2011, at 15:20, Sebastian Sastre wrote: > >> Isn't the plain events mechanism forkless and essential to the core of the system already? >> >> if you introduce that fork you break not only seaside but all artifacts of all the people that will rightly assume the current process between event and reaction is the same >> >> >> >> On Sep 9, 2011, at 7:13 AM, Tudor Girba wrote: >> >>> Igor and Stef can provide more details. >>> >>> The reason for forking is that even if one announcement breaks, the others should still be announced. Announcements are used for the functioning of the core of the system and this means that even if you register new objects, the core mechanisms (such as package management) should continue to work. >>> >>> It would be great if Seaside would work with these, and now depend on another framework. >>> >>> Cheers, >>> Doru >>> >>> >>> On 9 Sep 2011, at 06:38, Philippe Marschall wrote: >>> >>>> 2011/9/8 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>> Hi, >>>>> (yep, I'm copying tree lists because I think is a vm problem, but can be a seaside problem, or a pharo problem) >>>>> (yes, it can be MY problem too... but I don't think so... ;) >>>>> >>>>> I'm having this really, really strange problem (because it was working before, and I do not change anything... so, maybe a change in latest changes on pharo 1.3, the version I'm using, is the cause)... >>>> >>>> The announcements in the latest Pharo 1.3 don't work with Seaside >>>> anymore. For some reason they fork them instead of running them in an >>>> exception handler. >>>> >>>> Cheers >>>> Philippe >>>> _______________________________________________ >>>> seaside mailing list >>>> seaside(a)lists.squeakfoundation.org >>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >>> -- >>> www.tudorgirba.com >>> >>> "Yesterday is a fact. >>> Tomorrow is a possibility. >>> Today is a challenge." >>> >>> >>> >>> _______________________________________________ >>> seaside mailing list >>> seaside(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> sebastian >> >> o/ >> >> >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > -- > www.tudorgirba.com > > "Be rather willing to give than demanding to get." > > > >

Sept. 9, 2011

Re: [Pharo-project] [Seaside] Announcements/Seaside continuations collision in newer cog vm's

by Tudor Girba

Henrik provided a better answer than mine: On 9 Sep 2011, at 14:44, Henrik Sperre Johansen wrote: > Which is why it was changed, after discussion with Lukas. > It only forks UnhandledErrors now, before delivering the remaining. > As long as there is no abnormal termination, it will work just as before. > If any subscribers would abnormally terminate though, the ifCurtailed: kicks in, and (was supposed to) ensure delivers to remaining subscribers. > > If something in Seaside relies on such behaviour (like terminating current process in order for subsequent subscribers to not receive the announcement) that will be broken. > I don't think messing with announcement delivery should be considered a good control flow mechanism though. > > What Esteban encountered as an error on some VM's was a pure bug I made in the ifCurtailed: block (by using after: instead of copyAfter:), and had nothing to do with forking. > Why some VM's considered the delivery abnormally terminated, while others didn't, I have no idea though... > (The error he got only happens when the ifCurtailed block is invoked). > > Cheers, > Henry Cheers, Doru On 9 Sep 2011, at 15:20, Sebastian Sastre wrote: > Isn't the plain events mechanism forkless and essential to the core of the system already? > > if you introduce that fork you break not only seaside but all artifacts of all the people that will rightly assume the current process between event and reaction is the same > > > > On Sep 9, 2011, at 7:13 AM, Tudor Girba wrote: > >> Igor and Stef can provide more details. >> >> The reason for forking is that even if one announcement breaks, the others should still be announced. Announcements are used for the functioning of the core of the system and this means that even if you register new objects, the core mechanisms (such as package management) should continue to work. >> >> It would be great if Seaside would work with these, and now depend on another framework. >> >> Cheers, >> Doru >> >> >> On 9 Sep 2011, at 06:38, Philippe Marschall wrote: >> >>> 2011/9/8 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>> Hi, >>>> (yep, I'm copying tree lists because I think is a vm problem, but can be a seaside problem, or a pharo problem) >>>> (yes, it can be MY problem too... but I don't think so... ;) >>>> >>>> I'm having this really, really strange problem (because it was working before, and I do not change anything... so, maybe a change in latest changes on pharo 1.3, the version I'm using, is the cause)... >>> >>> The announcements in the latest Pharo 1.3 don't work with Seaside >>> anymore. For some reason they fork them instead of running them in an >>> exception handler. >>> >>> Cheers >>> Philippe >>> _______________________________________________ >>> seaside mailing list >>> seaside(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> -- >> www.tudorgirba.com >> >> "Yesterday is a fact. >> Tomorrow is a possibility. >> Today is a challenge." >> >> >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > sebastian > > o/ > > > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -- www.tudorgirba.com "Be rather willing to give than demanding to get."

Sept. 9, 2011