Re: [Pharo-users] [Moose-dev] Call for action for Roassal
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. 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 ;-) > On Feb 24, 2016, at 05:51, Alexandre Bergelwrote: > > Dear community, > > As you may have seen, Roassal has entered a stabilization phase. The book > 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > ___ > Moose-dev mailing list > moose-...@list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile
Re: [Pharo-users] [Moose-dev] Call for action for Roassal
This is very cool. We will all benefit from this documentation. One thing that I would still like to see fixed before the release is the edge building (this problem of not being able to properly specify random objects to be taken into account when building edges). Could we work on that? Cheers, Doru > On Feb 24, 2016, at 9:51 AM, Alexandre Bergelwrote: > > Dear community, > > As you may have seen, Roassal has entered a stabilization phase. The book > 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > ___ > Moose-dev mailing list > moose-...@list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com “Live like you mean it."
Re: [Pharo-users] [Moose-dev] Call for action for Roassal
>> Dear community, >> What are the 3 aspects you would like to see improved in Roassal? > > My favorite improvement would not really be a Roassal feature > but would save me a lot of time: > I would like the configuration versions to stop depending on numbered > versions of outside dependencies (Glamour, Neo-JSON-Core) Hi! I do not get this. Relying on the baseline is not enough? Roassal is very simply packaged. Only 4 packages: Roassal, Trachel, Roassal2Spec, Roassal2GT. It is very unlikely that this list of package will grow (not until we have a Git integration at least). You can make your configuration directly point to these packages no? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.