- Pharo-users - lists.pharo.org

[FUN] Fibonacci spiral

by Hilaire

Hello, A step by step construction of the Fibonacci Spiral with Smalltalk code and DrGeo :) http://blog.drgeo.eu/post/2016/Fibonacci-spiral Hilaire -- Dr. Geo http://drgeo.eu

March 10, 2016

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

by Sven Van Caekenberghe

Here is my response to some of the comments on the article (published with the article itself): ====== @Bert Ah, my mistake. I did obviously check several implementations but the fact that the abstract method did not exist on Boolean itself misled me, weird. In any case, the two methods on True and False have indeed a 2004 timestamp, but the unit test has a 2009 timestamp, weird again. There is no further history to be found there. The method is also totally unused in your base image, unlike in Pharo. Cuis which forked in 2009 (after Pharo) does not have this method, also weird. Now, the article is not about digital archeology, but about a tiny piece of beautiful code. I rephrased some sentences to correct my mistake. @Tim No need for conspiracy theories, it was a mistake and was corrected. It is wonderful how certain people think they invented or are the keepers of all things Smalltalk while they got everything from Smalltalk-80 that came before them and while many other successful Smalltalk implementations existed and continue to exist. Pharo forked in 2008, that is a long time ago. Get over it. We are not looking backwards, we are looking forwards. ====== (more below) > On 10 Mar 2016, at 15:24, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > >> >> On 10 Mar 2016, at 3:01 , Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> "Nice article. But asBit has existed in @SqueakSmalltalk since at least 2004. Why not say so?" >> https://twitter.com/bertfreudenberg/status/707922868273856512 >> >> And indeed, in Pharo I see it added on 27.3. and 28.12.2012 (why almost a year difference?) >> >> And in Squeak I see it added 1.7.2004 (although they don't have it in Boolean class). >> >> The rest of the Boolean class looks pretty identical to the letter (including comments), so it makes one wonder why wasn't this copied over. >> >> Peter > > It was, the same version of asBit you find in Squeak was present in Pharo 1.4 and earlier. > Though, uncategorized, and without the subclassResponsibility implementation on Boolean. Apparently (I did not look that far back initially). > 2.0 development was hectic, hard to tell if it was cleaned away and then re-added/invented ( I think it may have, I seem to remember it being an extension in NB for awhile) > The source compaction that happened at 2.0 release removed any lingering traces of the old version, either way attributing Anthony Hannan as well wouldn't be entirely out of place. Yes, sometimes changes were quite heavy. The problem is also that the 'author' of a method's source code is not necessarily who wrote it; reformatting, commenting, changing the category are all ways to overwrite that tag. Even the first one in the chain could have gotten it from somewhere else, originally. If it was Anthony Hannan like you say, then well done Anthony ! > Either way, a beautiful bit of code! That was the point (and I now see that you used it in the Unicode project, so you knew it already !). > Cheers, > Henry Sven

March 10, 2016

Re: [Pharo-users] Analyzing Tweets

by stepharo

Hi arturo do you have more information about this? Stef Le 27/11/15 04:13, Arturo Zambrano a Ã©crit : > Looks nice, very similar to what Agustin presented in Smalltalks a few > days ago. We will post more info soon. > > > So there are at least 3 known projects working in Pharo + Roassal > Are the authors in this list? Great work! > It would be great to share the experience > > On Thu, Nov 26, 2015 at 5:12 PM, Offray Vladimir Luna CÃ¡rdenas > <offray(a)riseup.net <mailto:offray@riseup.net>> wrote: > > Never mind. I found it[1]. It was on the see more of the you tube > video (I advice to make it more visible on the page of the project): > > [1] https://github.com/ser515asu/AgileTweetViz-Technocrats > [2] https://sites.google.com/a/asu.edu/project-geeko/ > > Cheers, > > Offray > > > On 26/11/15 15:07, Offray Vladimir Luna CÃ¡rdenas wrote: > > Really nice and helpful... I don't see any public repo for the > tool on . There is any? > > Cheers, > > Offray > > On 26/11/15 13:44, Alexandre Bergel wrote: > > Hi! > > Some students from Arizona State University are analyzing > some tweets. This is pretty cool. Here are some short > video and url full of pictures: > > https://sites.google.com/a/asu.edu/project-geeko/ > https://drive.google.com/file/d/0BxQoWoSofKvaTkN5bk9hN0NyQ28/view > https://www.youtube.com/watch?v=cnuc_crnWB0&feature=youtu.be > > Impressive! > > Cheers, > Alexandre > > > > > > >

March 10, 2016

Re: [Pharo-users] [Pharo-dev] [Moose-dev] Re: RTAnchorConstraint

by Alexandre Bergel

