- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Moose-dev] Roassal new algorithms

by Frank Shearar

Sure, and I had to discover that for myself, since the d3 example was titled "flare imports". I only found out about the name "hierarchical bundled edges" thanks to Alexandre's original post! frank On 20 April 2013 07:23, Tudor Girba <tudor(a)tudorgirba.com> wrote: > This visualization is precisely made for hierarchical graphs. That is why the edges are called "hierarchical bundled edges". So, yes, you need a hierarchical graph. > > Cheers, > Doru > > > On Apr 19, 2013, at 8:57 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> This is a very cool visualization. There is no reason why we cannot do it in Pharo >> >> Alexandre >> >> >> On Apr 19, 2013, at 10:49 AM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >> >>> I've played with these before [1]. They work best with hierarchical names. In other words, in a flat namespace (say, showing class dependencies with just the class name) you end up with a very messy diagram. >>> >>> Let's assume you use "." as the name token separator. If you prefixed the names with their packages, say Tools-Debugger.Debugger, you'd get a better graph, where the bundles would be tighter. If you made things more hierarchical still, say with names like Tools.Debugger.Debugger, things would look even better. >>> >>> The deeper the naming hierarchy the fewer fat bundles you get in the image. >>> >>> frank >>> >>> [1] http://mbostock.github.io/d3/talk/20111116/bundle.html >>> >>> On 19 April 2013 16:37, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> Let's have this discussion in the Pharo list. >>> >>> Alexandre >>> >>> Begin forwarded message: >>> >>>> From: Alexandre Bergel <alexandre.bergel(a)me.com> >>>> Subject: [Moose-dev] Re: Roassal new algorithms >>>> Date: April 19, 2013 11:25:31 AM GMT-04:00 >>>> To: Moose-related development <moose-dev(a)iam.unibe.ch> >>>> Reply-To: Moose-related development <moose-dev(a)iam.unibe.ch> >>>> >>>>> There are more than simply linear, quadratic and cubic Bezier curves. In fact, as you can have as many control points as you wish, you can have a Bezier curve of any order. >>>> >>>> Ok >>>> >>>>> But what I was calling RadialBezierCurve was a kind of strategy, I mean I have an abstract class which knows how to compute a curve, but I still have to choose my control points so I was thinking to create different subclasses whose role is to know what are their control points : >>>>> >>>>> - The radial one choose its control points within the same radius as its source and its target. >>>> >>>> Ah ok >>>> >>>>> I wanted to create an ortoVertical and an ortoHorizontal whose control points would have been computed differently, so that we could use Bezier curve for regular tree too. >>>> >>>> It would be cool to have hierarchical bundles edges in Roassal. >>>> A screenshot of what it looks like: >>>> <Screen Shot 2013-04-19 at 11.24.59 AM.png> >>>> >>>> The technical description: http://www.win.tue.nl/~dholten/papers/bundles_infovis.pdf >>>> >>>> Alexandre >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)iam.unibe.ch >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > -- > www.tudorgirba.com > > "What is more important: To be happy, or to make happy?" > >

April 20, 2013

Re: [Pharo-project] Version 1.39 of Versionner

by stephane ducasse

On Apr 19, 2013, at 5:25 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >>> Works now - thanks. I've put a copy of the config into ss3/MetaRepoForPharo20 >>> so one can easily load via Configuration browser from within the 2.0 image. >> >> Excellent! >> Something that would be amazing, is to have a small text panel that appears when you select a configuration, with a short description (or at least some keywords) of what the software about to install is all about. >> >> For example, there are only a few projects that I can imagine what they are about. For example, no idea what VistaCursors, VoyageMongo, ScriptManager are about. I know I can easily find the info on the different forges. But my point is that the visibility of these projects is really small. >> >> Maybe we can use as a convention a method #readme on each ConfigurationOf ? >> >> Alexandre > > I completely agree that more work is needed. I started a new config browser for 3.0 (based on Spec) as a changeset > - currently I cant find the issue on this horrible new issue tracker ;) :) Yes me too :) > > Yes - the config itself would be a good place. > > One problem: if you want to have a slick UI (fast moving in the list) you would have to load all the > configs into the image. Or one needs an updating server job that collects all #readmes > and provides a txt/xml file for the config browser client Yes :) Probably the job that will validate the projects that are accepted in a distribution should build this cache. In fact we want to have a job that loads the ConfigurationOf and parse their Pier description and generate a catalog on the web. Right now I'm continuing to write chapters for a future book in pier https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ but this will be with the same techno Like that we will not have to maintain the catalog in the collaborative book. Stef > Bye > T. > > >

April 20, 2013

Re: [Pharo-project] Version 1.39 of Versionner

by stephane ducasse

