8 Mar
2016
8 Mar
'16
1:52 p.m.
Excellent, thanks a lot! I will take a look at that tomorrow.
On Mar 7, 2016, at 11:34, Peter Uhnák
<i.uhnak(a)gmail.com> wrote:
Hi Johan,
I've just commited RTAnchorConstraint to latest Roassal, see class-side example
there.
I've been using it for my class diagrams where it works quite well, however class
diagrams are usually orthogonal-ish, which makes it a bit nicer.
<uml.png>
The Anchor will avoid intersecting it's own line, and one of the end shapes (it
should both but apparently I have a bug there...).
It doesn't look at other lines, however you can specify on which side it should be.
(You can also put the node label inside the circle with `el @ (RTLabelled new center)`
but you probably know that.)
<anchor.png>
I have also a global edge labeling layout which produces good placement… but it's
slow as hell… I need to write a fast flow alogrithm…
Also the Anchor currently doesn't work with self-edges. On the other hand Roassal
doesn't have self-edges yet so it shouldn't be a problem. :)
Peter
On Mon, Mar 7, 2016 at 2:34 PM, Johan Fabry <jfabry(a)dcc.uchile.cl
<mailto:jfabry@dcc.uchile.cl>> wrote:
Better late than never :-) (working on the holidays backlog)
I only have one request: better positioning on labels of nodes and edges. For example see
the image: three of the four labels are badly positioned because the bounding box of their
text is intersected by one or more edges.
<Screen Shot 2016-03-07 at 10.31.24.png>
I know that to solve this generally is hard, but for simple cases like this it should be
possible.
Ah, and it should work well with animations and dragging of course ;-)
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile
On Feb 24, 2016, at 05:51, Alexandre Bergel
<alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote:
Dear community,
As you may have seen, Roassal has entered a stabilization phase. The book
AgileVisualization.com <http://agilevisualization.com/> will soon be released. After
its release, Roassal will go over a new development phase. In order to prepare it, I am
asking this question:
What are the 3 aspects you would like to see improved in Roassal?
You can answer publicly or by sending private messages.
Kind regards,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
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>
---> 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>