Hi! Thanks Peter for having spotted the problem. I have fixed it somehow (âsomehowâ because this is not an ideal solution, but good enough for now). Try this after having updated Roassal: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | v lbls es e1 e2 a1 a2 layout stepping| v := RTView new. lbls := RTLabel new elementsOn: #(#First #Second). es := RTEllipse new size: 30; borderColor: Color black; elementsOn: #(#source #dest). v addAll: lbls; addAll: es. es @ RTDraggable. es @ RTLabeled. e1 := RTArrowedLine new withContinuousCircleAttachPoint; color: Color black; edgeFrom: es first to: es second. v add: e1. e2 := RTArrowedLine new withContinuousCircleAttachPoint; color: Color black; edgeFrom: es second to: es first. v add: e2. a1 := RTAnchorConstraint new. a1 anchorShape size: 10. a1 guideLine color: Color red. a1 element: lbls first; edge: e1; balance: 0.2; minDistance: 10; build. (a2 := RTAnchorConstraint new) element: lbls second; edge: e2; balance: 0.2; minDistance: 10; build. layout := RTForceBasedLayout new charge: -450; length: 100; doNotUseProgressBar; applyOn: es; yourself. layout initialLayout: RTSugiyamaLayout new. layout nodes: es. layout start: es. layout edges: { e1 . e2 }. stepping := RTSpringLayoutStepping new view: v; layoutWithoutPreparing: layout; afterBlock: [ v canvas camera focusOnCenter]. v addAnimation: stepping. ^ v -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Here is a screenshot: And this is all animated. Cool stuff! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Mar 10, 2016, at 12:42 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > To which problem? > > The problem is that RTSpringLayoutStepping always uses all the elements in the view and ignores what you set to the layout. > > This is a problem, because it will try to also layout the anchor, but that will trigger the anchor to fix itselfâ¦ and we get endless spinning. > > On Thu, Mar 10, 2016 at 4:21 PM, Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: > >> On Mar 10, 2016, at 12:08, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >>> >>> There is no other solution? Alex, do you have any idea? >> >> To which problem? > > Copy-paste from original mail: > > 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 ;-) > > | v lbls es e1 e2 a1 a2 layout stepping| > v := RTView new. > lbls := RTLabel new elementsOn: #(#First #Second). > es := RTEllipse new > size: 30; > borderColor: Color black; > elementsOn: #(#source #dest). > v > addAll: lbls; > addAll: es. > es @ RTDraggable. > es @ RTLabeled. > e1 := RTArrowedLine new > withContinuousCircleAttachPoint; > color: Color black; > edgeFrom: es first to: es second. > v add: e1. > e2 := RTArrowedLine new > withContinuousCircleAttachPoint; > color: Color black; > edgeFrom: es second to: es first. > v add: e2. > a1 := RTAnchorConstraint new. > a1 anchorShape size: 10. > a1 guideLine color: Color red. > a1 > element: lbls first; > edge: e1; > balance: 0.2; > minDistance: 10; > build. > (a2 := RTAnchorConstraint new) > element: lbls second; > edge: e2; > balance: 0.2; > minDistance: 10; > build. > layout := RTForceBasedLayout new > charge: -450; length: 100; > doNotUseProgressBar; applyOn: es; yourself. > layout initialLayout: RTSugiyamaLayout new. > stepping := RTSpringLayoutStepping new > view: v; layout: layout; > afterBlock: [ v canvas camera focusOnCenter]. > v addAnimation: stepping. > ^ v > > > ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- > > Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> > https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev> > >

March 10, 2016

Re: [Pharo-users] Roassal2 on Ubuntu 64

by Sven Van Caekenberghe

> On 10 Mar 2016, at 17:08, Evan Donahue <emdonahu(a)gmail.com> wrote: > > D'oh. Yep, this did it. I think I've been bitten by 32 bits before both on > sound and on file opening. One day I'll learn, and on that day, Pharo will > be 64 bit. ;-) > Thanks, > Evan > > > > -- > View this message in context: http://forum.world.st/Roassal2-on-Ubuntu-64-tp4883675p4883840.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

March 10, 2016

Re: [Pharo-users] Fwd: Fwd: Phratch + Debian

by Hilaire

We should help to promote Phratch at the Education Nationale/FR because there is now the need for graphic programming tools. Right now Scratch2.0 is what most recommend but there is problem to use it on some situation. Moreover when custom features are needed, it is far more easier to get it done with Phratch. Hilaire Le 09/03/2016 22:03, stepharo a Ã©crit : > Cool initiative! > Tx Jannik > I blogged it and twitted it :) -- Dr. Geo http://drgeo.eu

March 10, 2016

Re: [Pharo-users] Roassal2 on Ubuntu 64

by Peter UhnÃ¡k

