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

[Pharo-project] pharo-2.0-tests Â» 32,win - Build # 249 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

July 20, 2012

[Pharo-project] pharo-2.0-tests Â» 32,mac - Build # 248 - Failure!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

July 20, 2012

[Pharo-project] pharo-2.0-tests Â» 32,linux - Build # 248 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

July 20, 2012

[Pharo-project] pharo-2.0-tests Â» 32,win - Build # 248 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

July 20, 2012

Re: [Pharo-project] Double mouse down event

by Hilaire Fernandes

Ah, ok Sean fixed the problem in handleMouseDown: Released in Pharo Summer. Closed matter. Thanks Hilaire Le 20/07/2012 17:05, Hilaire Fernandes a Ã©crit : > While building a morph widget for tabular tools, I found two mouse down > event are sent to my TabGroupToolMorph. > > I have taken two screen shots of the debug trace, one for each mouse > down events. > > The stacks are not exactly the same > > Does it sound familiar to any of you? > > Thanks > > Hilaire >

July 20, 2012

[Pharo-project] pharo-2.0-tests Â» 32,linux - Build # 247 - Failure!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

July 20, 2012

[Pharo-project] pharo-2.0-tests Â» 32,win - Build # 247 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

July 20, 2012

[Pharo-project] Double mouse down event

by Hilaire Fernandes

While building a morph widget for tabular tools, I found two mouse down event are sent to my TabGroupToolMorph. I have taken two screen shots of the debug trace, one for each mouse down events. The stacks are not exactly the same Does it sound familiar to any of you? Thanks Hilaire

July 20, 2012

Re: [Pharo-project] Customizing the Caret of a PluggableTextMorph

by phil＠highoctane.be

So, there is the damn caret drawing code: Paragraph>>displaySelectionInLine: line on: aCanvas | leftX rightX w caretColor | selectionStart ifNil: [^self]. "No selection" aCanvas isShadowDrawing ifTrue: [ ^self ]. "don't draw selection with shadow" selectionStart = selectionStop ifTrue: ["Only show caret on line where clicked" selectionStart textLine ~= line ifTrue: [^self]] ifFalse: ["Test entire selection before or after here" (selectionStop stringIndex < line first or: [selectionStart stringIndex > (line last + 1)]) ifTrue: [^self]. "No selection on this line" (selectionStop stringIndex = line first and: [selectionStop textLine ~= line]) ifTrue: [^self]. "Selection ends on line above" (selectionStart stringIndex = (line last + 1) and: [selectionStop textLine ~= line]) ifTrue: [^self]]. "Selection begins on line below" leftX := (selectionStart stringIndex < line first ifTrue: [line ] ifFalse: [selectionStart ])left. rightX := (selectionStop stringIndex > (line last + 1) or: [selectionStop stringIndex = (line last + 1) and: [selectionStop textLine ~= line]]) ifTrue: [line right] ifFalse: [selectionStop left]. selectionStart = selectionStop ifTrue: [rightX := rightX + 1. w := self caretWidth. caretRect := (leftX-w) @ line top corner: (rightX+w)@ line bottom. self showCaret ifFalse:[^self]. caretColor := self insertionPointColor. 1 to: w do: [:i | "Draw caret triangles at top and bottom" aCanvas fillRectangle: ((leftX - w + i - 1) @ (line top + i - 1) extent: ((w - i) * 2 + 3) @ 1) color: caretColor. aCanvas fillRectangle: ((leftX - w + i - 1) @ (line bottom - i) extent: ((w - i) * 2 + 3) @ 1) color: caretColor]. aCanvas fillRectangle: (leftX @ line top corner: rightX @ line bottom) color: caretColor] ifFalse: [caretRect := nil. aCanvas fillRectangle: (leftX @ line top corner: rightX @ line bottom) color: self selectionColor] Paragraph class>>insertionPointColor has the color. I was fed up of blue, turned it red :-) This one is hardcoded and could take a hint from the selection color twiceDarker for example. Phil 2012/7/20 Denis Kudriashov <dionisiydk(a)gmail.com> > Hello > > 2012/7/20 Fernando Olivero <fernando.olivero(a)usi.ch> > >> Hi Sean, you can take a look at Athens-PangoCairo (in squeaksource). >> >> Using NativeBoost, i'm using the Pango layout library [1], and the >> Pango-Cairo binding [2], to avoid laying out text using the outdated >> (and messy) stuff in the image. >> >> Check out the classes: ParagraphDescription & AthensPangoCairoParagraph. >> >> I'm using them as the basis for the TextShape,LabelShape, and >> EditableTextShape in Shapes / Gaucho ( using TextEditor, >> SingleLineEditor ). >> >> Maybe somebody can do the same for Morphic? use Pango to layout the >> text, and code a new TextMorph on top of it? >> > > How I can try your code? > Do you have ready image to play with it? > > I am very interested with clean and simple alternative to morphic. I want > it for Presenty framework. > > (But I really like morphic as live user interface environment) > > Best regards, > Denis > > > > -- Philippe Back Dramatic Performance Improvements 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 Belgium

July 20, 2012

Re: [Pharo-project] Spec Enhancement Request

by Benjamin

I can do it quickly, but now I am working on something big for Spec which should be released soon and it takes all my time :) I will try to finish and release during the weekend and integrate the drag and drop at the beginning of next week :) Thank you for all your feedback and your interest for Spec :) Ebn On Jul 20, 2012, at 9:52 AM, Goubier Thierry wrote: > Le 18/07/2012 07:30, StÃ©phane Ducasse a Ã©crit : >> >> On Jul 17, 2012, at 9:46 AM, Goubier Thierry wrote: >> >>> Hi, >>> >>> could Spec gives access to drag and drop on morphs ? >> >> yes it should. >> A spec should capture all the description of the underlying widget. Many of the behavior/presentation are not captured right >> just because we wanted to make sure that the idea work and we took a breadth first approach. >> Because adding new meta-data is simple. > > Ok. Maybe an experiment could be to let Spec users extend on current Spec for a few cases of drag and drop, study the resulting code, and generalize an architecture for spec from that ? > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > >

July 20, 2012