- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Ephestos

by btc＠openinworld.com

kilon alios wrote: > Still long way to go until its really useful but following your advice > I decided to release it to public and announce it instead of having it > hidden. > > Ladies , gentleman and hybrids I present to you Ephestos, my visual > coding project for graphics and sound. > > This is my very first project with Pharo and Smalltalk and my second > coding project. > > Just released a version 0.1 so as you can imagine you wont see > anything impressive yet but none the less it included my first > Ephestos tool, Hyperion a vector graphics editor. Right now it can > only edit a single vector straight line and add new lines. > > I am working now on version 0.2 that will allow you to edit other > lines , moving them around with mouse and add support for bezier curves. > > So its moving .... slowly .... very slowly... but moving none the less :D > > You can find Ephestos here along with installation instructions and > how to use Hyperion. Suffice to say you will need Pharo 3 to run it > > http://www.smalltalkhub.com/#!/~kilon/Ephestos > <http://www.smalltalkhub.com/#%21/%7Ekilon/Ephestos> > > I hope I will have Version 1 in January 2015 that will set out the > base functionality of Hyperion which will be a complete very basic > vector editor with features you will expect to find in a vector editor > like moving lines around, editing them, adding new control points to > them, making gradients and basic layer support. Will also introduce > Prometheas a new documentation system . > > I would like to thank all people who make Pharo so amazing and cool, > my problems with this project have more to do with my understanding on > how to code this thing properly than pharo and its libraries. So I > definitely did not expected it to be such a smooth ride. That looks like a nice start. I could move the initial line around by its handles. Some thoughts (which are probably on your radar anyway)... * Tooltips for the buttons would be nice * Add a superclass to the buttons to site between them and Morph, to hold common methods. Interesting to see your use of Athens, since I haven't used this yet. For future announcments you may want to include pharo-users mail list, since that is a good place to discuss user apps. cheers -ben

Dec. 28, 2013

Re: [Pharo-dev] Are #explorerContents and #hasContentsInExplorer obsolete ?

by Tudor Girba

Thanks for raising this :). I now added a simple implementation in the GTInspector to have Pointers available for all objects. Perhaps it is overdoing it to have it by default on all objects, but it was cheap to implement in a crude way. I still do not eliminate all inspector related objects that point to the current object, but it's a start (see attached the pointers to Smalltalk). Object>>gtInspectorPointersIn: composite <gtInspectorPresentationOrder: 20> composite list title: 'Pointers'; display: [ (self pointersToExcept: { self }) reject: [ :each | each pointsOnlyWeaklyTo: self ] ]; format: [ :each | GTObjectPrinter new asTruncatedTextFrom: each ]; showOnly: 50 [image: Inline image 1] Cheers, Doru On Wed, Dec 25, 2013 at 12:04 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On 21 Dec 2013, at 15:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > Hi, > > > > It seems that #explorerContents and #hasContentsInExplorer are no longer > used. > > > > Implementing a new Eye inspector with #addSpecialFields: seems to affect > both the Inspector view as well as the Tree Inspector. > > > > So, should they be removed ? > > > > Yes, but we need to first find a solution for the Pointer Explorer: right > now this is a subclass of the old Explorere, therefore this is > still in the image. > > https://pharo.fogbugz.com/f/cases/11709/remove-old-ObjectExplorer > > Marcus > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 28, 2013

Re: [Pharo-dev] [fun] Editing graphic vectorial content

by Tudor Girba

