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

Re: [Pharo-project] Nautilus first impression

by phil＠highoctane.be

Yes, Nautilus is ubernice. Especially given the forthcoming search bar :-p The help panel cutting the bottom pane in two is all right but then, could we have it with a smaller font? I drives me nuts to have to scroll down there. Phil 2012/4/22 Sean P. DeNigris <sean(a)clipperadams.com> > Wow, Nautilus is *really* fun to use! I have quite a few ideas for > plugins... > > A few suggestions... > * Hierarchical package list - also, since with Metacello the convention is > (e.g. P-Core, P-UI, P-Tests) with no overarching package, it should group > all packages matching P-*, even if they are technically separate packages > * I miss the search bar from OB where I could just start typing as soon as > I > opened the window. It seems that Nautilus doesn't set the keyboard focus > anywhere useful. Options: > - search bar > - typing brings up the class search dialog > - give keyboard focus to the package list so I can use the shortcuts right > away. This may be the best one because I have access to 3 options: > - cmd-F to search packages > - cmd-f to search classes > - start typing to do a basic package search > * creating new methods - when you click a protocol name, the > "messageSelectorAndArgumentNames" template is displayed in the code pane, > and is pre-selected. I found this very confusing as a newbie because the > selection made me think that I could start typing to replace the template, > but the keyboard focus is not on the template. It's also useless because > when you click on the code pane, it unselects, so you have to double-click > anyway. Two suggestions > - from the class pane, protocol pane, or both, have an "add method" menu > item that transfers focus to the preselected template > - when just clicking on a protocol, don't pre-select the template > * back/forward buttons for history navigation? > * a centralized place to put/list plugins so we can share them > > Many thanks to Benjamin. This was sorely needed! > > Cheers, > Sean > > -- > View this message in context: > http://forum.world.st/Nautilus-first-impression-tp4578301p4578301.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges

April 22, 2012

Re: [Pharo-project] Do we get rid of the KeyDecodeTable in InputEventSensor?

by phil＠highoctane.be

May I add that some Cmd-Q on OSX really sucks for autocompletion? And Alt-Shift for Halos when you have multiple keyboards setup in Windows? (It is the system shortcut for toggle language (like FR->EN). Using the middle button like in Cuis would be much better methinks. Phil 2012/4/22 Guillermo Polito <guillermopolito(a)gmail.com> > It's supposed to do some conversions, but sometimes, it just screws up the > use input. It's main responsibility is to change *ctrl* into *alt*: > > installDuplicateKeyEntryFor: c > | key | > key := c asInteger. > "first do control->alt key" > KeyDecodeTable at: { key bitAnd: 16r9F . 2 } put: { key . 8 }. > "then alt->alt key" > KeyDecodeTable at: { key . 8 } put: { key . 8 } > > > And then it confuses stuff. For example, Ctrl + tab is decoded as ctrl + > $i, since > > $i asInteger bitAnd: 16r9F = Character tab asInteger > > > And btw, I love my ctrl key and want to have more fancy and sexy > shortcuts, so this F*** table is bothering :). > > Opinions? > Guille > -- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges

April 22, 2012

Re: [Pharo-project] Suggestion: introducing a fixme/issue/todo pragma

by phil＠highoctane.be

