April 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 4036 in pharo: Please update Help> Announcements tutorial

by StÃ©phane Ducasse

Great! I asked Ben and Igor to think about an announcement chapter for pharo by example vol 2. So this help will be a excellent start. Stef > This section should probably also explain the concept of the subscriber, ie. the thing you need to unregister for the announcement to stop being sent. > > For message sends (on:send:to:) it is the receiver (to: argument), for blocks (on: do:) it's the object where block is defined. > #on:do:for:/#when:do:for, which lets you specify another object as subscriber for block actions, is currently not implemented. > It's also a difference from the VW implementation, where when:do: uses the action block itself as subscriber, so you're much more likely to need on:do:for:. > > Cheers, > Henry > > > On 18.04.2011 11:13, Henrik Sperre Johansen wrote: >> On 18.04.2011 10:47, Fernando Olivero wrote: >>> To remove the subscription you can evaluate: World announcer initialize. >>> >>> Maybe the tutorial should add (pesudo code): >>> >>> MyStuff>>initialize >>> World announcer >>> on: WindowOpened >>> send: #showOnTranscript >>> to: self >>> SystemAnnouncer on:#classremove send:#release: to: self. >>> >>> MyStuff>>release: anAnn >>> World announcer unsuscribe: self. >>> >>> MyStuff>>showOnTranscript >>> Transcript show: 'A new window was opened';cr >>> >>> I can update the tutorial if people agrees on the pseudo code. >>> >>> >>> To open a transcript evaluate: TranscriptMorph openWindow >>> (decoupled Transcript from Morphic, so directly ask the view to open itself) >>> >>> Fernando >> >> The old tutorial was weak mainly because it didn't tell you how to unsubscribe. >> >> >> Here's a few examples of that: >> >> "Unsubscribe automatically with weak announcements." >> World announcer weak >> on: WindowOpened >> send: #shownOnTranscript >> to: self. >> >> Then example in Workspace >> obj := self new. >> "Open a window, and see Transcript printing" >> obj := nil. >> "Open a window, you may see Transcript printing (depending on finalization)" >> "Now force finalization" >> Smalltalk garbageCollect. >> "Open a window, now see no transcript prints." >> >> >> "Automatically unregister after handling one announcement" >> initialize >> World announcer >> on: WindowOpened >> do: [:ann: announcer | self shownOnTranscript. >> announcer unsubscribe: self.] >> >> "Unregister specifically after some time" >> initialize >> World announcer >> on: WindowOpened >> send: #shownOnTranscript >> to: self. >> >> release >> World announcer unsubscribe: self. >> >> "Using same action block registered for multiple announcers, unregister specifially at a specific time" >> initialize >> handlesAnnoucements := true. >> actionBlock:= [:ann :announcer | >> handlesAnnouncement >> ifTrue: [self shownOnTranscript] >> ifFalse: [announcer unsubscribe: self]]. >> World announcer on: WindowOpened do: actionBlock. >> AnnouncerTest announcer on: TestCaseEnded do: actionBlock. >> >> release >> handlesAnnouncements := false. >> >> >> >> >> >> > >

April 19, 2011

Re: [Pharo-project] Transcript rant

by StÃ©phane Ducasse