Excellent! It would be great to build on this. Cheers, Doru On Sat, Dec 28, 2013 at 12:51 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > Just to share a 10 min coding session, just before lunch. > > Result here: > > https://www.facebook.com/photo.php?fbid=564129843673617&set=a.3411893793009… > > code: > -=-=-=-=-=-=-=-= > | view stack selected statusBar | > stack := ROViewStack new. > view := ROView new. > selected := nil. > statusBar := nil. > > view on: ROMouseClick do: [ :evt | > selected == #line ifTrue: [ > | ex1 ex2 line | > ex1 := (ROBox new size: 10; color: (Color purple alpha: > 0.2)) element. > ex2 := (ROBox new size: 10; color: (Color purple alpha: > 0.2)) element. > ex1 translateTo: evt position. > ex2 translateTo: evt position + (100 @ 60). > ex1 @ ROLightlyHighlightable. > ex2 @ ROLightlyHighlightable. > ex1 @ RODraggable. > ex2 @ RODraggable. > line := (ROLine new width: 3; color: (Color blue alpha: > 0.2)) elementFrom: ex1 to: ex2. > view addAll: { ex1 . ex2 . line }. > ]. > > selected == #circle ifTrue: [ > | ellipse | > ellipse := (ROEllipse new size: 40; color: (Color yellow > alpha: 0.2)) element. > ellipse translateTo: evt position. > ellipse @ RODraggable. > view add: ellipse. > ]. > > > selected == #rectangle ifTrue: [ > | box | > box := (ROBox new width: 40; height: 30; color: (Color > blue alpha: 0.2)) element. > box translateTo: evt position. > box @ RODraggable. > view add: box. > ]. > view signalUpdate. > ]. > > > > view @ RODraggable. > > stack zoomInButton; zoomOutButton. > stack addMenu: '+ line' callBack: [ :evt | selected := #line. statusBar > model: 'line' ]. > stack addMenu: '+ rectangle' callBack: [ :evt | selected := #rectangle. > statusBar model: 'rectangle' ]. > stack addMenu: '+ circle' callBack: [ :evt | selected := #circle. > statusBar model: 'circle' ]. > stack addMenu: 'Info' callBack: [ :evt | UIManager default inform: > 'Vectorial editing is hyper cool' ]. > > stack addView: view. > stack title: 'Vectorial edition'. > > "Status bar at the bottom of the window" > statusBar := (ROElement new) + ROLabel + ROBox white. > stack add: statusBar. > ROConstraint stickAtTheBottomOfTheWindow: statusBar. > > stack open > -=-=-=-=-=-=-=-= > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 28, 2013

[fun] Editing graphic vectorial content

by Alexandre Bergel

Just to share a 10 min coding session, just before lunch. Result here: https://www.facebook.com/photo.php?fbid=564129843673617&set=a.3411893793009… code: -=-=-=-=-=-=-=-= | view stack selected statusBar | stack := ROViewStack new. view := ROView new. selected := nil. statusBar := nil. view on: ROMouseClick do: [ :evt | selected == #line ifTrue: [ | ex1 ex2 line | ex1 := (ROBox new size: 10; color: (Color purple alpha: 0.2)) element. ex2 := (ROBox new size: 10; color: (Color purple alpha: 0.2)) element. ex1 translateTo: evt position. ex2 translateTo: evt position + (100 @ 60). ex1 @ ROLightlyHighlightable. ex2 @ ROLightlyHighlightable. ex1 @ RODraggable. ex2 @ RODraggable. line := (ROLine new width: 3; color: (Color blue alpha: 0.2)) elementFrom: ex1 to: ex2. view addAll: { ex1 . ex2 . line }. ]. selected == #circle ifTrue: [ | ellipse | ellipse := (ROEllipse new size: 40; color: (Color yellow alpha: 0.2)) element. ellipse translateTo: evt position. ellipse @ RODraggable. view add: ellipse. ]. selected == #rectangle ifTrue: [ | box | box := (ROBox new width: 40; height: 30; color: (Color blue alpha: 0.2)) element. box translateTo: evt position. box @ RODraggable. view add: box. ]. view signalUpdate. ]. view @ RODraggable. stack zoomInButton; zoomOutButton. stack addMenu: '+ line' callBack: [ :evt | selected := #line. statusBar model: 'line' ]. stack addMenu: '+ rectangle' callBack: [ :evt | selected := #rectangle. statusBar model: 'rectangle' ]. stack addMenu: '+ circle' callBack: [ :evt | selected := #circle. statusBar model: 'circle' ]. stack addMenu: 'Info' callBack: [ :evt | UIManager default inform: 'Vectorial editing is hyper cool' ]. stack addView: view. stack title: 'Vectorial edition'. "Status bar at the bottom of the window" statusBar := (ROElement new) + ROLabel + ROBox white. stack add: statusBar. ROConstraint stickAtTheBottomOfTheWindow: statusBar. stack open -=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 28, 2013