We should add more information in the configurationOf Stef >>> No idea why happened. >>> I copied the a missing file in the repository >>> Try again, it should work now >>> >>> Alexandre >> >> Works now - thanks. I've put a copy of the config into ss3/MetaRepoForPharo20 >> so one can easily load via Configuration browser from within the 2.0 image. > > Excellent! > Something that would be amazing, is to have a small text panel that appears when you select a configuration, with a short description (or at least some keywords) of what the software about to install is all about. > > For example, there are only a few projects that I can imagine what they are about. For example, no idea what VistaCursors, VoyageMongo, ScriptManager are about. I know I can easily find the info on the different forges. But my point is that the visibility of these projects is really small. > > Maybe we can use as a convention a method #readme on each ConfigurationOf ? > > Alexandre > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

April 20, 2013

Re: [Pharo-project] Any wishes for Roassal?

by stephane ducasse

We want speed up and less garbage generation (ie do not use collect when do will make it or some stuff like that). May be people here could have a look at it and do a fast code review? Stef > Hi! > > Roassal 2.0 is on the way. We would like to make sure everybody find this release attractive. > We are wondering whether you have some particular requirements you would like us to address or some bugs you would like to see fixed. > > Feel free to speak up! > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

April 20, 2013

Re: [Pharo-project] [Moose-dev] Roassal new algorithms

by stephane ducasse

On Apr 20, 2013, at 8:23 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > This visualization is precisely made for hierarchical graphs. That is why the edges are called "hierarchical bundled edges". So, yes, you need a hierarchical graph. +1 :) > > Cheers, > Doru > > > On Apr 19, 2013, at 8:57 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> This is a very cool visualization. There is no reason why we cannot do it in Pharo >> >> Alexandre >> >> >> On Apr 19, 2013, at 10:49 AM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >> >>> I've played with these before [1]. They work best with hierarchical names. In other words, in a flat namespace (say, showing class dependencies with just the class name) you end up with a very messy diagram. >>> >>> Let's assume you use "." as the name token separator. If you prefixed the names with their packages, say Tools-Debugger.Debugger, you'd get a better graph, where the bundles would be tighter. If you made things more hierarchical still, say with names like Tools.Debugger.Debugger, things would look even better. >>> >>> The deeper the naming hierarchy the fewer fat bundles you get in the image. >>> >>> frank >>> >>> [1] http://mbostock.github.io/d3/talk/20111116/bundle.html >>> >>> On 19 April 2013 16:37, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> Let's have this discussion in the Pharo list. >>> >>> Alexandre >>> >>> Begin forwarded message: >>> >>>> From: Alexandre Bergel <alexandre.bergel(a)me.com> >>>> Subject: [Moose-dev] Re: Roassal new algorithms >>>> Date: April 19, 2013 11:25:31 AM GMT-04:00 >>>> To: Moose-related development <moose-dev(a)iam.unibe.ch> >>>> Reply-To: Moose-related development <moose-dev(a)iam.unibe.ch> >>>> >>>>> There are more than simply linear, quadratic and cubic Bezier curves. In fact, as you can have as many control points as you wish, you can have a Bezier curve of any order. >>>> >>>> Ok >>>> >>>>> But what I was calling RadialBezierCurve was a kind of strategy, I mean I have an abstract class which knows how to compute a curve, but I still have to choose my control points so I was thinking to create different subclasses whose role is to know what are their control points : >>>>> >>>>> - The radial one choose its control points within the same radius as its source and its target. >>>> >>>> Ah ok >>>> >>>>> I wanted to create an ortoVertical and an ortoHorizontal whose control points would have been computed differently, so that we could use Bezier curve for regular tree too. >>>> >>>> It would be cool to have hierarchical bundles edges in Roassal. >>>> A screenshot of what it looks like: >>>> <Screen Shot 2013-04-19 at 11.24.59 AM.png> >>>> >>>> The technical description: http://www.win.tue.nl/~dholten/papers/bundles_infovis.pdf >>>> >>>> Alexandre >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)iam.unibe.ch >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > -- > www.tudorgirba.com > > "What is more important: To be happy, or to make happy?" > >

April 20, 2013

Re: [Pharo-project] plugin in Nautilus

by stephane ducasse

I use a group for that :) And what I would love is a group: latest loaded packages. On Apr 20, 2013, at 12:24 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Is there a documentation on how to create a plugin for Nautilus? > > I would like to create a command 'Hide all packages' in the Package column of Nautilus. Any hint on how to do this? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

April 20, 2013

Re: [Pharo-project] [Moose-dev] Roassal new algorithms

by Tudor Girba

