March 2016 - Pharo-users - lists.pharo.org

Roassal2 on Ubuntu 64

by Evan Donahue

Hello, I'm trying to learn Roassal, but I can't seem to get the first visualization from https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/QuickStart/… working on any combination of image and vm. I've tried the vm+40 and vm+50 from get.pharo and the moose 6.0 image from the moose site. The issue seems to be that CairoLibrary>>unixModuleName does not contain the /usr/lib/x86_64-linux-gnu/libcairo.so.2 path where 64-bit Ubuntu installs cairo. If I symlink that library, I get an Error: External module not found from AthensCairoSurface. I don't really know enough about the external module system to know what this is telling me. Any ideas would be much appreciated. Thanks, Evan

March 10, 2016

Re: [Pharo-users] [ARTICLE] Tiny, yet so beautiful

by Sven Van Caekenberghe

Thanks a lot, Ben, for your remarks; I applied them all. I am glad you liked the article. Sven > On 10 Mar 2016, at 01:21, Ben Coman <btc(a)openinworld.com> wrote: > > On Thu, Mar 10, 2016 at 6:05 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> I wrote another article: >> >> Tiny, yet so beautiful >> The smallest piece of great Pharo code >> https://medium.com/concerning-pharo/tiny-yet-so-beautiful-1ef5149c910e >> > > I love reading these articles of yours. Very well written. > Feedback for some minor wordsmithing... > > - 2 out of 5 reserved words in the language.) > + 2 out of _the_ 5 reserved words in the language.) _They are > instances respectively of classes True and False, that have common > superclass Boolean._ > > - where an identical message _results in_ different implementations > + where an identical message _invokes_ different implementations > > - Manipulating objects using their API > + Manipulating objects using their _pre-existing_ API > > - Switserland > + Switzerland > > cheers -ben >

March 10, 2016

Re: [Pharo-users] GTSpotter fuzzy search

by Damien Pollet

+1 I wanted to copy the algo from selecta but never got to itâ¦ https://github.com/garybernhardt/selecta/blob/master/selecta On 9 March 2016 at 20:51, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Would you like to try to propose a implementation for this? This would fit > as a subclass of GTFilter? > > Cheers, > Doru > > > > On Mar 9, 2016, at 4:04 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > Would be possible to have fuzzy-search? > > Or rather Pascal-based search? > > > > RTAE -> RTAbstractExample > > BCF -> BlConfigurableFormatter > > > > etc. > > -- > www.tudorgirba.com > www.feenk.com > > "Every successful trip needs a suitable vehicle." > > > > > > >

March 10, 2016

Re: [Pharo-users] Call for action for Roassal

by Peter UhnÃ¡k