Re: [Pharo-dev] Fwd: problem while parsing xml

by Sven Van Caekenberghe

And it would be good if monty talked directly on the list ;-) On 28 Dec 2013, at 11:37, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thanks for forwarding the message, Stef. > > Good to know. But, it would still be good to have the error message point to the root cause :) > > Cheers, > Doru > > > > > On Sat, Dec 28, 2013 at 10:51 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > > Begin forwarded message: > >> From: "monty" <monty.os(a)engineer.com> >> Subject: Re: [Pharo-dev] problem while parsing xml >> Date: 28 Dec 2013 01:41:36 GMT+1 >> To: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> >> >> Thanks for the CCs. I've identified the sources of the problem(s) and am working on it now and should have it fixed soon (though its not entirely confined to XMLParser, but the fixes outside are minimal). >> >> NOTE: You can always just disable resolvesExternalEntities: and isValidating: (or use parse:usingNamespaces:validation:externalEntities: with the last two args false) if they are causing problems. >> >>> ----- Original Message ----- >>> From: StÃ©phane Ducasse >>> Sent: 12/27/13 04:42 AM >>> To: Pharo Development List >>> Subject: Re: [Pharo-dev] problem while parsing xml >>> >>> ok I missed the example in the mail of satoshi I will try to have a look or at leat write a test. >>> >>> On 25 Dec 2013, at 19:04, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>>> Hi Hernan >>>> >>>> how did you reproduce the bug? >>>> Because it would be nice to fix it. >>>> >>>> Stef >>>> >>>> On 24 Dec 2013, at 18:48, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >>>> >>>>> I have tried in Pharo 2.0 configurations from Config Browser (ConfigurationOfXMLParser-StephaneDucasse.16) and latest from http://www.smalltalkhub.com/mc/PharoExtras/XMLParser/main (ConfigurationOfXMLParser-monty.37) and both have this bug. >>>>> HernÃ¡n >>>>> >>>>> 2013/12/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>>> Hi Satoshi >>>>> >>>>> Did you try with the latest configuration of XMLParser? >>>>> Because I do not know what it is in Moose. >>>>> Stef >>>>> >>>>> On 23 Dec 2013, at 18:26, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: >>>>> >>>>> > Hello >>>>> > >>>>> > using: Pharo3.0 Latest update: #30659 (it occurs same error to >>>>> > Pharo2.0 Latest update: #20628) >>>>> > (Moose 4.9 with XML-Parser (DamienCassou.143) has no_err) >>>>> > >>>>> > 1. load XMLParser (StephaneDucasse.16) from Configuration browser >>>>> > 2. select and inspect it below: >>>>> > ^ XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> >>>>> >>>>> > <!DOCTYPE score-partwise PUBLIC >>>>> > "-//Recordare//DTD MusicXML 3.0 Partwise//EN" >>>>> > "http://www.musicxml.org/dtds/partwise.dtd"> >>>>> > <score-partwise version="3.0"> >>>>> > <part-list> >>>>> > <score-part id="P1"> >>>>> > <part-name>Music</part-name> >>>>> > </score-part> >>>>> > </part-list> >>>>> > <part id="P1"> >>>>> > <measure number="1"> >>>>> > <attributes> >>>>> > <divisions>1</divisions> >>>>> > <key> >>>>> > <fifths>0</fifths> >>>>> > </key> >>>>> > <time> >>>>> > <beats>4</beats> >>>>> > <beat-type>4</beat-type> >>>>> > </time> >>>>> > <clef> >>>>> > <sign>G</sign> >>>>> > <line>2</line> >>>>> > </clef> >>>>> > </attributes> >>>>> > <note> >>>>> > <pitch> >>>>> > <step>C</step> >>>>> > <octave>4</octave> >>>>> > </pitch> >>>>> > <duration>4</duration> >>>>> > <type>whole</type> >>>>> > </note> >>>>> > </measure> >>>>> > </part> >>>>> > </score-partwise> >>>>> > ' readStream. >>>>> > >>>>> > 3. and get DNU: SmallInteger>>asciiValue >>>>> > >>>>> > 'case of XMLZincClient>>#get: >>>>> > 'http://www.musicxml.com/dtds/partwise.dtd' timeout: ... onError: ... >>>>> > returns binaryStream? >>>>> > >>>>> > >>>>> > -- >>>>> > -- >>>>> > "NISHIHARA Satoshi" >>>>> > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] >>>>> > <PharoDebug.log> >>>>> >>>>> >> > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Dec. 28, 2013