I kind of like dirty corners. Especially for cleaning them up and turn them into shiny new orbs of glory. Jokes aside, there is an awful lot of potential in Pharo. Just being exposed to it for a while shows in my other coding activities (other languages). I would be perfect if we could grasp the whole system given enough attention (like the "Feel of Cuis" which is real). The challenge is to hit the sweet spot. Too much convolutions and we are doomed. Too little features and we can't be considered a contender. KR Philippe 2012/4/22 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > On Sun, Apr 22, 2012 at 3:53 PM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > >> Ok. >> >> Looks like there is still a lot of dirty corners under the hood by >> looking at this list of senders... >> > > Indeed. But the first step is to identify them, right? So at least we > know those dirty corners ;) > > > >> >> Phil >> >> 2012/4/22 Mariano Martinez Peck <marianopeck(a)gmail.com> >> >>> >>> >>> On Sun, Apr 22, 2012 at 11:55 AM, StÃ©phane Ducasse < >>> stephane.ducasse(a)inria.fr> wrote: >>> >>>> we use self flag: #fixMe >>>> you can then query either #fixMe or flag: >>>> >>>> and yes this is a good idea to mark things and create bug entries. >>>> >>>> Stef >>>> >>>> >>>> On Apr 22, 2012, at 11:18 AM, phil(a)highoctane.be wrote: >>>> >>>> > While looking around in the image, I am in need of knowing where I >>>> found thngs that either puzzle me or are "wrong" (well, a code smell). >>>> > >>>> > What I do is that I put pragmas in there like this (not that this >>>> sample is meant to be representative) >>>> > >>>> > privCleanTextConstants >>>> > <fixme> >>>> > TextConstants TextSharedInformation removeKey: >>>> #DefaultTextStyle. >>>> > TextConstants TextSharedInformation removeKey: >>>> #DefaultMultiStyle. >>>> > TextConstants TextSharedInformation removeKey: >>>> #DefaultFixedTextStyle. >>>> > TextConstants TextSharedInformation removeKey: StrikeFont >>>> defaultFontKey. >>>> > >>>> > Smalltalk allClasses select: [:c | c sharedPools includes: >>>> TextConstants] thenDo: [:c | c compileAll ]. >>>> > >>>> > And I can then find back the things with: >>>> > >>>> > pc := (PragmaCollector filter: [:prg | prg keyword = 'fixme']) reset. >>>> > pc collected size. "(Print It: 1)" >>>> > pc collected explore. >>>> > >>>> > And then finding back the Class and Method Name >>>> > >>>> > Building upon that, why not do what is done in other environments >>>> (well, I've got that in PHP, Java, ...) and use: >>>> > >>>> > <todo:do this and that> or plain <todo> >>>> > <fixme: this and that> or plain <fixme> >>>> > <issue:issue#> >>>> > >>>> >>> >>> As Stef said, we usually use #flag: Normal cases are #flag:todo, >>> #flag:fixMe, etc .. and the browser is aware of that and shows you a flag >>> in the icon of the method. >>> >>> >>> >>> >>>> > And have a specific tool to help the navigation (explore is fine for >>>> a moment but...) >>>> > >>>> > This would allow us to have an idea on the technical debt inside the >>>> system, broken down by areas if we start leveraging Packages. >>>> > >>>> > What I do not know is how much stress this would put on the system. >>>> Are pragmas eating a lot or a just markers? >>>> > >>>> > Phil >>>> > >>>> >>>> >>>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >>> >> >> >> -- >> Philippe Back >> "Helping you hit the top 3 outcomes you really want to achieve" >> >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: >> phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >> http://philippeback.be >> >> High Octane SPRL >> rue cour Boisacq 101 >> 1301 Bierges >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges

April 22, 2012

Re: [Pharo-project] [ANN] Styled Text Editor for Cuis 4.0 Smalltalk

by Chris Muller

Did your "Smalltalk Code Critic" tell you that or just another one of your biased opinions? Squeak is a fantastic media authoring environment -- even old versions from years past embarass programs like, say, PowerPoint. It's text-handling is fantastic -- remember the release image delivered with text on the desktop flowing out one text box, following along a loop-de-loop spline and into another text box? What other programs that can do that today in 2012..? In the spirit of Squeak, the original developers delivered a lot of power with little code. But yes, it's a complex domain and so reviewing the code in one afternoon may not meet your "aesthetic eye." On Sat, Apr 21, 2012 at 2:21 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Apr 21, 2012, at 9:17 PM, phil(a)highoctane.be wrote: > >> Great news! >> >> I am currently busy looking after Text, TextAttributes, TextConstants, Paragraph... and god, it went through the grinder and it shows. >> > > Isn't it amazing how bad the Squeak code is for text and everything media considering that the goal was to be the media environment for the future? > > Â Â Â Â Marcus > > > -- > Marcus Denker -- http://marcusdenker.de > >

April 22, 2012

Re: [Pharo-project] Do we get rid of the KeyDecodeTable in InputEventSensor?

by StÃ©phane Ducasse