On Thu, Mar 10, 2016 at 12:36 AM, Martin BÃ¤hr <martin(a)realss.com> wrote: > hi, > > i just remembered two things: > > i'd like to see rounded corners on nodes. > We've added this quite some time ago, unless you have something else in mind. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |v e| v := RTView new. e := RTRoundedBox new size: 100; borderRadius: 20; borderColor: Color black; borderWidth: 1; element. v add: e. v ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ â > > Excerpts from stepharo's message of 2016-02-24 12:42:49 +0100: > > - having a better output (arrows, edge) > > and related to edges: > > i'd like edges to connect to a node on the border of the box, not to the > center > of the node. this means the connecting point would always be at the middle > of > the side of one edge: > We have about 10 different attach points already. See the 'attach point' protocol of RTAbstractLine. Some of them also automatically add extra space if there are multiple lines between the same elements. As for bezier and multiline edges, their curvature isn't currently handled properly, but it's in my todo list (I'll work on this probably during the weekend). I'm sure it can be presented in more revealing way, but it's too late for me today (or is it too early?). You can play with it (drag the elements to see how it behaves). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |v attachOptions es e offset| v := RTView new. attachOptions := RTAbstractLine selectors select: [ :each | each beginsWith: #with ]. offset := 0 @ 0. attachOptions do: [ :each | es := RTBox new borderColor: Color black; size: 50; elementsOn: #(a b). each = #withContinuousCircleAttachPoint ifTrue: [ es := RTEllipse new borderColor: Color black; size: 50; elementsOn: #(a b). ]. es translateBy: offset. es @ RTDraggable. offset := offset + (0 @ 100). v addAll: es. es second translateBy: 300 @ 25. e := RTArrowedLine new color: Color black; perform: each; edgeFrom: es first to: es second. e model: each. v add: e. e @ (RTLabelled new color: Color black). ]. v ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ â > > ___\|/___ > | | > \| |/ > --| |-- > /| |\ > |_________| > /|\ > > bezier edges should always leave at a 90deg angle: > ____|____ > | | > | | > --| |-- > | | > |_________| > | > > optionally, starting at the corners could also be nice: > > \_________/ > | | > | | > | | > | | > |_________| > / \ > > and in such a case bezier edges should leave at 135deg to each side. > > by default the edge should find the nearest connection point, but i'd like > to > configure a list of allowed points. > > finally, multiple edges in the same general direction should either leave > at > the same point, pick the nearest side that doesn't have an edge already. > or spaced evenly along the same side if all available sides have edges > already. > > the list of allowed connection points would have 12 options: > the middle of 4 sides, 4 corners, and 4 sides as a whole when multiple > edges > should be spaced evenly. > > greetings, martin. > > -- > eKita - the online platform for your entire academic > life > -- > chief engineer > eKita.co > pike programmer pike.lysator.liu.se caudium.net > societyserver.org > secretary > beijinglug.org > mentor > fossasia.org > foresight developer foresightlinux.org > realss.com > unix sysadmin > Martin BÃ¤hr working in china > http://societyserver.org/mbaehr/ > >

March 10, 2016

Re: [Pharo-users] [ARTICLE] Tiny, yet so beautiful

by Ben Coman

On Thu, Mar 10, 2016 at 6:05 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > I wrote another article: > > Tiny, yet so beautiful > The smallest piece of great Pharo code > https://medium.com/concerning-pharo/tiny-yet-so-beautiful-1ef5149c910e > I love reading these articles of yours. Very well written. Feedback for some minor wordsmithing... - 2 out of 5 reserved words in the language.) + 2 out of _the_ 5 reserved words in the language.) _They are instances respectively of classes True and False, that have common superclass Boolean._ - where an identical message _results in_ different implementations + where an identical message _invokes_ different implementations - Manipulating objects using their API + Manipulating objects using their _pre-existing_ API - Switserland + Switzerland cheers -ben

March 10, 2016

Re: [Pharo-users] Call for action for Roassal

by Martin BÃ¤hr

hi, i just remembered two things: i'd like to see rounded corners on nodes. Excerpts from stepharo's message of 2016-02-24 12:42:49 +0100: > - having a better output (arrows, edge) and related to edges: i'd like edges to connect to a node on the border of the box, not to the center of the node. this means the connecting point would always be at the middle of the side of one edge: ___\|/___ | | \| |/ --| |-- /| |\ |_________| /|\ bezier edges should always leave at a 90deg angle: ____|____ | | | | --| |-- | | |_________| | optionally, starting at the corners could also be nice: \_________/ | | | | | | | | |_________| / \ and in such a case bezier edges should leave at 135deg to each side. by default the edge should find the nearest connection point, but i'd like to configure a list of allowed points. finally, multiple edges in the same general direction should either leave at the same point, pick the nearest side that doesn't have an edge already. or spaced evenly along the same side if all available sides have edges already. the list of allowed connection points would have 12 options: the middle of 4 sides, 4 corners, and 4 sides as a whole when multiple edges should be spaced evenly. greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin BÃ¤hr working in china http://societyserver.org/mbaehr/

March 9, 2016

[VIDEO TUTORIAL] Automating Image Building

by Dimitris Chloupis

This one is a lengthy one but for a good reason, building images can be a tedious task but can be easily automated with the help of startup scripts and make files plus the mandatory dosage of Pharo technomagic. https://www.youtube.com/watch?v=rR4UmDoYAyQ&feature=youtu.be

March 9, 2016

[ARTICLE] Tiny, yet so beautiful

by Sven Van Caekenberghe

I wrote another article: Tiny, yet so beautiful The smallest piece of great Pharo code https://medium.com/concerning-pharo/tiny-yet-so-beautiful-1ef5149c910e Sven Please consider joining us @ http://pharodays2016.pharo.org

March 9, 2016

Re: [Pharo-users] [Moose-dev] Re: Re: Call for action for Roassal

by Peter UhnÃ¡k

On Wed, Mar 9, 2016 at 10:02 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > Heh, also a funny feature of your anchor constraints: they do not play > well with layouts and animations. Try the code below (adapted from the > example to use the layout and animation of LRP ) and you will see that the > circles keep spinning around, they never stop. I think it would be better > for them to stop ;-) > can't help myself :) https://youtu.be/PGNiXGX2nLU?t=1m > stepping := RTSpringLayoutStepping new > view: v; layout: layout; > afterBlock: [ v canvas camera focusOnCenter]. > The problem is that RTSpringLayoutStepping>>view sets in effect the layout on all elements in the view, which obviously won't work since they'll start competing. I'm not sure right now how to address it, but try this stepping := RTSpringLayoutStepping new view: RTView new; layout: layout; nodes: es; afterBlock: [ v canvas camera focusOnCenter]. > > I even have a bug report for you â¦ before, when I removed the edge, the > label was also removed automatically. Now this is no longer the case. :-( > > Ah right, thanks. I've extracted the class from my code and I have different removal mechanism... Please try the latest version, it should be fixed there. Peter

March 9, 2016

Re: [Pharo-users] NBOpenGL on Pharo5

by Alexandre Bergel

Yes we are. The binding uses native boost, the code has to be ported. Alexandre > Le 9 mars 2016 Ã 06:42, Richard Wettel <wettel(a)gmail.com> a Ã©crit : > > Hi > > I was wondering what the status of NBOpenGL on Pharo5 was. As far as I know, it does not work. I would like to have CodeCity work on Pharo5. > > Is anybody else (for instance the Roassal3d team) affected by this? > > Cheers > Ricky

March 9, 2016