Re: [Pharo-dev] Fwd: problem while parsing xml

by Tudor Girba

Thanks for forwarding the message, Stef. Good to know. But, it would still be good to have the error message point to the root cause :) Cheers, Doru On Sat, Dec 28, 2013 at 10:51 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > > > Begin forwarded message: > > *From: *"monty" <monty.os(a)engineer.com> > *Subject: **Re: [Pharo-dev] problem while parsing xml* > *Date: *28 Dec 2013 01:41:36 GMT+1 > *To: *"StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > > Thanks for the CCs. I've identified the sources of the problem(s) and am > working on it now and should have it fixed soon (though its not entirely > confined to XMLParser, but the fixes outside are minimal). > > NOTE: You can always just disable resolvesExternalEntities: and > isValidating: (or use parse:usingNamespaces:validation:externalEntities: > with the last two args false) if they are causing problems. > > > > ----- Original Message ----- > From: StÃ©phane Ducasse > Sent: 12/27/13 04:42 AM > To: Pharo Development List > Subject: Re: [Pharo-dev] problem while parsing xml > > ok I missed the example in the mail of satoshi I will try to have a look > or at leat write a test. > > On 25 Dec 2013, at 19:04, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > > Hi Hernan > > how did you reproduce the bug? > Because it would be nice to fix it. > > Stef > > On 24 Dec 2013, at 18:48, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > wrote: > > > I have tried in Pharo 2.0 configurations from Config Browser > (ConfigurationOfXMLParser-StephaneDucasse.16) and latest from > http://www.smalltalkhub.com/mc/PharoExtras/XMLParser/main(ConfigurationOfXM… and both have this bug. > HernÃ¡n > > 2013/12/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >> Hi Satoshi >> >> Did you try with the latest configuration of XMLParser? >> Because I do not know what it is in Moose. >> Stef >> >> On 23 Dec 2013, at 18:26, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: >> >> > Hello >> > >> > using: Pharo3.0 Latest update: #30659 (it occurs same error to >> > Pharo2.0 Latest update: #20628) >> > (Moose 4.9 with XML-Parser (DamienCassou.143) has no_err) >> > >> > 1. load XMLParser (StephaneDucasse.16) from Configuration browser >> > 2. select and inspect it below: >> > ^ XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" >> standalone="no"?> >> >> > <!DOCTYPE score-partwise PUBLIC >> > "-//Recordare//DTD MusicXML 3.0 Partwise//EN" >> > "http://www.musicxml.org/dtds/partwise.dtd"> >> > <score-partwise version="3.0"> >> > <part-list> >> > <score-part id="P1"> >> > <part-name>Music</part-name> >> > </score-part> >> > </part-list> >> > <part id="P1"> >> > <measure number="1"> >> > <attributes> >> > <divisions>1</divisions> >> > <key> >> > <fifths>0</fifths> >> > </key> >> > <time> >> > <beats>4</beats> >> > <beat-type>4</beat-type> >> > </time> >> > <clef> >> > <sign>G</sign> >> > <line>2</line> >> > </clef> >> > </attributes> >> > <note> >> > <pitch> >> > <step>C</step> >> > <octave>4</octave> >> > </pitch> >> > <duration>4</duration> >> > <type>whole</type> >> > </note> >> > </measure> >> > </part> >> > </score-partwise> >> > ' readStream. >> > >> > 3. and get DNU: SmallInteger>>asciiValue >> > >> > 'case of XMLZincClient>>#get: >> > 'http://www.musicxml.com/dtds/partwise.dtd' timeout: ... onError: ... >> > returns binaryStream? >> > >> > >> > -- >> > -- >> > "NISHIHARA Satoshi" >> > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] >> > <PharoDebug.log> >> >> > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 28, 2013