+1 we will get there :) Stef On Apr 22, 2012, at 4:53 PM, Guillermo Polito wrote: > It's supposed to do some conversions, but sometimes, it just screws up the use input. It's main responsibility is to change ctrl into alt: > > installDuplicateKeyEntryFor: c > | key | > key := c asInteger. > "first do control->alt key" > KeyDecodeTable at: { key bitAnd: 16r9F . 2 } put: { key . 8 }. > "then alt->alt key" > KeyDecodeTable at: { key . 8 } put: { key . 8 } > > > And then it confuses stuff. For example, Ctrl + tab is decoded as ctrl + $i, since > > $i asInteger bitAnd: 16r9F = Character tab asInteger > > > And btw, I love my ctrl key and want to have more fancy and sexy shortcuts, so this F*** table is bothering :). > > Opinions? > Guille

April 22, 2012

[Pharo-project] Morphic Event handler crap

by Guillermo Polito

EventHandler>>on: eventName send: selector to: recipient eventName == #mouseDown ifTrue: [mouseDownRecipient := recipient. mouseDownSelector := selector. ^ self]. eventName == #mouseMove ifTrue: [mouseMoveRecipient := recipient. mouseMoveSelector := selector. ^ self]. eventName == #mouseStillDown ifTrue: [mouseStillDownRecipient := recipient. mouseStillDownSelector := selector. ^ self]. eventName == #mouseUp ifTrue: [mouseUpRecipient := recipient. mouseUpSelector := selector. ^ self]. eventName == #mouseEnter ifTrue: [mouseEnterRecipient := recipient. mouseEnterSelector := selector. ^ self]. eventName == #mouseLeave ifTrue: [mouseLeaveRecipient := recipient. mouseLeaveSelector := selector. ^ self]. eventName == #mouseEnterDragging ifTrue: [mouseEnterDraggingRecipient := recipient. mouseEnterDraggingSelector := selector. ^ self]. eventName == #mouseLeaveDragging ifTrue: [mouseLeaveDraggingRecipient := recipient. mouseLeaveDraggingSelector := selector. ^ self]. eventName == #click ifTrue: [clickRecipient := recipient. clickSelector := selector. ^ self]. eventName == #doubleClick ifTrue: [doubleClickRecipient := recipient. doubleClickSelector := selector. ^ self]. eventName == #doubleClickTimeout ifTrue: [doubleClickTimeoutRecipient := recipient. doubleClickTimeoutSelector := selector. ^ self]. eventName == #startDrag ifTrue: [startDragRecipient := recipient. startDragSelector := selector. ^ self]. eventName == #keyStroke ifTrue: [keyStrokeRecipient := recipient. keyStrokeSelector := selector. ^ self]. eventName == #gesture ifTrue: [ ^self onGestureSend: selector to: recipient ]. self error: 'Event name, ' , eventName , ' is not recognizable.' First) It is not handling KeyDown and keyUp :) Second) it does not support multiple handlers for the same event Moving it to announcements in a first attempt seems too agressive :P. Working a bit on it :). Guille

April 22, 2012

Re: [Pharo-project] Nautilus first impression

by Sean P. DeNigris

Benjamin Van Ryseghem-2 wrote > > I just copy/paste the behavior from the default browser > haha. yes, it looked very familiar Benjamin Van Ryseghem-2 wrote > >> * a centralized place to put/list plugins so we can share them > I have now idea how to do that except creating a dedicated repository :) > Just dreaming... Benjamin Van Ryseghem-2 wrote > > Thanks to you for your feedback and your good ideas :) > You're welcome. It's the least I could do :) -- View this message in context: http://forum.world.st/Nautilus-first-impression-tp4578301p4578361.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 22, 2012

Re: [Pharo-project] System announcements and MC

by Sean P. DeNigris

MC was also loading all classes twice (which explains the instance-side class def changed notifications), so I fixed that too... Fix in inbox: SLICE-Issue-5652-MC-incorrect-announcements-on-class-load-SeanDeNigris.1 * Fixed inappropriate class definition changed notifications during MC loading * Fixed related bug where MC was loading classes twice (see MCPackageLoader>>basicLoad) Sean -- View this message in context: http://forum.world.st/System-announcements-and-MC-tp4577351p4578356.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 22, 2012

Re: [Pharo-project] Nautilus first impression

by Guillermo Polito

