- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Tabs and back button in browser?

by StÃ©phane Ducasse

I would love but time/money usual problem. Not lack of vision or will. Stef On Jan 24, 2011, at 2:47 PM, Janko MivÅ¡ek wrote: > Hi Pharoers, > > Are you thinking about introducing tabs and back/forward button, like in > web browsers? > > Just because of web we are now all accustomized and used of tabbed > browsing and navigation with a back and forward buttons. This habit now > demands all other tools to follow. Tabs are now everywhere, also in > Smalltalk. Look at Visualworks, also Dolphin. > > Introducing tabs soon in Pharo will therefore greatly improve user > experience, so if someone would spend some time on it, his contribution > will be very valuable! > > Best regards > Janko > > > -- > Janko MivÅ¡ek > AIDA/Web > Smalltalk Web Application Server > http://www.aidaweb.si >

Jan. 24, 2011

Re: [Pharo-project] Hapao for Test coverage!

by StÃ©phane Ducasse

This is cool to have news! Excellent idea. I will try to help you to post regularly. On Jan 24, 2011, at 11:01 AM, Marcus Denker wrote: > On Thu, Jan 20, 2011 at 6:41 PM, Vanessa PeÃ±a <vane.c.pena(a)gmail.com> wrote: >> Hello all, >> >> We are happy to introduce you Hapao, an innovative test coverage tool which >> gives you an intuitive graphical representation to visually assess the >> quality of the coverage. >> >> For more information and download you can visit us at: >> http://hapao.dcc.uchile.cl/ >> Of course, all feedback is always welcome :) >> > Very nice! > > One small thing: the dialog selecting the packages at the beginning should > label the button "continue"", not "terminate" (which sounds like cancel to me). > > I added a blog post: http://pharo-project.org/news > > > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de >

Jan. 24, 2011

Re: [Pharo-project] whisker browser

by StÃ©phane Ducasse

I should have the code but only for a 3.8 or older version. With the code gary sent around it would be cool to build it. Stef On Jan 24, 2011, at 10:12 AM, Tudor Girba wrote: > Hi, > > Does anybody have an image with a working Whisker Browser? I would be interested in learning from it. > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Next time you see your life passing by, say 'hi' and get to know her." > > > >

Jan. 24, 2011

[Pharo-project] Issue 3590 in pharo: AntiAliased fix

by pharo＠googlecode.com

Status: Fixed Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3590 by stephane...(a)gmail.com: AntiAliased fix http://code.google.com/p/pharo/issues/detail?id=3590 Out of curiosity, I executed your code in Squeak and the antialiasing > works there. Debugging a little, I found a difference in > BalloonCanvas>>#line:to:width:color:. If you update Pharo's > implementation with Squeak's one it works in Pharo as well. > There might be other differences so you might look into that. Thanks Ricardo Moran Attachments: BalloonCanvas-linetowidthcolor.st 451 bytes

Jan. 24, 2011

Re: [Pharo-project] doc on ob requests and commands

by Lukas Renggli

Performing a user interaction always goes through signaling the notification. For example to request a text input: expression := OBTextRequest new prompt: 'Enter a matching expression'; signal Or to open the completion dialog: category := OBCompletionRequest new assisted: true; collection: categories; prompt: 'Add Category'; signal Or to open a new browser: view := OBBrowseRequest new browser: OBSystemBrowser new; signal Note that Morphic raises some interaction notifications in a very hackish too (with information stuffed into arrays and dictionaries) when opening some (of course not all) of the user interactions. OB implemented its own user interaction mechanism long before Morphic was improved and also to remain independent of the platform/view. Lukas On 24 January 2011 13:07, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi Lukas, > > On 24 Jan 2011, at 15:57, Lukas Renggli wrote: > >>> My main current question is what are the reasons for OBInteractionRequest to subclass Notification? >> >> To be able to perform user interactions anywhere without having a >> global OBPlatform instance, and without having to pass OBPlatform in >> or store OBPlatform anywhere. There can be multiple UI platforms >> active at the same time and they can even change over the lifetime of >> a single browser window. > > I am not sure I understand. Why did it have to be a subclass of Notification? Would it not be enough to have it as a subclass of Object? > > Cheers, > Doru > > > >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > -- > www.tudorgirba.com > > "The coherence of a trip is given by the clearness of the goal." > > > > > > -- Lukas Renggli www.lukas-renggli.ch

