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

Re: [Pharo-project] OB column width resizing

by StÃ©phane Ducasse

Igor do you have your code somewhere? Stef On Jun 18, 2011, at 2:47 PM, Schwab,Wilhelm K wrote: > Stef, > > I had missed it. Fernando raises some good points about the layout manager. One of the ways I have historically solved some of the problems that arise is to use "way too many"<g> nested containers. > > Consider making a list of several labeled text fields for a dialog box. One approach to that is a pair of vertical proportional layouts, one with the labels (each aligning text to the right) and another with the fields. Put both of them in another container to size them to available space in something else. > > Igor and Fernando reminded me of something I failed to mention about Dolphin: the layout manager of a container forces particular types for the managed subviews' #arrangement. ProportionalLayout wants numbers; FramingLayout wants things very similar to what exists in Pharo. Framing layout is very powerful, but nested proportionals can often to pretty much the same thing and often with far less anguish. > > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > Sent: Saturday, June 18, 2011 3:01 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] OB column width resizing > > bill > > did you check the idea of igor about layout that acts as anchors? > > Stef > > > On Jun 17, 2011, at 11:49 PM, Schwab,Wilhelm K wrote: > >> As my Pharo MVP framework grows, I am starting to miss Dolphin's layout managers. The voodoo of automatically inserting splitters is, IMHO, time thrown after bad. We should instead have easy-to-use widgets that do what one expects and then explicitly place them where they belong. >> >> Dolphin's proportional layouts can be set as horizontal or vertical, and one can add splitters to allow the proportions to be changed. An aspect called #arrangement can be set to zero to make something fixed size or to any number which then becomes that much out of the sum of peer #arrangement values. >> >> My first priority is to get any type of layout that is reliable with deeply nested composites. Not there yet :( >> >> Bill >> >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Sean P. DeNigris [sean(a)clipperadams.com] >> Sent: Friday, June 17, 2011 4:00 PM >> To: pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] OB column width resizing >> >> Lukas Renggli wrote: >>> >>> See >>> http://groups.google.com/group/omnibrowser-dev/browse_thread/thread/3957238… >>> >> >> Thx :( >> >> -- >> View this message in context: http://forum.world.st/OB-column-width-resizing-tp3606264p3606347.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> > > >

June 18, 2011

[Pharo-project] roadmap for 1.4

by StÃ©phane Ducasse

Hi guys here is a kind of dump of roadmap for 1.4 first level is to make sure that we have only one single image. - load FileSystem -> so that we can start to integrate and improve the fileSystem API - Load shout, Ocompletion, RBEngine (not OB) so that we can change what should be changed for RPackage to work - Ring -> so that we can start to integrate it - Fuel -> so that we can deprecate SmartRefStream (there may be a problem with mcz (not sure)). - I want Opal in 1.4 too. - continue to remove StringHolder hierarchy - Morphic improvements Comments are welcomed. Stef

June 18, 2011

Re: [Pharo-project] TWM and Keymapping

by StÃ©phane Ducasse

On Jun 18, 2011, at 12:18 AM, laurent laffont wrote: > On Fri, Jun 17, 2011 at 3:58 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > BTW, thanks for pushing this! :) > > > Indeed, actually I hope Keymapping + TWM + WindowOrganizer will be in 1.4 so we can have a more productive IDE. What I would really like is to be able to load packages in one click but I cannot find the time to work on this idea of distribution repository. Now I would like to see how we can integrate Keymapping for now the plan for 1.4 is described in the next mail Please comment it. Stef

June 18, 2011

Re: [Pharo-project] OB column width resizing

by Schwab,Wilhelm K