I know all that :) I favor changes. Now theadSafeTranscript was thread safe. How can I get the old transcript because I need to get fast for debugging an ugly bug. > From the release notes of CUIS: > "New Transcript > Fast (Calls return quickly) > Fast (Updates are immediate) > Thread safe > Can log to file in addition to Display > Display output is optional (for headless images) > Can work on a bare bones image (Doesn't need UI, dependency, events, > processes) > Optional morphic window for seamless integration in Morphic > UI framework agnostic. Can be used to debug Morphic, even with the > morphic window open, without crashing the image! > No longer a text editor. Display is read only." > > The idea of the current Transcript are, not to use a standart widget > for decoupling from Morphic, in case of errors the transcript still > remains functional. > > I propose adding a new transcript morph, that has the previous > functionality ( cut and paste ), but keep the new transcript model ( > as in the ISSUE 3948). > > Fernando > > On Sun, Apr 17, 2011 at 6:59 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> How can I get the old transcript? >> >> Stef >> >> On Apr 7, 2011, at 9:58 AM, Fernando Olivero wrote: >> >>> I propose some modifications to the Transcript as a (singleton) class, >>> and revert to the use of TranscriptModel. >>> >>> See the latest post on 3948: Transcript and ThreadedTranscript needs >>> to be merged. >>> >>> Fernando >>> >>> On Wed, Apr 6, 2011 at 10:39 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>> On 6 April 2011 20:24, <csrabak(a)bol.com.br> wrote: >>>>> Em 06/04/2011 09:07, Igor Stasenko <siguctua(a)gmail.com> escreveu: >>>>>>> On 6 April 2011 13:54, Fernando Olivero <fernando.olivero(a)usi.ch> >>>>> wrote: >>>>> >>>>>>> Hi Stef, i will as an initial step take Igor's suggestion and make >>>>>>> Transcript a global wich points to an instance of TranscriptModel >>>>>>> ( the new name i propose for the current class taken from CUIS). >>>>>>> I still believe that composition is better then inheritance for >>>>>>> handling different behaviors of the Transcript, so i argue against >>>>>>> making it a subclass of WriteStream and making it polymorphic with >>>>>>> a write stream instead. >>>>>>> >>>>>> That's totally not my concern. As long as thing which sits there >>>>>> responds to writestream protocol , i don't care about rest. >>>>>> >>>>> >>>>> Would it make sense then to lift the methods from {write}stream and >>>>> put then in a Trait so the composition is made through reuse of code? >>>>> >>>>> My 0.0199999.... >>>> >>>> hehe.. yes, but if to follow this road every time you need to do small >>>> improvement, >>>> then at some day you will discover that you rewriting whole system >>>> from scratch :) >>>> >>>>> >>>>> -- >>>>> Cesar Rabak >>>> >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko AKA sig. >>>> >>>> >>> >> >> >

April 19, 2011

Re: [Pharo-project] Networking change in Pharo 1.2?

by Chris Muller

Thank you too; it was a bruising problem I'm glad to have it identified. On Mon, Apr 18, 2011 at 12:21 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Apr 18, 2011, at 7:14 PM, Chris Muller wrote: > >>> The only change to NetNameResolver was this: >>> >>> Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=1853 >> >> Reverting this change fixed it. >> > > > Thanks! I have opend the issue again for 1.2.2 and 1.3 > > Â Â Â Â Marcus > > > -- > Marcus Denker Â -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

April 19, 2011

Re: [Pharo-project] [ANN] new mailinglist for tracker mails

by Stephan Eggermont

Marcus wrote: >The mails from the google tracker now go to this list: >http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker >in turn, this means the traffic on the pharo-project list should be a bit more managable. Thank you. Stephan

April 18, 2011

Re: [Pharo-project] [TODO 1.2.2] Steps to a 1.2.2 Release

by Alexandre Bergel

Impressive... Alexandre On 18 Apr 2011, at 16:36, Lukas Renggli wrote: > I can confirm that OmniBrowser works in Pharo 1.2 and Pharo 1.3 with > refactoring tools, syntax highlighting and code completion. All tests > pass in the latest versions of both images: > > 2131 run, 2130 passes, 1 expected failures, 0 failures, 0 errors, > 0 unexpected passes > > The following two scripts load the necessary packages (and tests): > > https://github.com/renggli/builder/blob/master/scripts/omnibrowser.st > https://github.com/renggli/builder/blob/master/scripts/omnibrowser-tests.st > > Cheers, > Lukas > > On 18 April 2011 19:25, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> >> >> On Mon, Apr 18, 2011 at 7:21 PM, Marcus Denker <marcus.denker(a)inria.fr> >> wrote: >>> >>> On Apr 18, 2011, at 7:18 PM, Mariano Martinez Peck wrote: >>> >>>> >>>> >>>> On Mon, Apr 18, 2011 at 7:05 PM, Marcus Denker <marcus.denker(a)inria.fr> >>>> wrote: >>>> >>>> Core >>>> -> Nothing to be done. >>>> >>>> Full: >>>> -> Build is broken: >>>> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/232/console >>>> >>>> Hopefully someone will sit, spend a couple of hours and merge latest >>>> changes from Lukas OB and ours. >>> >>> Why merge? Lukas maintains OB and I am sure his version is fine for 1.2... >>> >>> So let's just load it. We just had to temporary fork to make it usable >>> while 1.2 was not yet relased. >>> >> >> Yes, true. Sorry, I was thinking about 1.3. Yes, for Pharo 1.2.2 it should >> be easier, I guess almost the same we released for 1.2.1 >> >>> >>> Marcus >>> >>> >>> -- >>> Marcus Denker -- http://www.marcusdenker.de >>> INRIA Lille -- Nord Europe. Team RMoD. >>> >>> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 18, 2011