Jan. 24, 2011

Re: [Pharo-project] doc on ob requests and commands

by Dale Henrichs

On 01/24/2011 01:07 PM, Tudor Girba wrote: > Hi Lukas, > > On 24 Jan 2011, at 15:57, Lukas Renggli wrote: > >>> My main current question is what are the reasons for OBInteractionRequest to subclass Notification? >> >> To be able to perform user interactions anywhere without having a >> global OBPlatform instance, and without having to pass OBPlatform in >> or store OBPlatform anywhere. There can be multiple UI platforms >> active at the same time and they can even change over the lifetime of >> a single browser window. > > I am not sure I understand. Why did it have to be a subclass of Notification? Would it not be enough to have it as a subclass of Object? > > Cheers, > Doru Doru, They are subclasses of Notification so that exception handlers can be used to intercept the notification and do something different than prompt the user for the request ... the defaultAction of the exception triggers the UI to prompt the user with an appropriate dialog box... Dale

Jan. 24, 2011

Re: [Pharo-project] Graphics with Anti-Aliasing

by StÃ©phane Ducasse

tx On Jan 23, 2011, at 11:07 PM, Ricardo Moran wrote: > Yes, just load the attached file. > > Cheers > Richo > > On Sun, Jan 23, 2011 at 6:06 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > ricardo could you send the code (squeak version) around so that we can try? > > Stef > > On Jan 23, 2011, at 9:13 PM, Ricardo Moran wrote: > > > Mmmm... maybe it is platform related. I really don't know. I'm on Windows XP. > > > > Pharo version: Pharo1.2rc1 of 18 January 2011 update 12311 > > Squeak version: Squeak4.2alpha of 4 January 2011 update 10854 > > Vm version: Squeak3.10.2 of ''5 June 2008'' [latest update: #7179] > > > > On Sun, Jan 23, 2011 at 5:00 PM, Udo Schneider <udo.schneider(a)homeaddress.de> wrote: > > Hi Richo, > > > > could you tell me which Image/VM/OS you where using? > > > > On my System (Mac OS X 10.6.6) Pharo 1.1 and Squeak 4.1 on Cog VM (r2349) and regular VM (4.2.5beta1U) both show no antialiasing (image attached) > > > > Is this maybe somehow platform/plugin related? > > > > Best Regards, > > > > Udo > > > > > > > > On 23.01.11 20:28, Ricardo Moran wrote: > > Hi Udo, > > > > Out of curiosity, I executed your code in Squeak and the antialiasing > > works there. Debugging a little, I found a difference in > > BalloonCanvas>>#line:to:width:color:. If you update Pharo's > > implementation with Squeak's one it works in Pharo as well. > > There might be other differences so you might look into that. > > > > I hope this helps. > > Richo > > > > On Sun, Jan 23, 2011 at 4:09 PM, Udo Schneider > > <udo.schneider(a)homeaddress.de > > <mailto:udo.schneider@homeaddress.de>> wrote: > > > > All, > > > > I'm using the following code. IMHO the line is jagged ... but maybe > > I'm doing something wrong: > > > > form := Form extent: 640@480 depth: 32. > > "form fillWhite." > > canvas := BalloonCanvas on: form. > > canvas aaLevel: 4. > > canvas line: 0@0 to: 640@480 color: Color red. > > morph := ImageMorph new. > > morph image: form. > > morph openCenteredInWorld. > > "morph abandon." > > > > CU. > > > > Udo > > > > > > > > On 22.01.11 15:37, Udo Schneider wrote: > > > > All, > > > > does somebody has a pointer to a graphics lib/framework/engine > > for Pharo > > which works with Anti-Aliasing. > > > > My first tests with Balloon2D were disappointing (maybe I'm doing > > something wrong). But even setting aaLevel does not seem to > > bring any > > result. I.e. the line drawing code falls back to superclass code > > which > > simply draws the same jagged lines like always. > > > > Any pointers? > > > > CU, > > > > Udo > > > > > > > > > > > > > > > > > > > > <aatest.PNG> > > > > <BalloonCanvas-linetowidthcolor.st>

Jan. 24, 2011

Re: [Pharo-project] collapsing panes

by Tudor Girba

Hi Gary, On 24 Jan 2011, at 16:16, Gary Chambers wrote: > Hi, > I don't think the layouts can be merged, as such, as they have very different > approaches. > > With the TableLayout, it is possible to assign "weights" to each spaceFill > section to get what you want, I think. (see #spaceFillWeight:) I tried to use it, but I get no effect when I use it in your example. Below is one of my trouts (added spaceFillWeight: 10 to morph2). What am I doing wrong? | container morph1 morph2 morph3 ex1 ex2 ex3 sp1 sp2| morph1 := (PanelMorph new fillStyle: (SolidFillStyle color: Color red)) hResizing: #spaceFill; vResizing: #spaceFill. morph2 := (PanelMorph new fillStyle: (SolidFillStyle color: Color blue)) hResizing: #spaceFill; vResizing: #spaceFill; spaceFillWeight: 10. morph3 := (PanelMorph new fillStyle: (SolidFillStyle color: Color yellow)) hResizing: #spaceFill; vResizing: #spaceFill. ex1 := (UITheme builder newExpander: 'Red' for: morph1) expanded: true. ex2 := (UITheme builder newExpander: 'Blue' for: morph2) expanded: true. ex3 := (UITheme builder newExpander: 'Yellow' for: morph3) expanded: true. sp1 := EdgeGripMorph new target: ex1; edgeName: #bottom; vResizing: #rigid; extent: 24 @ ProportionalSplitterMorph splitterWidth; on: #mouseDown send: #expandedSizingRigid to: ex1. sp2 := EdgeGripMorph new target: ex2; edgeName: #bottom; vResizing: #rigid; extent: 24 @ ProportionalSplitterMorph splitterWidth; on: #mouseDown send: #expandedSizingRigid to: ex2. container := UITheme builder newColumn: { ex1. sp1. ex2. sp2. ex3}. container cellInset: 0. container extent: 400@400. container openInWindow. Cheers, Doru > Regards, Gary > > ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Monday, January 24, 2011 2:32 PM > Subject: Re: [Pharo-project] collapsing panes > > > Thanks a lot, Gary! I gave it a try and it does go in the wanted direction. > > Now, the next question. I see that you are using a TableLayout. Is there a way to specify a proportion (like in the proportional layout?) for the initial extent of the inner panes? > > If yes, then I suppose we could merge the two layouts into one. > > Cheers, > Doru > > > On 24 Jan 2011, at 14:51, Benjamin wrote: > >> I love that :) >> It could be very useful ^^ >> >> >> Ben >> >> On Jan 24, 2011, at 2:36 PM, Gary Chambers wrote: >> >>> Tricky... >>> Just an experiment, but try the following after filing in attached change set. >>> Can make the re-proportioning explicit and maybe fix things to constrain to >>> the owner morph if interested... >>> >>> >>> | container morph1 morph2 morph3 ex1 ex2 ex3 sp1 sp2| >>> morph1 := (PanelMorph new fillStyle: (SolidFillStyle color: Color red)) >>> hResizing: #spaceFill; >>> vResizing: #spaceFill. >>> morph2 := (PanelMorph new fillStyle: (SolidFillStyle color: Color blue)) >>> hResizing: #spaceFill; >>> vResizing: #spaceFill. >>> morph3 := (PanelMorph new fillStyle: (SolidFillStyle color: Color yellow)) >>> hResizing: #spaceFill; >>> vResizing: #spaceFill. >>> ex1 := (UITheme builder newExpander: 'Red' for: morph1) >>> expanded: true. >>> ex2 := (UITheme builder newExpander: 'Blue' for: morph2) >>> expanded: true. >>> ex3 := (UITheme builder newExpander: 'Yellow' for: morph3) >>> expanded: true. >>> sp1 := EdgeGripMorph new >>> target: ex1; >>> edgeName: #bottom; >>> vResizing: #rigid; >>> extent: 24 @ ProportionalSplitterMorph splitterWidth; >>> on: #mouseDown send: #expandedSizingRigid to: ex1. >>> sp2 := EdgeGripMorph new >>> target: ex2; >>> edgeName: #bottom; >>> vResizing: #rigid; >>> extent: 24 @ ProportionalSplitterMorph splitterWidth; >>> on: #mouseDown send: #expandedSizingRigid to: ex2. >>> container := UITheme builder newColumn: { >>> ex1. >>> sp1. >>> ex2. >>> sp2. >>> ex3}. >>> container cellInset: 0. >>> container extent: 400@400. >>> container openInWindow. >>> >>> >>> >>> Have a play/fun. >>> >>> Regards, Gary >>> >>> ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> >>> To: "Pharo-project(a)lists.gforge.inria.fr Development" <pharo-project(a)lists.gforge.inria.fr> >>> Sent: Friday, January 21, 2011 11:18 PM >>> Subject: [Pharo-project] collapsing panes >>> >>> >>> Hi, >>> >>> I have a question about how to obtain an effect similar to minimizing a pane in Eclipse. Let's consider the example from below. I have a ProportionalLayout because I want to fill the entire space and be able to resize the inside panes. Now, I would also like to have some way of collapsing one of the panes and have the rest resize to fill the rest of the space. It's a bit like I would need some part of a behavior from the TableLayout. >>> >>> Can anyone provide me with some hints in this direction? Do I need to create a new Layout? >>> >>> | container morph1 morph2 morph3 window | >>> container := PanelMorph new. >>> morph1 := PanelMorph new fillStyle: (SolidFillStyle color: Color red). >>> morph2 := PanelMorph new fillStyle: (SolidFillStyle color: Color blue). >>> morph3 := PanelMorph new fillStyle: (SolidFillStyle color: Color yellow). >>> container changeProportionalLayout. >>> container addMorph: morph1 fullFrame: (LayoutFrame fractions: (0 @ 0 corner: 1 @ 0.33)). >>> container addMorph: morph2 fullFrame: (LayoutFrame fractions: (0 @ 0.33 corner: 1 @ 0.66)). >>> container addMorph: morph3 fullFrame: (LayoutFrame fractions: (0 @ 0.66 corner: 1 @ 1)). >>> container addPaneSplitters. >>> container fillStyle: (SolidFillStyle color: Color yellow). >>> container extent: 400@400. >>> container openInWindow. >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Be rather willing to give than demanding to get." >>> >>> >>> >>> <ExpanderTweak.1.cs> >> >> > > -- > www.tudorgirba.com > > "Every now and then stop and ask yourself if the war you're fighting is the right one." > > > > > -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

Jan. 24, 2011

Re: [Pharo-project] collapsing panes

by StÃ©phane Ducasse

Yes we want more and a class to encapsulate that logic. Stef On Jan 24, 2011, at 2:51 PM, Benjamin wrote: > I love that :) > It could be very useful ^^ > > > Ben > > On Jan 24, 2011, at 2:36 PM, Gary Chambers wrote: > >> Tricky... >> Just an experiment, but try the following after filing in attached change set. >> Can make the re-proportioning explicit and maybe fix things to constrain to >> the owner morph if interested... >> >> >> | container morph1 morph2 morph3 ex1 ex2 ex3 sp1 sp2| >> morph1 := (PanelMorph new fillStyle: (SolidFillStyle color: Color red)) >> hResizing: #spaceFill; >> vResizing: #spaceFill. >> morph2 := (PanelMorph new fillStyle: (SolidFillStyle color: Color blue)) >> hResizing: #spaceFill; >> vResizing: #spaceFill. >> morph3 := (PanelMorph new fillStyle: (SolidFillStyle color: Color yellow)) >> hResizing: #spaceFill; >> vResizing: #spaceFill. >> ex1 := (UITheme builder newExpander: 'Red' for: morph1) >> expanded: true. >> ex2 := (UITheme builder newExpander: 'Blue' for: morph2) >> expanded: true. >> ex3 := (UITheme builder newExpander: 'Yellow' for: morph3) >> expanded: true. >> sp1 := EdgeGripMorph new >> target: ex1; >> edgeName: #bottom; >> vResizing: #rigid; >> extent: 24 @ ProportionalSplitterMorph splitterWidth; >> on: #mouseDown send: #expandedSizingRigid to: ex1. >> sp2 := EdgeGripMorph new >> target: ex2; >> edgeName: #bottom; >> vResizing: #rigid; >> extent: 24 @ ProportionalSplitterMorph splitterWidth; >> on: #mouseDown send: #expandedSizingRigid to: ex2. >> container := UITheme builder newColumn: { >> ex1. >> sp1. >> ex2. >> sp2. >> ex3}. >> container cellInset: 0. >> container extent: 400@400. >> container openInWindow. >> >> >> >> Have a play/fun. >> >> Regards, Gary >> >> ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> >> To: "Pharo-project(a)lists.gforge.inria.fr Development" <pharo-project(a)lists.gforge.inria.fr> >> Sent: Friday, January 21, 2011 11:18 PM >> Subject: [Pharo-project] collapsing panes >> >> >> Hi, >> >> I have a question about how to obtain an effect similar to minimizing a pane in Eclipse. Let's consider the example from below. I have a ProportionalLayout because I want to fill the entire space and be able to resize the inside panes. Now, I would also like to have some way of collapsing one of the panes and have the rest resize to fill the rest of the space. It's a bit like I would need some part of a behavior from the TableLayout. >> >> Can anyone provide me with some hints in this direction? Do I need to create a new Layout? >> >> | container morph1 morph2 morph3 window | >> container := PanelMorph new. >> morph1 := PanelMorph new fillStyle: (SolidFillStyle color: Color red). >> morph2 := PanelMorph new fillStyle: (SolidFillStyle color: Color blue). >> morph3 := PanelMorph new fillStyle: (SolidFillStyle color: Color yellow). >> container changeProportionalLayout. >> container addMorph: morph1 fullFrame: (LayoutFrame fractions: (0 @ 0 corner: 1 @ 0.33)). >> container addMorph: morph2 fullFrame: (LayoutFrame fractions: (0 @ 0.33 corner: 1 @ 0.66)). >> container addMorph: morph3 fullFrame: (LayoutFrame fractions: (0 @ 0.66 corner: 1 @ 1)). >> container addPaneSplitters. >> container fillStyle: (SolidFillStyle color: Color yellow). >> container extent: 400@400. >> container openInWindow. >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Be rather willing to give than demanding to get." >> >> >> >> <ExpanderTweak.1.cs> > >

Jan. 24, 2011

Re: [Pharo-project] doc on ob requests and commands

by Tudor Girba

Hi Lukas, On 24 Jan 2011, at 15:57, Lukas Renggli wrote: >> My main current question is what are the reasons for OBInteractionRequest to subclass Notification? > > To be able to perform user interactions anywhere without having a > global OBPlatform instance, and without having to pass OBPlatform in > or store OBPlatform anywhere. There can be multiple UI platforms > active at the same time and they can even change over the lifetime of > a single browser window. I am not sure I understand. Why did it have to be a subclass of Notification? Would it not be enough to have it as a subclass of Object? Cheers, Doru > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > -- www.tudorgirba.com "The coherence of a trip is given by the clearness of the goal."

Jan. 24, 2011