On Sun, Apr 22, 2012 at 5:24 PM, Benjamin < benjamin.vanryseghem.pharo(a)gmail.com> wrote: > > On Apr 22, 2012, at 5:01 PM, Sean P. DeNigris wrote: > > > Wow, Nautilus is *really* fun to use! I have quite a few ideas for > plugins... > > Cool :) > > > A few suggestions... > > * Hierarchical package list - also, since with Metacello the convention > is > > (e.g. P-Core, P-UI, P-Tests) with no overarching package, it should group > > all packages matching P-*, even if they are technically separate packages > > We thought of that, but first, we had to make the tree widgets faster :) > > > * I miss the search bar from OB where I could just start typing as soon > as I > > opened the window. It seems that Nautilus doesn't set the keyboard focus > > anywhere useful. > > This is strange, the focus should be at the nice place (like class if you > browse a class, method if you browse a method and so on) > I will check that. > > > Options: > > - search bar > > I will keep that in mind ;) > > > - typing brings up the class search dialog > > - give keyboard focus to the package list so I can use the shortcuts > right > > away. This may be the best one because I have access to 3 options: > > - cmd-F to search packages > > - cmd-f to search classes > > - start typing to do a basic package search > > As I said, the focus should be there. > > > * creating new methods - when you click a protocol name, the > > "messageSelectorAndArgumentNames" template is displayed in the code pane, > > and is pre-selected. I found this very confusing as a newbie because the > > selection made me think that I could start typing to replace the > template, > > but the keyboard focus is not on the template. It's also useless because > > when you click on the code pane, it unselects, so you have to > double-click > > anyway. > > True ! I already notice that ^^ To be honest, I just copy/paste the > behavior from the default browser, but I will change that soon ^^ > > > Two suggestions > > - from the class pane, protocol pane, or both, have an "add method" menu > > item that transfers focus to the preselected template > > - when just clicking on a protocol, don't pre-select the template > > > * back/forward buttons for history navigation? > > They use to be there, I will reintroduce them :) > > > * a centralized place to put/list plugins so we can share them > > I have now idea how to do that except creating a dedicated repository :) > And then a Plugin to fetch them :3 > > > > > Many thanks to Benjamin. This was sorely needed! > > > > Cheers, > > Sean > > > > Thanks to you for your feedback and your good ideas :) > > Ben > > > -- > > View this message in context: > http://forum.world.st/Nautilus-first-impression-tp4578301p4578301.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > >

April 22, 2012

Re: [Pharo-project] Nautilus first impression

by Benjamin

On Apr 22, 2012, at 5:01 PM, Sean P. DeNigris wrote: > Wow, Nautilus is *really* fun to use! I have quite a few ideas for plugins... Cool :) > A few suggestions... > * Hierarchical package list - also, since with Metacello the convention is > (e.g. P-Core, P-UI, P-Tests) with no overarching package, it should group > all packages matching P-*, even if they are technically separate packages We thought of that, but first, we had to make the tree widgets faster :) > * I miss the search bar from OB where I could just start typing as soon as I > opened the window. It seems that Nautilus doesn't set the keyboard focus > anywhere useful. This is strange, the focus should be at the nice place (like class if you browse a class, method if you browse a method and so on) I will check that. > Options: > - search bar I will keep that in mind ;) > - typing brings up the class search dialog > - give keyboard focus to the package list so I can use the shortcuts right > away. This may be the best one because I have access to 3 options: > - cmd-F to search packages > - cmd-f to search classes > - start typing to do a basic package search As I said, the focus should be there. > * creating new methods - when you click a protocol name, the > "messageSelectorAndArgumentNames" template is displayed in the code pane, > and is pre-selected. I found this very confusing as a newbie because the > selection made me think that I could start typing to replace the template, > but the keyboard focus is not on the template. It's also useless because > when you click on the code pane, it unselects, so you have to double-click > anyway. True ! I already notice that ^^ To be honest, I just copy/paste the behavior from the default browser, but I will change that soon ^^ > Two suggestions > - from the class pane, protocol pane, or both, have an "add method" menu > item that transfers focus to the preselected template > - when just clicking on a protocol, don't pre-select the template > * back/forward buttons for history navigation? They use to be there, I will reintroduce them :) > * a centralized place to put/list plugins so we can share them I have now idea how to do that except creating a dedicated repository :) > > Many thanks to Benjamin. This was sorely needed! > > Cheers, > Sean > Thanks to you for your feedback and your good ideas :) Ben > -- > View this message in context: http://forum.world.st/Nautilus-first-impression-tp4578301p4578301.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

April 22, 2012