> Ok. Just to check. Are you advocating that leaving out cairo as a dependency of the main pharo app for new pharo users is a 'feature'? Until Bloc it is a feature, but if it is installed via package manager then it should imho also install cairo because that's not that hard there. The problem is the VM downloaded via zeroconf. Sorry I don't explain myself properly. I was meaning a window with this > message instead of a error trace, which could be intimidating. Something > with the same message and buttons like "Ok", "Launch debugger". In the > workshops there are some Gnu/Linux newbies and the hidding the error trace > for a while seems to be helpful to them. This should be relatively simple to do: 1) create new "PreDebugger" that's user-friendly (currently we have (GT)SpecPreDebugWindow that is started from (GT)SpecDebugger>>openWithNotification:) 2) let Debuggers ask for PreDebugWindow class through Smalltalk tools 3) install your UserFirendlyPreDubugWindow to Smalltalk tools I think this would be a very useful addition for many people. (I wanted to make this some time ago but haven't got around to do it yet.) No, but because we could build a wrapper for particular packages that > installs Nix, and then others (32 bits variants of libcairo or sqlite, > pandoc, etc) without caring about a particular Unix variant (being them Mac > or hundreds Gnu/Linux distros based on dozen of "bases"), making the > experience smother for the newbie, providing he/she has root privileges. > People will not see nix anywhere, not even for installing Mac is self-contained, so the main issue is linux. If the user has a root privilege, then maybe we should push for pharo directly in the package manager repository? And sure, there are hundreds of distros, but you will cover majority of the market withâ¦ maybe 5 distros? People that can't handle obscure distros don't install them. But to get some motion: 1) let's compile a list of majority distros 2) let's see how hard it is to build packages for them (imho this could be automated via CI), and we already have ubuntu package (or maybe nix can be pushed to all distros?) 3) maybe consider all-in-one bundle for non-root targets (this would work for cairo, but not for 64b systems in general, because the dependency list there is monstrous) So no need to be sarcastic here Peter. Sorry, I got carried away. I've got my fair share of dependency hell and introducing another package manager always makes me shiver. On Thu, Mar 10, 2016 at 4:40 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 10-03-16 15:28, Thierry Goubier wrote: > >> Recommande: pharo-vm-core:i386 >> >> pharo-vm-core suggest pharo-vm-desktop, and pharo-vm-desktop only >> recommand libcairo2 ? >> So, maybe we need to change the dependencies then ? >> > Yes, that sounds wrong. I would assume it to be: > Pharo launcher is a desktop application, > and the desktop needs Cairo. Core should be headless. > > Stephan > > >

March 10, 2016

Re: [Pharo-users] Roassal2 on Ubuntu 64

by Evan Donahue

D'oh. Yep, this did it. I think I've been bitten by 32 bits before both on sound and on file opening. One day I'll learn, and on that day, Pharo will be 64 bit. Thanks, Evan -- View this message in context: http://forum.world.st/Roassal2-on-Ubuntu-64-tp4883675p4883840.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 10, 2016

Re: [Pharo-users] [Moose-dev] Re: [Pharo-dev] RTAnchorConstraint

by Peter UhnÃ¡k

> To which problem? The problem is that RTSpringLayoutStepping always uses all the elements in the view and ignores what you set to the layout. This is a problem, because it will try to also layout the anchor, but that will trigger the anchor to fix itselfâ¦ and we get endless spinning. On Thu, Mar 10, 2016 at 4:21 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > On Mar 10, 2016, at 12:08, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > > There is no other solution? Alex, do you have any idea? > > > To which problem? > > > Copy-paste from original mail: > > 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 ;-) > > | v lbls es e1 e2 a1 a2 layout stepping| > v := RTView new. > lbls := RTLabel new elementsOn: #(#First #Second). > es := RTEllipse new > size: 30; > borderColor: Color black; > elementsOn: #(#source #dest). > v > addAll: lbls; > addAll: es. > es @ RTDraggable. > es @ RTLabeled. > e1 := RTArrowedLine new > withContinuousCircleAttachPoint; > color: Color black; > edgeFrom: es first to: es second. > v add: e1. > e2 := RTArrowedLine new > withContinuousCircleAttachPoint; > color: Color black; > edgeFrom: es second to: es first. > v add: e2. > a1 := RTAnchorConstraint new. > a1 anchorShape size: 10. > a1 guideLine color: Color red. > a1 > element: lbls first; > edge: e1; > balance: 0.2; > minDistance: 10; > build. > (a2 := RTAnchorConstraint new) > element: lbls second; > edge: e2; > balance: 0.2; > minDistance: 10; > build. > layout := RTForceBasedLayout new > charge: -450; length: 100; > doNotUseProgressBar; applyOn: es; yourself. > layout initialLayout: RTSugiyamaLayout new. > stepping := RTSpringLayoutStepping new > view: v; layout: layout; > afterBlock: [ v canvas camera focusOnCenter]. > v addAnimation: stepping. > ^ v > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University > of Chile > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > >

March 10, 2016

Re: [Pharo-users] Roassal2 on Ubuntu 64

by Stephan Eggermont

On 10-03-16 15:28, Thierry Goubier wrote: > Recommande: pharo-vm-core:i386 > > pharo-vm-core suggest pharo-vm-desktop, and pharo-vm-desktop only > recommand libcairo2 ? > So, maybe we need to change the dependencies then ? Yes, that sounds wrong. I would assume it to be: Pharo launcher is a desktop application, and the desktop needs Cairo. Core should be headless. Stephan

March 10, 2016