- Pharo-dev - lists.pharo.org

Re: [Pharo-project] News about the consortium :)

by laurent laffont

Great ! Laurent. On Thu, Jul 14, 2011 at 10:29 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > Hi guys > > just to let you know that INRIA validated our idea to build a consortium. > We are checking the details with them. The discussion will probably > continue in September but this is a good news > since they are ready to finance an engineer. Now we have to sort out > everything. > > Stef >

July 14, 2011

[Pharo-project] getting notice of text selection

by Tudor Girba

Hi, How can I get a notice when the selection changes in a PluggableTextMorph? I see no obvious hook. Cheers, Doru -- www.tudorgirba.com "Obvious things are difficult to teach."

July 14, 2011

Re: [Pharo-project] shortcuts in PluggableTextMorph

by Tudor Girba

Hi, Ok, I found a solution (inspired by OB): - GLMPluggableTextMorph subclasses PluggableTextMorph - GLMTextMorphForEditView subclasses TextMorphForEditView - GLMPluggableTextMorph>>textMorphClass ^ GLMTextMorphForEditView - GLMTextMorphForEditView>>keyStroke: anEvent | isHandledByModel | isHandledByModel := self editView model keystroke: anEvent from: self editView. isHandledByModel ifFalse: [ super keyStroke: anEvent ] This is messy, to put it mildly :). Are there other options? Cheers, Doru On 13 Jul 2011, at 13:07, Lukas Renggli wrote: > What about using the keyDown event then? > > Lukas > > On 13 July 2011 13:05, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Yes. But as I said, the value of "self text" is already modified when it gets to the #keystroke:from: >> >> GLMTextModel>>keystroke: anEvent from: aMorph >> self text inspect. >> ^ true >> >> So, I am stuck again :(. >> >> Doru >> >> >> >> On 13 Jul 2011, at 11:22, Lukas Renggli wrote: >> >>> And you return true, if you handled the request? >>> >>> On 13 July 2011 11:18, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> On 13 Jul 2011, at 11:08, Lukas Renggli wrote: >>>> >>>>>> This is what I am doing right now and it does not work: >>>>>> (PluggableTextMorph on: textModel ...) >>>>>> onKeyStrokeSend: #keystroke:from: to: textModel >>>>>> ... >>>>> >>>>> You have to attach your handler on the text morph itself, not on the >>>>> pluggable morph which is just a wrapper. >>>> >>>> This is just a helper method in PluggableTextMorph that does what you propose: >>>> >>>> PluggableTextMorph>>onKeyStrokeSend: sel to: recipient >>>> textMorph on: #keyStroke send: sel to: recipient. >>>> >>>> But this still does not seem to work. >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> >>>>> Lukas >>>>> >>>>> -- >>>>> Lukas Renggli >>>>> www.lukas-renggli.ch >>>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Speaking louder won't make the point worthier." >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >> >> -- >> www.tudorgirba.com >> >> "Be rather willing to give than demanding to get." >> >> >> >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

July 14, 2011

Re: [Pharo-project] crLog:

by StÃ©phane Ducasse

On Jul 13, 2011, at 11:09 PM, Nicolas Cellier wrote: > I noticed that crLog: is sometimes sent to Transcript. > This completely ruin the goal of eliminating direct reference to Transcript, doesn't it ? indeed crLog and friends should be sent to self > Another thing, I couldn't find a reference to crLog: in the issue tracker... I probably forgot to add it :) I was may be in a rush mode no it is there http://code.google.com/p/pharo/issues/detail?id=4264 http://code.google.com/p/pharo/issues/detail?id=4302 > I'm really not sure how the issue tracker can be used to track changes back (maybe it simply can't). the google search engine of the bugtracker is bad bad bad bad only find full name :( terrible software Now nicolas I would love to remove all the Transcript refs :) > > Nicolas

July 14, 2011

Re: [Pharo-project] Tests package is missing in the Pharo14 repository

by Pavel Krivanek

ok, thank you, I hope that no other package is missing. -- Pavel On Thu, Jul 14, 2011 at 10:34 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > ok done. > > pavel I added you as a commiter to pharo1.4 > is it ok for you? > > Stef > > On Jul 14, 2011, at 10:16 AM, Pavel Krivanek wrote: > >> Please, >> >> can somebody copy latests Tests package from Pharo repository to >> Pharo14 repository too? >> >> -- Pavel >> > > >

July 14, 2011

Re: [Pharo-project] Tests package is missing in the Pharo14 repository

by StÃ©phane Ducasse

ok done. pavel I added you as a commiter to pharo1.4 is it ok for you? Stef On Jul 14, 2011, at 10:16 AM, Pavel Krivanek wrote: > Please, > > can somebody copy latests Tests package from Pharo repository to > Pharo14 repository too? > > -- Pavel >

July 14, 2011

[Pharo-project] News about the consortium :)

by StÃ©phane Ducasse

Hi guys just to let you know that INRIA validated our idea to build a consortium. We are checking the details with them. The discussion will probably continue in September but this is a good news since they are ready to finance an engineer. Now we have to sort out everything. Stef

July 14, 2011

Re: [Pharo-project] how to get new inspector running in 1.4

by StÃ©phane Ducasse

yes another todo. May be camillo should give a try and we integrate it. Stef On Jul 13, 2011, at 7:35 PM, Igor Stasenko wrote: > As i already told to Camillo, new inspector needs refactoring for > integrating into 1.4 > it should not use ToolSet and instead it should register itself as > #inspector in tool registry. > > Smalltalk tools register: NewInspector as: #inspector > > in its #registerToolsOn: > > (Note that Inspector also registers itself as #inspector, > so, its the order how they are installed will affect which one is used) > > Maybe we should extend a ToolRegistry protocol to make sure that one > tool can override another one, > so if you reset a tools, then overrides will be applied in right order. > > Also , since we removed toolbuilder, a code for building its UI should > also rewritten. > > > -- > Best regards, > Igor Stasenko AKA sig. >

July 14, 2011

[Pharo-project] Tests package is missing in the Pharo14 repository

by Pavel Krivanek

Please, can somebody copy latests Tests package from Pharo repository to Pharo14 repository too? -- Pavel

July 14, 2011

Re: [Pharo-project] [Seaside] Class Variable Browser Fix

by Lukas Renggli

> If you go to a class variable usage in the browser, say DefaultDirectory in FileDirectory>>default, and select and right click it, Seaside brings up a walk-back. I cannot reproduce that. Also note, that this is not Seaside related, but OmniBrowser (I thus reply to the Pharo list). > My fix for this re-writes the existing method a little by using '&' instead of the older 'and:', which I find clearer. What I've done is check that the value can respond to #asNode: > > globalReference > Â Â Â Â | binding | > Â Â Â Â target hasSelector > Â Â Â Â Â Â Â Â ifFalse: [ ^ nil ]. > Â Â Â Â (requestor selectedClass notNil & (binding := requestor selectedClass bindingOf: target selector) notNil & binding value notNil & (binding value class selectors includes: #asNode)) > Â Â Â Â Â Â Â Â ifTrue: [ ^ binding value asNode ]. > Â Â Â Â (binding := Smalltalk classNamed: target selector) notNil > Â Â Â Â Â Â Â Â ifTrue: [ ^ binding value asNode ]. > Â Â Â Â ^ nil This certainly introduces other bugs. The use of the non-eager #and: is intentional, because if "requestor selectedClass" is nil, "requestor selectedClass bindingOf:" is not supposed to be evaluated. Lukas -- Lukas Renggli www.lukas-renggli.ch

July 14, 2011