This visualization is precisely made for hierarchical graphs. That is why the edges are called "hierarchical bundled edges". So, yes, you need a hierarchical graph. Cheers, Doru On Apr 19, 2013, at 8:57 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > This is a very cool visualization. There is no reason why we cannot do it in Pharo > > Alexandre > > > On Apr 19, 2013, at 10:49 AM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > >> I've played with these before [1]. They work best with hierarchical names. In other words, in a flat namespace (say, showing class dependencies with just the class name) you end up with a very messy diagram. >> >> Let's assume you use "." as the name token separator. If you prefixed the names with their packages, say Tools-Debugger.Debugger, you'd get a better graph, where the bundles would be tighter. If you made things more hierarchical still, say with names like Tools.Debugger.Debugger, things would look even better. >> >> The deeper the naming hierarchy the fewer fat bundles you get in the image. >> >> frank >> >> [1] http://mbostock.github.io/d3/talk/20111116/bundle.html >> >> On 19 April 2013 16:37, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Let's have this discussion in the Pharo list. >> >> Alexandre >> >> Begin forwarded message: >> >>> From: Alexandre Bergel <alexandre.bergel(a)me.com> >>> Subject: [Moose-dev] Re: Roassal new algorithms >>> Date: April 19, 2013 11:25:31 AM GMT-04:00 >>> To: Moose-related development <moose-dev(a)iam.unibe.ch> >>> Reply-To: Moose-related development <moose-dev(a)iam.unibe.ch> >>> >>>> There are more than simply linear, quadratic and cubic Bezier curves. In fact, as you can have as many control points as you wish, you can have a Bezier curve of any order. >>> >>> Ok >>> >>>> But what I was calling RadialBezierCurve was a kind of strategy, I mean I have an abstract class which knows how to compute a curve, but I still have to choose my control points so I was thinking to create different subclasses whose role is to know what are their control points : >>>> >>>> - The radial one choose its control points within the same radius as its source and its target. >>> >>> Ah ok >>> >>>> I wanted to create an ortoVertical and an ortoHorizontal whose control points would have been computed differently, so that we could use Bezier curve for regular tree too. >>> >>> It would be cool to have hierarchical bundles edges in Roassal. >>> A screenshot of what it looks like: >>> <Screen Shot 2013-04-19 at 11.24.59 AM.png> >>> >>> The technical description: http://www.win.tue.nl/~dholten/papers/bundles_infovis.pdf >>> >>> Alexandre >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

April 20, 2013

Re: [Pharo-project] Any wishes for Roassal?

by Paul DeBruicker

I haven't looked in a while, this is probably possible, and a Fuel visualizer thing rather than a Roassal thing but: Is there a way to hide all the edges pointing to a node unless the node is clicked, or has more fewer than X edges pointing to it, or ......? I'm using Chronos for some things and each Timepoint has a Calendar that it references, but its the same Calendar so every Timepoint draws a line to the Calendar, which can both slow down the drawing incredibly but also mask useful information behind lines. Thanks for sharing Roassal abergel wrote > Hi! > > Roassal 2.0 is on the way. We would like to make sure everybody find this > release attractive. > We are wondering whether you have some particular requirements you would > like us to address or some bugs you would like to see fixed. > > Feel free to speak up! > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. -- View this message in context: http://forum.world.st/Any-wishes-for-Roassal-tp4682621p4682683.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 20, 2013

Re: [Pharo-project] Any wishes for Roassal?

by Serge Stinckwich

I don't know if you add this feature recently but I would like to be able to attach edges to center of nodes. Thank you for your great work! EnvoyÃ© de mon iPhone Le 20 avr. 2013 Ã 01:58, Alexandre Bergel <alexandre.bergel(a)me.com> a Ã©crit : > Hi! > > Roassal 2.0 is on the way. We would like to make sure everybody find this release attractive. > We are wondering whether you have some particular requirements you would like us to address or some bugs you would like to see fixed. > > Feel free to speak up! > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

April 20, 2013

Re: [Pharo-project] [Athens] A new wave of impressionism

by Alexandre Bergel

Excellent! Alexandre On Apr 18, 2013, at 4:58 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Not really impressive (that's why it called new wave) > > Here is results of 2 days of preparing/implementing and polishing a > quadric bezier curve approximation > algorithm by series of lines. > > The red pill.. err fill is polygon consisting purely from lines, > the white outline is same quadric bezier, but drawn directly by cairo > with stroke width = 5. > > Cubic bezier , then elliptical arc and then generic parametric > functions ahead! :) > > There is two reasons why i implementing highly inefficient (because of > boxed floats) > path flattener: > - some path segments are not supported by cairo, therefore i am > forced to approximate it with something else (and something else is > lines ;) > - having path geometry turned into silly polygon, there is very easy > algorithm to tell if given point inside or outside of polygon > > so, potentially, this will give use following: > - being able to use any kind of curves as path segments (well, it > could be a bit slow, but it is up to you, right?) e.g. something like: > builder > lineTo: 50@50; > parametricCurve: [:t | t sin * t squared ] tMin: 0 tMax: 10 to: 20@30 > > - being able to detect whether mouse hovers over shape or not :) > > > -- > Best regards, > Igor Stasenko. > <Screen Shot 2013-04-18 at 10.43.07 PM.png> -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 20, 2013