March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Geometric model in Pharo

by stephane ducasse

On Mar 11, 2013, at 4:30 PM, Tristan Bourgois <tristan.bourgois(a)gmail.com> wrote: > Hi! > > I'm actually doing my final-year internship in ThalÃ¨s and I'm porting > an application, for creating UI, from VisualWorks to Pharo (Using > Athens :). The problem is they use a geometric model already > implemented in VisualWorks (Graphics-Geometry package). > The features which are very important to have is the possibility to > convert a figure (like a Circle) to a Polyline representation. (They > use it, for example, to know if the mouse are on a shape) > > That there is something in Pharo that I could use? > look at the PolygonMorph and subclasses. This class implements a morph which can behave as four different objects depending on the the following two facts: - is it OPEN or CLOSED? - is it SEGMENTED or SMOOTHED. 1. The OPEN and SEGMENTED variant looks like polyline. 2. The OPEN and SMOOTHED variant looks like spline (kind of curve) 3. The CLOSED and SEGMENTED variant looks like polygon. This is actually what you get when you do PolygonMorph new openInWorld You get a triangle. See below how to manipulate these objects... 4. The CLOSED and SMOOTHED variant looks like blob (???) Prototypes of this morph can also be found in "Object Catalog". Several (different variants) of this object are among "Basic" morphs. Explore the assiciated morph-menu. It enables you - to toggle showing of "handles". They make it possible to - reposition already existing vertices (by moving yellow handles) - create new vertices (by moving green handles) - delete already existing vertices (by dragging and dropping one yellow handle closely nearby the adjacent yellow handle Handles can be made visible/hidden by shift+leftclicking the morph. This way it is possible to quickly show handles, adjust vertices and then again hide handles. - making closed polygon open, i.e. converting it to a curve (and vice versa) - toggle smoothed/segmented line/outline - set up custom dashing (for line, curves or borders of closed polygons - set up custom arrow-heads (for lines resp. curves) ------------------------------------------------------------------------------------------ Implementation notes: This class combines the old Polygon and Curve classes. The 1-bit fillForm to make display and containment tests reasonably fast. However, this functionality is in the process of being supplanted by balloon capabilities, which should eventually provide anti-aliasing as well. wiz 7/18/2004 21:26 s have made some changes to this class to 1) correct some bugs associated with one vertex polygons. 2) prepare for some enhancements with new curves.

March 11, 2013

Re: [Pharo-project] Help with MenuMorph

by stephane ducasse