[ANN] Ephestos

by kilon alios

Still long way to go until its really useful but following your advice I decided to release it to public and announce it instead of having it hidden. Ladies , gentleman and hybrids I present to you Ephestos, my visual coding project for graphics and sound. This is my very first project with Pharo and Smalltalk and my second coding project. Just released a version 0.1 so as you can imagine you wont see anything impressive yet but none the less it included my first Ephestos tool, Hyperion a vector graphics editor. Right now it can only edit a single vector straight line and add new lines. I am working now on version 0.2 that will allow you to edit other lines , moving them around with mouse and add support for bezier curves. So its moving .... slowly .... very slowly... but moving none the less :D You can find Ephestos here along with installation instructions and how to use Hyperion. Suffice to say you will need Pharo 3 to run it http://www.smalltalkhub.com/#!/~kilon/Ephestos I hope I will have Version 1 in January 2015 that will set out the base functionality of Hyperion which will be a complete very basic vector editor with features you will expect to find in a vector editor like moving lines around, editing them, adding new control points to them, making gradients and basic layer support. Will also introduce Prometheas a new documentation system . I would like to thank all people who make Pharo so amazing and cool, my problems with this project have more to do with my understanding on how to code this thing properly than pharo and its libraries. So I definitely did not expected it to be such a smooth ride.

Dec. 28, 2013

Error in loading libreries

by Lorenzo Schiavina

Hi, every time I try to load a package from Monticello, I receive the message: ERROR: MCHttpRepository expected. Can anybody tell me why and suggest me a workeround? Many thanks and season's greetings Lorenzo

Dec. 28, 2013

Fwd: problem while parsing xml

by StÃ©phane Ducasse

