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

[Pharo-project] Adding hooks for well known events in morphic
by Guillermo Polito May 3, 2012

May 3, 2012

I've made up a list with all the useful morphic widget I've found in a alpha alpha alpha 2.0 image. I'd like to put in those widgets empty hooks like: Morph>>triggerOnShow "hook" for common events widgets provide usually in MVC frameworks. That means *not changing the whole interface nor refactoring everything*. *Just adding the hooks*. What we were talking with Mariano (I hate you for putting ideas in my head) today in the train was to add those empty hooks and put senders for them, what should be easy. This way we can start to homogenize morphic a bit. Most likely, in a not so far future, those empty hooks could be replaced by something like: Morph>>triggerOnShow self announcer announce: (MorphShowAnnouncement show: self) Now, here is a list of the most important widgets i've found (I could've missed some) and events they should trigger. I'm not taking into account new multitouch interfaces and stuff. For all widgets onShow onDelete onKeyUp onKeyPress onKeyDown onClick onMouseDown onMouseUp onDoubleClick onDragged onDropped onMove? onResize? For all containers onChildAdded onChildRemoved "Widgets" Check/Radio -> CheckboxButtonMorph/SimpleSwitchMorph onSelectionChanged List/Grids -> PluggableListMorph/PluggableMultiColumnListMorph/LazyListMorph/MulticolumnLazyListMorph onSelectionChanged Button -> PluggableButtonMorph/SimpleButtonMorph/MultistateButtonMorph onClick Label -> LabelMorph/FuzzyLabelMorph /MultistateLabelMorph Progress Bar-> SystemProgressBarMorph Slider -> Slider/PluggableSliderMorph onSelectionChanged Text handling -> TextMorph/PluggableTextMorph onSelectionChanged Field Handling -> PluggableTextFieldMorph/PluggableTextEditorMorph Tree -> MorphTreeMorph onSelectionChanged onExpandItem onCollapseItem Combo box -> DropListMorph/EditableDropListMorph /SearchMorph/MorphDropListMorph onSelectionChanged Menues -> MenuMorph + friends onClick (for menu item probably) Image -> ImageMorph/ImagePreviewMorph Diff -> DiffMorph Color Presenter -> ColorPresenterMorph Color chooser -> ColorChooserMorph/HSVColorSelectorMorph / SVColorSelectorMorph onSelectionChanged Task var -> TaskbarMorph "Containers" ScrollPane Windows -> SystemWindow/PluggableSystemWindow /StandardWindow Dialog window -> DialogWindow & (lots of) subclasses Panel -> PanelMorph & subclasses / PluggablePanelMorph Tabs -> TabGroupMorph (Other Tab stuff -> PluggableTabBarMorph + PluggableTabButtonMorph ) onSelectionChanged Guille

5 8

[Pharo-project] What about making the configuration browser more visible?
by Guillermo Polito May 3, 2012

May 3, 2012

What about naming it "Package Loader" or "Package center" or something like that? And putting it in the main menu instead of inside of Tools? I want people who open pharo for the first time to say "Hey, here I can download stuff!!!" Guille

9 32

[Pharo-project] Mouse handler on a morph
by Erwan Douaille May 3, 2012

May 3, 2012

Hi. I would like to know if it's possible to add a mouse handler on a specific morph ? I have a window and i would like to know the position of my mouse only in this window. For exemple i also use : self on: #mouseDown send: #captureMouse: to: self. But it give me the mouse position in pharo environment and not only in my window. Thanks :) -- Douaille Erwan <douaille.erwan(a)gmail.com>

4 4

[Pharo-project] Enable #alwaysOpenFullDebugger: and fastDragging:
by Mariano Martinez Peck May 3, 2012

May 3, 2012

Hi guys. There are 2 settings that I ALWAYS need to change and I think it would be nice to have them by default: 1) Always show debugger and avoid pre-debugger windows. It makes no sense for development. It takes you the double of time. What does the pre-debug brings you? nothing. If you want to proceed, then the debugger also has that option. If you want to abandon, you can just close the debugger. So, we should enable this. If someone wanst the pre-debugger fwindows for a reasons, then he should enable it. 2) Fast dragging. The normal dragging is slow in old machines and slow when there are lots of opened windows. The fast drag is much faster and nicer because since it is transparent you can even see what is below. Let's do a quick survey. We have 24 hrs. Do not vote if you didn't try it. I start: Debugger alwaysOpenFullDebugger: true. +1 UITheme currentSettings fastDragging: true. +1 Cheers -- Mariano http://marianopeck.wordpress.com

4 3

