- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Unsubscribing for Announcements

by Schwab,Wilhelm K

Of course. But when the status quo has been robustly defended, it seems reasonable to lobby for change as a start. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] Sent: Tuesday, January 18, 2011 2:22 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Unsubscribing for Announcements Yes but having good weakstructure will not arrive by accident. On Jan 17, 2011, at 4:34 PM, Schwab,Wilhelm K wrote: > Two comments: > > (1) there needs to be a way to unregister interest; > (2) the registrations need to be weak so that (1) is largely optional. > > If Dolphin has a weakness, it is that failure of an MVP triad to open can leave the system in a confused state. Morphic appears to be a little more robust about that, though in fairness, I do not push Pharo's GUI nearly as hard as I have Dolphin's. If in doubt, some type of #ifCurtailed: or similar protection around the assembly of a complex morph might be a good idea. > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Sean P. DeNigris [sean(a)clipperadams.com] > Sent: Monday, January 17, 2011 1:18 AM > To: pharo-project(a)lists.gforge.inria.fr > Subject: [Pharo-project] Unsubscribing for Announcements > > I really like Announcements! It's so much easier to update complex GUIs when > you can pass state :) > > I hit one glitch when unsubscribing... The CollaborActive book suggests > unsubscribing in #delete. For complex UIs, this doesn't seem to work > because #delete is only called for the one morph that was deleted, not for > its submorphs (which may need to unsubscribe). > > I tried this: > MyMorph>>delete > super delete. "Must come first. Deleting a submorph before self = > emergency evaluator" > aSubmorphThatNeedsToUnsubscribe delete. > > SubmorphMentionedAbove>>delete > self inventory announcer unsubscribe: self. > super delete. > > > But it seems like a lot of work and coupling. Is there no hook that is > guaranteed to be called when a morph is going away - i.e. it or a morph in > the owner chain is being deleted? > > Thanks. > Sean > -- > View this message in context: http://forum.world.st/Unsubscribing-for-Announcements-tp3220751p3220751.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

Jan. 18, 2011

Re: [Pharo-project] list on he fly selection :)

by Tudor Girba

I am not sure where it should work, but I tried in Pharo 1.2 and it does not work. First, there is a "self self". Second, even if I fix this one, I still get a DNU for OnTheFlySelectionPluggableListMorph>>lastKeystrokes. Cheers, Doru On 18 Jan 2011, at 20:21, StÃ©phane Ducasse wrote: > close your eyes and imagine that you can just type as to get all the methods starting with as* > without extra shortcut whatever.... > same for classes, packages... of course. > > Stef > > On Jan 18, 2011, at 4:16 PM, Alexandre Bergel wrote: > >> Just tried. I could not immediately figure out what is the difference with the "Find Class" panel (pressing Cmd-f in OB)? >> >> Cheers, >> Alexandre >> >> >> On 18 Jan 2011, at 12:00, StÃ©phane Ducasse wrote: >> >>> Hi guys >>> >>> I'm sure that some of you will really like to type on that list and see it auto selectioning its elements.... >>> >>> Gofer it >>> squeaksource: 'DirtyExperiments'; >>> package: 'DirtyExperiments'; >>> load >>> >>> | test | >>> test := DummyTest on: (Smalltalk allClasses). >>> test openInWorld >>> >>> Of course I would love to have that for a lot of lists..... :) >>> >>> Thanks Benjamin for this first version :) >>> Stef >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> > > -- www.tudorgirba.com "Sometimes the best solution is not the best solution."

Jan. 18, 2011

Re: [Pharo-project] Surprising binary messages!

by StÃ©phane Ducasse

Yes man. Stef > You're right. It looks like I need to sleep more :-D > > Noury

Jan. 18, 2011

Re: [Pharo-project] Unsubscribing for Announcements

by StÃ©phane Ducasse