Stef, I had missed it. Fernando raises some good points about the layout manager. One of the ways I have historically solved some of the problems that arise is to use "way too many"<g> nested containers. Consider making a list of several labeled text fields for a dialog box. One approach to that is a pair of vertical proportional layouts, one with the labels (each aligning text to the right) and another with the fields. Put both of them in another container to size them to available space in something else. Igor and Fernando reminded me of something I failed to mention about Dolphin: the layout manager of a container forces particular types for the managed subviews' #arrangement. ProportionalLayout wants numbers; FramingLayout wants things very similar to what exists in Pharo. Framing layout is very powerful, but nested proportionals can often to pretty much the same thing and often with far less anguish. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] Sent: Saturday, June 18, 2011 3:01 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] OB column width resizing bill did you check the idea of igor about layout that acts as anchors? Stef On Jun 17, 2011, at 11:49 PM, Schwab,Wilhelm K wrote: > As my Pharo MVP framework grows, I am starting to miss Dolphin's layout managers. The voodoo of automatically inserting splitters is, IMHO, time thrown after bad. We should instead have easy-to-use widgets that do what one expects and then explicitly place them where they belong. > > Dolphin's proportional layouts can be set as horizontal or vertical, and one can add splitters to allow the proportions to be changed. An aspect called #arrangement can be set to zero to make something fixed size or to any number which then becomes that much out of the sum of peer #arrangement values. > > My first priority is to get any type of layout that is reliable with deeply nested composites. Not there yet :( > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Sean P. DeNigris [sean(a)clipperadams.com] > Sent: Friday, June 17, 2011 4:00 PM > To: pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] OB column width resizing > > Lukas Renggli wrote: >> >> See >> http://groups.google.com/group/omnibrowser-dev/browse_thread/thread/3957238… >> > > Thx :( > > -- > View this message in context: http://forum.world.st/OB-column-width-resizing-tp3606264p3606347.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

June 18, 2011

Re: [Pharo-project] TWM and Keymapping

by laurent laffont

> > Something I want to fix: if an editor has the focus, TWM shortcuts don't >> work. >> > I've tried: >> >> TilingTWMSettings class>>buildKeyMappingSettingsOn: aBuilder >> <keymap> >> ..... >> {PasteUpMorph. SystemWindow. TextEditor. SmalltalkEditor} >> do: [:aClass| aBuilder attachShortcutCategory: #twmShortcut to: aClass ]. >> >> but no success ..... >> > > Probably the TextEditor overrides a shortcut in a non desired way... Does > it happen for every twm shortcut? > Yes, as soon as a text editor / entry / field is selected, TWM shortcuts don't work... Here's the default shortcuts for TWM, maybe $w command is not a good idea for a prefix ? shortcuts ^ { #minimizeAllWindows -> 'Minimize all windows' -> [$w command, $m command]. #maximizeAllWindows -> 'Maximize all windows' -> [$w command, $m shift command]. #tileVisibleWindows -> 'Tile visible windows' -> [$w command, $t command]. #tileLastUsedWindows -> 'Tile last used windows' -> [$w command, $l command]. #tileBrowsers -> 'Tile browsers' -> [$w command, $b command]. #tileWorkspaces -> 'Tile workspaces' -> [$w command, $z command]. #tileTesters -> 'Tile testers' -> [$w command, $s command]. #tileMonticellos -> 'Tile monticellos' -> [$w command, $c command]. #tileInspectors -> 'Tile inspectors' -> [$w command, $i command]. #tileDebuggers -> 'Tile debuggers' -> [$w command, $d command]. #tileChanges -> 'Tile changes' -> [$w command, $c shift command]. #tileTools -> 'Tile tools' -> [$w command, $t shift command]. #tileSystem -> 'Tile system windows' -> [$w command, $y command]. #snapshotWorld -> 'Snapshot current world state' -> [$r command, $s command]. #worldBackward -> 'Move to previous world state' -> [$r command, $p command]. #worldForward -> 'Move to next world state' -> [$r command, $n command]. #deleteCurrentSnapshot -> 'Delete current world state' -> [$r command, $d command]. #topWindowMoveLeft -> 'Move window to left area' -> [$w command, $1]. #topWindowMoveRight -> 'Move window to right area' -> [$w command, $2]. #topWindowMoveTop -> 'Move window to top area' -> [$w command, $3]. #topWindowMoveBottom -> 'Move window to bottom area' -> [$w command, $4]. #topWindowMoveTopLeft -> 'Move window to top left area' -> [$w command, $5]. #topWindowMoveTopRight -> 'Move window to top right area' -> [$w command, $6]. #topWindowMoveBottomLeft -> 'Move window to bottom left area' -> [$w command, $7]. #topWindowMoveBottomRight -> 'Move window to bottom right area' -> [$w command, $8]. } > We should write a testcase... > How can I test this ? Laurent. > > >> >> >> >> Laurent Laffont - @lolgzs <http://twitter.com/#%21/lolgzs> >> >> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >> Blog: http://magaloma.blogspot.com/ >> Developer group: http://cara74.seasidehosting.st >> >> >

June 18, 2011

Re: [Pharo-project] something never happened before

by StÃ©phane Ducasse

Yes We are discussing with the guy of SmalltalkHub and I hope that we will get something cool soon.... Stef On Jun 18, 2011, at 9:21 AM, Norbert Hartl wrote: > > > Am 17.06.2011 um 22:45 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > >> hey, guess what! >> >> squeaksource is down! >> > What a shitty indicator of success, right? :) > > Norbert >