Begin forwarded message: > From: "monty" <monty.os(a)engineer.com> > Subject: Re: [Pharo-dev] problem while parsing xml > Date: 28 Dec 2013 01:41:36 GMT+1 > To: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > > Thanks for the CCs. I've identified the sources of the problem(s) and am working on it now and should have it fixed soon (though its not entirely confined to XMLParser, but the fixes outside are minimal). > > NOTE: You can always just disable resolvesExternalEntities: and isValidating: (or use parse:usingNamespaces:validation:externalEntities: with the last two args false) if they are causing problems. > >> ----- Original Message ----- >> From: StÃ©phane Ducasse >> Sent: 12/27/13 04:42 AM >> To: Pharo Development List >> Subject: Re: [Pharo-dev] problem while parsing xml >> >> ok I missed the example in the mail of satoshi I will try to have a look or at leat write a test. >> >> On 25 Dec 2013, at 19:04, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> >>> Hi Hernan >>> >>> how did you reproduce the bug? >>> Because it would be nice to fix it. >>> >>> Stef >>> >>> On 24 Dec 2013, at 18:48, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >>> >>>> >>>> I have tried in Pharo 2.0 configurations from Config Browser (ConfigurationOfXMLParser-StephaneDucasse.16) and latest from http://www.smalltalkhub.com/mc/PharoExtras/XMLParser/main (ConfigurationOfXMLParser-monty.37) and both have this bug. >>>> HernÃ¡n >>>> >>>> 2013/12/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>> Hi Satoshi >>>> >>>> Did you try with the latest configuration of XMLParser? >>>> Because I do not know what it is in Moose. >>>> Stef >>>> >>>> On 23 Dec 2013, at 18:26, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: >>>> >>>> > Hello >>>> > >>>> > using: Pharo3.0 Latest update: #30659 (it occurs same error to >>>> > Pharo2.0 Latest update: #20628) >>>> > (Moose 4.9 with XML-Parser (DamienCassou.143) has no_err) >>>> > >>>> > 1. load XMLParser (StephaneDucasse.16) from Configuration browser >>>> > 2. select and inspect it below: >>>> > ^ XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> >>>> > <!DOCTYPE score-partwise PUBLIC >>>> > "-//Recordare//DTD MusicXML 3.0 Partwise//EN" >>>> > "http://www.musicxml.org/dtds/partwise.dtd"> >>>> > <score-partwise version="3.0"> >>>> > <part-list> >>>> > <score-part id="P1"> >>>> > <part-name>Music</part-name> >>>> > </score-part> >>>> > </part-list> >>>> > <part id="P1"> >>>> > <measure number="1"> >>>> > <attributes> >>>> > <divisions>1</divisions> >>>> > <key> >>>> > <fifths>0</fifths> >>>> > </key> >>>> > <time> >>>> > <beats>4</beats> >>>> > <beat-type>4</beat-type> >>>> > </time> >>>> > <clef> >>>> > <sign>G</sign> >>>> > <line>2</line> >>>> > </clef> >>>> > </attributes> >>>> > <note> >>>> > <pitch> >>>> > <step>C</step> >>>> > <octave>4</octave> >>>> > </pitch> >>>> > <duration>4</duration> >>>> > <type>whole</type> >>>> > </note> >>>> > </measure> >>>> > </part> >>>> > </score-partwise> >>>> > ' readStream. >>>> > >>>> > 3. and get DNU: SmallInteger>>asciiValue >>>> > >>>> > 'case of XMLZincClient>>#get: >>>> > 'http://www.musicxml.com/dtds/partwise.dtd' timeout: ... onError: ... >>>> > returns binaryStream? >>>> > >>>> > >>>> > -- >>>> > -- >>>> > "NISHIHARA Satoshi" >>>> > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] >>>> > <PharoDebug.log> >>>> >>>> >

Dec. 28, 2013

Re: [Pharo-dev] Nautilus: tab key change focus

by GOUBIER Thierry

Hi Jura, I had a short look (kind of hard at the moment) and I noticed that Ctrl+tab was working to switch the focus around correctly, but maybe in an incorrect order. This could be fixed by adding the morphs at creation time in a different order. However, Ctrl+Shift+Tab wasn't working :( And tab has no effect in the filter (neither focus change nor text input). Your solution is a bit heavy handed for me, I was thinking of something more like: searchWidget onKeyCombination: Character tab asKeyCombination do: [self giveFocusToPackage]. Don't forget that, as you're touching the focus tab order, you have a duty to make it complete (i.e. all widgets can be tabbed to starting from any widget). Thierry ________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Juraj Kubelka [juraj.kubelka(a)gmail.com] Date d'envoi : vendredi 27 dÃ©cembre 2013 18:49 Ã : Pharo Development List Objet : Re: [Pharo-dev] Nautilus: tab key change focus Thanks for the advice. I have just tried to add my own key stroke handling and I face interesting issue. The first time I enter the package filter input field, everything works. When I press down-key, it change focus to package list. But since then whenever I enter again the filter, any key stroke change the focus back to package list. I do not see any glue right now. The code is like this: buildPackageSearch "It is an search dialog which filters package list" searchWidget := SearchMorph new model: self; updateSelector: #packageSearchUpdate:; ghostText: 'Type: Pkg1|^Pkg2|Pk.*Core$'; list: SharedValueHolder instance; useSelectionIndex: false; setIndexSelector: #packageSearchUpdate:; keystrokeSelector: #packageSearchKeyStroke:; yourself. ^ searchWidget packageSearchKeyStroke: anEvent (anEvent keyCharacter = Character arrowDown) ifTrue: [ self giveFocusToPackage. ^ true ]. ^ false Thanks. Jura

Dec. 28, 2013