On Mar 11, 2013, at 2:10 PM, jannik laval <jannik.laval(a)gmail.com> wrote: > Hi Stef, > > I am searching to do that too. > For now, I am using something else... And I plan to create new Menu more usable. > > Here is what I use, for your case, just adapt it when trying: > > === > | aMenu sz on | > on := soundInput isRecording. > self stop. > aMenu := MenuMorph new title: ('FFT size (currently {1})' translated format:{fft n}). > ((7 to: 10) collect: [:n | 2 raisedTo: n]) do: [:r | > aMenu add: r printString > target: FFT > selector: #new > argument: r > ]. > > aMenu popUpInWorld. > > self resetDisplay. > on ifTrue: [self start]. > === the problem is that we are missing a way to have menu that simply return a value (without resorting to a method execution and selector). Stef > > Jannik > > > 2013/3/11 stephane ducasse <stephane.ducasse(a)free.fr> > In fact I see that the problem is more into > > how can I specify a menu item which returns a value that I specify without passing a symbol > > ((7 to: 10) collect: [:n | 2 raisedTo: n]) do: [:r | aMenu add: r printString action: r]. > > > On Mar 11, 2013, at 1:28 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > > > HI guys > > > > I'm trying to fix all the sound interface for 2.0 and I got trapped into MenuMorph. How do I schedule a menu and get its selected value? > > I have to convert code like the following one. > > > > > > > > | aMenu sz on | > > aMenu := MenuMorph new title: ('FFT size (currently {1})' translated format:{fft n}). > > ((7 to: 10) collect: [:n | 2 raisedTo: n]) do: [:r | aMenu add: r printString action: r]. > > > > sz := aMenu popUpInWorld. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > how can I get the selected value? > > > > > > sz ifNil: [^ self]. > > on := soundInput isRecording. > > self stop. > > fft := FFT new: sz. > > self resetDisplay. > > on ifTrue: [self start]. > > > > > > > > > > -- > ~~Dr. Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu >

March 11, 2013

[Pharo-project] Fwd: Code review tools?

by stephane ducasse

> >> Do you know when monticello was invented? >> and working for real? > > Around 2004-2005 as far as I remember. And working for real at that > very moment, I guess. > > Why? because pay attention when you talk about smalltalker reinventing the wheel. So far with this argument we could say that we should all use eclipse because Java invented the ide, isn't. So if you want Pharo to make progress, contribute. Simple easy and with measurable impact. Stef > > Regards! > > > Esteban. >

March 11, 2013

Re: [Pharo-project] Code review tools?

by stephane ducasse

Sorry I do not have the time to discuss. Busy writing report. Our goal is to make sure that people can use Pharo to build real application. Of course we would love to be as big as ruby and have 1000 of contributors. So far this is not the case so â¦ Still by focusing on key assets we are making progress. Stef >> >>>> Every time I see smalltalkers forking away from established mainstream >>>> solutions/practices I hear a big noise inside my head. On the >>>> opposite, whenever I see stuff like the CI integrations, FileTree, >>>> standards compliance, and so on, I'm really happy. >> >>> Do you know when monticello was invented? >>> and working for real? >> >> Around 2004-2005 as far as I remember. And working for real at that >> very moment, I guess. >> >> Why? > > Presumably because it predates git :) But I think 2003 is the actual birth year. > > But the counter argument is trivial: how many people use Monticello? > (At most, hundreds. In comparison to at least 10s of thousands using > git.) Does Monticello actually use any of the special syntax-awareness > it's supposed to bring to the table? (No.) > > But the counter-counter argument is "it's good enough". (I disagree, > but I accept the argument that it does work well enough to actually > get stuff done, even if code review in Smalltalk is currently way > harder than in Ruby or Clojure, the other languages in which I most > commonly program. And they're so easy to code review because being > git-friendly allows me to see diffs and discuss diffs and use all > manner of cool tools that hook into git.) > > frank > >> Regards! >> >> >> Esteban. >> >

March 11, 2013

Re: [Pharo-project] Code review tools?

by Frank Shearar

On 11 March 2013 16:28, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2013/3/11 stephane ducasse <stephane.ducasse(a)free.fr>: > >>> Every time I see smalltalkers forking away from established mainstream >>> solutions/practices I hear a big noise inside my head. On the >>> opposite, whenever I see stuff like the CI integrations, FileTree, >>> standards compliance, and so on, I'm really happy. > >> Do you know when monticello was invented? >> and working for real? > > Around 2004-2005 as far as I remember. And working for real at that > very moment, I guess. > > Why? Presumably because it predates git :) But I think 2003 is the actual birth year. But the counter argument is trivial: how many people use Monticello? (At most, hundreds. In comparison to at least 10s of thousands using git.) Does Monticello actually use any of the special syntax-awareness it's supposed to bring to the table? (No.) But the counter-counter argument is "it's good enough". (I disagree, but I accept the argument that it does work well enough to actually get stuff done, even if code review in Smalltalk is currently way harder than in Ruby or Clojure, the other languages in which I most commonly program. And they're so easy to code review because being git-friendly allows me to see diffs and discuss diffs and use all manner of cool tools that hook into git.) frank > Regards! > > > Esteban. >

March 11, 2013

Re: [Pharo-project] Code review tools?

by Esteban A. Maringolo

2013/3/11 stephane ducasse <stephane.ducasse(a)free.fr>: >> Every time I see smalltalkers forking away from established mainstream >> solutions/practices I hear a big noise inside my head. On the >> opposite, whenever I see stuff like the CI integrations, FileTree, >> standards compliance, and so on, I'm really happy. > Do you know when monticello was invented? > and working for real? Around 2004-2005 as far as I remember. And working for real at that very moment, I guess. Why? Regards! Esteban.

March 11, 2013

Re: [Pharo-project] Porting SmaCC from 1.4 to 2.0; doSilently: equivalent ?

by Goubier Thierry

Le 11/03/2013 11:09, stephane ducasse a Ã©crit : >> >> I can. >> >> I'll try to make sure I test it with a larger set of tests next, but, so far, the only change I had to do was that doSilently: thing. >> >> Now, would anyone has a nice configuration showing how to customize for Pharo 2.0/Pharo 1.4 ? > > > The idea is that you have your baseline and version > then you add symbolic version > > stable: spec > <symbolicVersion: #'stable'> > > spec for: #'common' version: '1.1'. > spec for: #'pharo1.4.x' version: '1.4' > spec for: #'pharo2.0.x' version: '1.8' > > Have a look at the metacello chapter Done, but then I had a segfault (#becomeForward:)... well in fact two, trying to load SmaCCDev and OSProcess. Will try to recover my changes soon. Kind of hard at the moment to use Pharo 2.0, with the segfaults. 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

March 11, 2013

Re: [Pharo-project] Code review tools?

by stephane ducasse

>>> >>> >> i am very happy that github exists.. and its features available only if you >> put code there.. >> but if code is not on github, then what you will do? > > To rephrase the question: what do we still need to do before we can > integrate (something like) github into a standard Smalltalk workflow? how many man month engineer time do you have free for that? Personally I prefer that FFI VM vector graphics â¦ get pushed. So git integration will come but on people free time. Stef

March 11, 2013

Re: [Pharo-project] Code review tools?

by stephane ducasse

On Mar 11, 2013, at 4:05 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2013/3/11 Frank Shearar <frank.shearar(a)gmail.com> >> >> On 11 March 2013 13:34, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> i am very happy that github exists.. and its features available only if you >>> put code there.. >>> but if code is not on github, then what you will do? >> >> To rephrase the question: what do we still need to do before we can >> integrate (something like) github into a standard Smalltalk workflow? > > I totally agree on that. But Github is great if your project is open > source or you're willing to pay for private repos. > On the other hand, BitBucket.org has free private repositories. But it > doesn't have code review. > > In my case it is not a required feature, and I'd go for the already > implemented Github alternative. > > Every time I see smalltalkers forking away from established mainstream > solutions/practices I hear a big noise inside my head. On the > opposite, whenever I see stuff like the CI integrations, FileTree, > standards compliance, and so on, I'm really happy. Do you know when monticello was invented? and working for real? Stef

March 11, 2013

[Pharo-project] Geometric model in Pharo

by Tristan Bourgois

Hi! I'm actually doing my final-year internship in ThalÃ¨s and I'm porting an application, for creating UI, from VisualWorks to Pharo (Using Athens :). The problem is they use a geometric model already implemented in VisualWorks (Graphics-Geometry package). The features which are very important to have is the possibility to convert a figure (like a Circle) to a Polyline representation. (They use it, for example, to know if the mouse are on a shape) That there is something in Pharo that I could use? Thanks! Tristan.

March 11, 2013