Re: [Pharo-project] [TODO 1.2.2] Steps to a 1.2.2 Release

by Sven Van Caekenberghe

Great! On 18 Apr 2011, at 22:36, Lukas Renggli wrote: > I can confirm that OmniBrowser works in Pharo 1.2 and Pharo 1.3 with > refactoring tools, syntax highlighting and code completion. All tests > pass in the latest versions of both images: > > 2131 run, 2130 passes, 1 expected failures, 0 failures, 0 errors, > 0 unexpected passes

April 18, 2011

Re: [Pharo-project] [TODO 1.2.2] Steps to a 1.2.2 Release

by Lukas Renggli

I can confirm that OmniBrowser works in Pharo 1.2 and Pharo 1.3 with refactoring tools, syntax highlighting and code completion. All tests pass in the latest versions of both images: 2131 run, 2130 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes The following two scripts load the necessary packages (and tests): https://github.com/renggli/builder/blob/master/scripts/omnibrowser.st https://github.com/renggli/builder/blob/master/scripts/omnibrowser-tests.st Cheers, Lukas On 18 April 2011 19:25, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Mon, Apr 18, 2011 at 7:21 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: >> >> On Apr 18, 2011, at 7:18 PM, Mariano Martinez Peck wrote: >> >> > >> > >> > On Mon, Apr 18, 2011 at 7:05 PM, Marcus Denker <marcus.denker(a)inria.fr> >> > wrote: >> > >> > Core >> > Â Â Â Â -> Nothing to be done. >> > >> > Full: >> > Â Â Â Â -> Build is broken: >> > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/232/console >> > >> > Hopefully someone will sit, spend a couple of hours and merge latest >> > changes from Lukas OB and ours. >> >> Why merge? Lukas maintains OB and I am sure his version is fine for 1.2... >> >> So let's just load it. We just had to temporary fork to make it usable >> while 1.2 was not yet relased. >> > > Yes, true. Sorry, I was thinking about 1.3. Yes, for Pharo 1.2.2 it should > be easier, I guess almost the same we released for 1.2.1 > >> >> Â Â Â Â Marcus >> >> >> -- >> Marcus Denker Â -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Lukas Renggli www.lukas-renggli.ch

April 18, 2011

Re: [Pharo-project] About float: new chapter looking for reader and contributors

by Nicolas Cellier

Hi Stephane, did you notice https://github.com/SquareBracketAssociates/PharoByExample-english/pulls ? Nicolas 2011/4/14 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > On Apr 14, 2011, at 11:31 AM, Nicolas Cellier wrote: > >> I created a git account last night but must install latex on my mac. > > you can also just write and I will latex it. There is no problem. > >> I don't have your rythm :) > > :) > But you are doing a lot of things too. > Sometimes I have the impression that I could be more focused and it would be better > but the system does not give me this chance. > Stef > > >

April 18, 2011

[Pharo-project] [COTDC] 50 - LongTestCase

by laurent laffont

Today: LongTestCase Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

April 18, 2011

Re: [Pharo-project] [COTDC] 49 - ClassFactoryWithOrganization

by laurent laffont

Thanks Alex and Stef Laurent. On Mon, Apr 18, 2011 at 2:27 AM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > I am similar to ClassFactoryForTestCase (i.e., I can be used in place of a > ClassFactoryForTestCase), expect that classes may be created on a specific > class category. > > Alexandre > > > On 17 Apr 2011, at 15:36, StÃ©phane Ducasse wrote: > > > I'm a class to create classes with a category. I'm only used by Tests. > > > > > > On Apr 17, 2011, at 9:26 PM, laurent laffont wrote: > > > >> ClassFactoryWithOrganization > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > >

April 18, 2011