Yes but having good weakstructure will not arrive by accident. On Jan 17, 2011, at 4:34 PM, Schwab,Wilhelm K wrote: > Two comments: > > (1) there needs to be a way to unregister interest; > (2) the registrations need to be weak so that (1) is largely optional. > > If Dolphin has a weakness, it is that failure of an MVP triad to open can leave the system in a confused state. Morphic appears to be a little more robust about that, though in fairness, I do not push Pharo's GUI nearly as hard as I have Dolphin's. If in doubt, some type of #ifCurtailed: or similar protection around the assembly of a complex morph might be a good idea. > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Sean P. DeNigris [sean(a)clipperadams.com] > Sent: Monday, January 17, 2011 1:18 AM > To: pharo-project(a)lists.gforge.inria.fr > Subject: [Pharo-project] Unsubscribing for Announcements > > I really like Announcements! It's so much easier to update complex GUIs when > you can pass state :) > > I hit one glitch when unsubscribing... The CollaborActive book suggests > unsubscribing in #delete. For complex UIs, this doesn't seem to work > because #delete is only called for the one morph that was deleted, not for > its submorphs (which may need to unsubscribe). > > I tried this: > MyMorph>>delete > super delete. "Must come first. Deleting a submorph before self = > emergency evaluator" > aSubmorphThatNeedsToUnsubscribe delete. > > SubmorphMentionedAbove>>delete > self inventory announcer unsubscribe: self. > super delete. > > > But it seems like a lot of work and coupling. Is there no hook that is > guaranteed to be called when a morph is going away - i.e. it or a morph in > the owner chain is being deleted? > > Thanks. > Sean > -- > View this message in context: http://forum.world.st/Unsubscribing-for-Announcements-tp3220751p3220751.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

Jan. 18, 2011

Re: [Pharo-project] Xtreams-Xtras: hashing and HMAC

by Sven Van Caekenberghe

On 18 Jan 2011, at 19:57, mkobetic(a)gmail.com wrote: > "Sven Van Caekenberghe"<sven(a)beta9.be> wrote: >>> The code is in Xtreams-Xtras and Xtreams-XtrasTests (note that you'll have to load FFI!). I tested it on Pharo 1.2 beta with both cog vm and standard vm. There are few test failures with file terminals that don't seem to like to be closed twice. Should be an easy fix. >> >> Could it be that you forgot to check in #hashing: for read streams ? Or did I load the code while you were updating ? > > Ah, my bad, I misspelled the category on XTReadStream and so it was omitted. No problem. > I didn't find a way to browse a "package" in Pharo 1.2 so I'm struggling a bit to keep the categories in line. Hmm, click the 'Browse' button in either the Monticello Browser or the Repository Browser with the correct package selected ? But I guess you know that as well... > Thanks for the note, a new version of Xtras is on squeaksource. Works much better, down to 7 failures out of 785! The problem is the one I reported earlier: XTFileReadingWritingTest expecting a read stream to be aware of data written to a file after it was opened. This does not seem to work on Mac OS X. Sven

Jan. 18, 2011

Re: [Pharo-project] list on he fly selection :)

by StÃ©phane Ducasse

close your eyes and imagine that you can just type as to get all the methods starting with as* without extra shortcut whatever.... same for classes, packages... of course. Stef On Jan 18, 2011, at 4:16 PM, Alexandre Bergel wrote: > Just tried. I could not immediately figure out what is the difference with the "Find Class" panel (pressing Cmd-f in OB)? > > Cheers, > Alexandre > > > On 18 Jan 2011, at 12:00, StÃ©phane Ducasse wrote: > >> Hi guys >> >> I'm sure that some of you will really like to type on that list and see it auto selectioning its elements.... >> >> Gofer it >> squeaksource: 'DirtyExperiments'; >> package: 'DirtyExperiments'; >> load >> >> | test | >> test := DummyTest on: (Smalltalk allClasses). >> test openInWorld >> >> Of course I would love to have that for a lot of lists..... :) >> >> Thanks Benjamin for this first version :) >> Stef > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