June 18, 2011

Re: [Pharo-project] Integer>>#factorial

by StÃ©phane Ducasse

> Mathematical recreation ? > The sake of complexifty ? (it's fun when you can't even understand > your own question after reading the answers). > Maybe you should ask Paul Bauman about his motivation. :)

June 18, 2011

Re: [Pharo-project] SS is down

by Johan Brichau

I wonder: why is there not automatic restart script? It seems a bit silly that a human is now part of the squeaksource system itself... to restart it. On 18 Jun 2011, at 08:54, laurent laffont wrote: > ....... sad because it's raining here ...... > > Laurent

June 18, 2011

Re: [Pharo-project] Integer>>#factorial

by Nicolas Cellier

Mathematical recreation ? The sake of complexifty ? (it's fun when you can't even understand your own question after reading the answers). Maybe you should ask Paul Bauman about his motivation. Nicolas 2011/6/18 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Is there an interest for security or other points? > > Stef > > On Jun 16, 2011, at 12:38 PM, Sven Van Caekenberghe wrote: > >> Hi, >> >> On Planet Smalltalk I read about this challenge: http://www.parcplace.net/list/vwnc-archive/1106/msg00080.html the goal being to optimize the current, naive Integer>>#factorial implementation. >> >> I had some old Lisp code hanging around, implementing an algorithm that I once found somewhere, and I ported it to Smalltalk. I am sure there are faster solutions, but this one is twice as fast as the original while still being easy to understand and it has a useful, safe helper method: >> >> Integer>>#svcFactorial >> Â Â Â "Answer the factorial of the receiver." >> >> Â Â Â self = 0 ifTrue: [ ^ 1 ]. >> Â Â Â self > 0 ifTrue: [ ^ 1 productUpTo: self ]. >> Â Â Â self error: 'Not valid for negative integers' >> >> Integer>>#productUpTo: anInteger >> Â Â Â "Answer the product of all integers from the receiver (non-inclusive) up to anInteger (inclusive)." >> >> Â Â Â | difference split | >> Â Â Â self assert: (self between: 0 and: anInteger). >> Â Â Â "the idea is to multiply LargePositiveIntegers of approximately the same size" >> Â Â Â difference := anInteger - self. >> Â Â Â difference = 0 ifTrue: [ ^ 1 ]. >> Â Â Â difference = 1 ifTrue: [ ^ anInteger ]. >> Â Â Â difference = 2 ifTrue: [ ^ (anInteger - 1) * anInteger ]. >> Â Â Â difference = 3 ifTrue: [ ^ (anInteger - 2) * (anInteger - 1) * anInteger ]. >> Â Â Â difference = 4 ifTrue: [ ^ (anInteger - 3) * (anInteger - 2) * (anInteger - 1) * anInteger ]. >> Â Â Â split := (self + anInteger) bitShift: -1. >> Â Â Â ^ (self productUpTo: split) * (split productUpTo: anInteger) >> >> Would it be a good idea to replace the current implementation with this one ? >> >> Sven >> >> > > >

June 18, 2011

Re: [Pharo-project] something never happened before

by Jorge Ressia

Hi guys, It is working On Sat, Jun 18, 2011 at 9:21 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > Am 17.06.2011 um 22:45 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > >> hey, guess what! >> >> squeaksource is down! >> > What a shitty indicator of success, right? :) > > Norbert > > -- Jorge Ressia www.jorgeressia.com

June 18, 2011