Re: [Pharo-project] [update 2.0] #20038
by Marcus Denker May 3, 2012

May 3, 2012

On May 3, 2012, at 2:01 PM, StÃ©phane Ducasse wrote: > > On May 2, 2012, at 2:12 PM, Marcus Denker wrote: > >> Issue 5738: do allow the same ivar in the hierarchy >> http://code.google.com/p/pharo/issues/detail?id=5738 > > Do we really want to let the user define instance variables duplicated in the class hierarchy? > I think that this is not really a good move. But I did not browse the issue because I do not have internet. > How then do you move a variable up in the hierarchy? Marcus -- Marcus Denker -- http://marcusdenker.de

3 2

[Pharo-project] [update 1.4] #14440
by Esteban Lorenzano May 3, 2012

May 3, 2012

14440 ----- 5773: Have access to the original event in PLuggableButtonMorph http://code.google.com/p/pharo/issues/detail?id=5773 5584: File Browser not recognizing cs and st if filename has more than one point http://code.google.com/p/pharo/issues/detail?id=5584 5667: Renaming a file just deletes it due to missing #fileNameFromFormattedItem: http://code.google.com/p/pharo/issues/detail?id=5667

1 0

[Pharo-project] A simple getenv primitive
by Damien Cassou May 3, 2012

May 3, 2012

Hi, I can't find any getenv primitive that would allow me to access environment an variable value from its name. This could be really helpful to get the HOME directory for example. Does one such primitive exist? If not, why? It looks trivial to implement for linux, and it is potentially also easy on Windows and Mac OS. I'm willing to try if necessary. Thank you -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

2 2

Re: [Pharo-project] Enable #alwaysOpenFullDebugger: and fastDragging:
by Marcus Denker May 3, 2012

May 3, 2012

On May 3, 2012, at 10:10 AM, Mariano Martinez Peck wrote: > Hi guys. There are 2 settings that I ALWAYS need to change and I think it would be nice to have them by default: > > 1) Always show debugger and avoid pre-debugger windows. It makes no sense for development. It takes you the double of time. What does the pre-debug brings you? nothing. If you want to proceed, then the debugger also has that option. If you want to abandon, you can just close the debugger. So, we should enable this. If someone wanst the pre-debugger fwindows for a reasons, then he should enable it. > > 2) Fast dragging. The normal dragging is slow in old machines and slow when there are lots of opened windows. The fast drag is much faster and nicer because since it is transparent you can even see what is below. > > Let's do a quick survey. We have 24 hrs. Do not vote if you didn't try it. > > I start: > > Debugger alwaysOpenFullDebugger: true. +1 > UITheme currentSettings fastDragging: true. +1 > Please do a doodle. We have already too many mails on the mailinglist. -- Marcus Denker -- http://marcusdenker.de

6 10

Re: [Pharo-project] Enable #alwaysOpenFullDebugger: and fastDragging:
by Marcus Denker May 3, 2012

May 3, 2012

On May 3, 2012, at 10:16 AM, Mariano Martinez Peck wrote: > > > On Thu, May 3, 2012 at 10:13 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On May 3, 2012, at 10:10 AM, Mariano Martinez Peck wrote: > > > Hi guys. There are 2 settings that I ALWAYS need to change and I think it would be nice to have them by default: > > > > 1) Always show debugger and avoid pre-debugger windows. It makes no sense for development. It takes you the double of time. What does the pre-debug brings you? nothing. If you want to proceed, then the debugger also has that option. If you want to abandon, you can just close the debugger. So, we should enable this. If someone wanst the pre-debugger fwindows for a reasons, then he should enable it. > > > > 2) Fast dragging. The normal dragging is slow in old machines and slow when there are lots of opened windows. The fast drag is much faster and nicer because since it is transparent you can even see what is below. > > > > Let's do a quick survey. We have 24 hrs. Do not vote if you didn't try it. > > > > I start: > > > > Debugger alwaysOpenFullDebugger: true. +1 > > UITheme currentSettings fastDragging: true. +1 > > > > Please do a doodle. We have already too many mails on the mailinglist. > > I was trying to be diplomatic. Ok: http://code.google.com/p/pharo/issues/detail?id=5787 > FixToInclude. No more emails ;) What I want to *not* have are 580 emails of people saying +1 or -1 There is for sure some website for doing a vote? I thought doodle added that? Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] grabbing morphs in 2.0
by Francisco Garau May 3, 2012

May 3, 2012

Hi - up until 1.4 doing ctrl-click on any morph would bring up a menu for the clicked morph. This is not happening any more in 2.0. Shall I open an issue for it? - Francisco

2 1