Jan. 18, 2011

Re: [Pharo-project] Metacello Help book in Pharo-Dev

by StÃ©phane Ducasse

Yes we fix it. Stef On Jan 18, 2011, at 6:49 PM, Dale Henrichs wrote: > On 01/18/2011 05:37 AM, Torsten Bergmann wrote: >>> the current behavior of ConfigurationOfPharo loads Metacello >>> completly, included packages like Metacello-Help and Metacello-ProfStef >> >> OK, then its fine >> >>> someone can update that to 1.0-beta.28 and you will see the new versions. >> >> When I switch to Metacello "1.0-beta.28" in ConfigurationOfPharo >> then it fails while loading OB. >> >> A conflict since Metacello uses OB too, maybe in another version? >> >> Thx >> T. > > Torsten, > > I had trouble using OB into the very latest Pharo1.2 core over the weekend, but it was working fine in older, but recent versions ... it looked to me like something got balled up involving SHOUT and morphic ... > > The symbolic versions feature in Metacello 1.0-beta.28 is designed to help solve the "using the correct version in Pharo1.2" problem, but 1.0-beta.28 had to be released first:) > > Dale >

Jan. 18, 2011

Re: [Pharo-project] [ANN 1.2] pre-build Core 1.2rc1 #12311

by StÃ©phane Ducasse

tx marcus. Stef > > > https://gforge.inria.fr/frs/download.php/28162/PharoCore-1.2rc1-12311.zip > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

Jan. 18, 2011

Re: [Pharo-project] Pharo packages and Settings/Preferences questions

by StÃ©phane Ducasse

On Jan 18, 2011, at 2:51 PM, Benoit St-Jean wrote: > Two quick questions this morning : > > 1) If I am using a package from squeaksource.com and this package only works with Squeak now (methods have been removed from Pharo, methods only exists in Squeak, different behavior in Pharos vs Squeak, whatever the reason), what is the preferred way of committing a works-in-Pharo version to SqueakSource ? I wouldn't want the same problem happening to Squeakers, i.e. someone loads this package in Squeak and discover that the new version only works in Pharo now! Perhaps the answer is "Pharo needs its own SqueakSource repository" but in the meantime, what should I do and how? May be postfix the package name with -Pharo > 2) Is there a preferred way of adding settings/preferences to the Pharo environment, if so can someone redirect me to the proper documentation/link on how-to-do-it ? I'm a bit confused as to what I'd have to use since there seems to be some old (?!?!) Preferences stuff still present in Pharo. Probably only in the external package. Please do not use Preferences. We will remove the class probably in 1.3. > In my case, I'd like to be able to specify my own parseableSourceCodeTemplate instead of the default one. Let us know if this is answering your question. I suggest that you package your setting in a separate package. > > ----------------- > Benoit St-Jean > Yahoo! Messenger: bstjean > A standpoint is an intellectual horizon of radius zero. > (Albert Einstein) > >

Jan. 18, 2011

Re: [Pharo-project] [squeak-dev] Re: Xtreams-Xtras: hashing and HMAC

by mkobetic＠gmail.com

"Sven Van Caekenberghe"<sven(a)beta9.be> wrote: > > The code is in Xtreams-Xtras and Xtreams-XtrasTests (note that you'll have to load FFI!). I tested it on Pharo 1.2 beta with both cog vm and standard vm. There are few test failures with file terminals that don't seem to like to be closed twice. Should be an easy fix. > > Could it be that you forgot to check in #hashing: for read streams ? Or did I load the code while you were updating ? Ah, my bad, I misspelled the category on XTReadStream and so it was omitted. I didn't find a way to browse a "package" in Pharo 1.2 so I'm struggling a bit to keep the categories in line. Thanks for the note, a new version of Xtras is on squeaksource.

Jan. 18, 2011