[Pharo-project] Roassal Survey

Hello! As you probably know, Roassal was presented at ESUG. We received a lot of positive feedback from you and also a lot of request for features. Thank you very much! We want to start working on this, but also prioritize what seems to be more urgent. For this, we would like to survey the c

[Pharo-project] Roassal Survey

I just wonder what is necessary to use Roassal not only as a visualization engine of existing data but to give it more interactivity to create new data/shapes/connections. An example: one can build a UML class shape and visualize the existing class hierarchy of Pharo with the current engine. But

Re: [Pharo-project] Roassal Survey

What is it? Thansk Hilaire Le 25/09/2012 16:48, Vanessa Peña Araya a écrit : > Hello! > As you probably know, Roassal was presented at ESUG. We received a lot > of positive feedback from you and also a lot of request for features. > Thank you very much! > > We want to start working on this, but

Re: [Pharo-project] Roassal Survey

Roassal is a visualization engine. You can find more information (including screenshots and a screencast) here: http://objectprofile.com/roassal-home.html Thanks, Vanessa. On 09/25/2012 11:57 AM, Hilaire Fernandes wrote: What is it? Thansk Hilaire Le 25/09/2012 16:48, Vanessa Peña Araya a

Re: [Pharo-project] Roassal Survey

I don't know your project scope, but these pointers may help you to grab some features to implement: http://www.tm4.org/mev/features Also take a look into the Circular Genome Viewer: http://wishart.biology.ualberta.ca/cgview/gallery.html specially the browsable maps http://wishart.biology

Re: [Pharo-project] Roassal Survey

This is not that we do not have ideas :-) Our todo list includes: - book chapter on Roassal - exporters (e.g., HTML, SVG, JavaScript) - semantic zooming - way to compose shapes - scalability We obtained this list from our personal needs and the need of the Moose and VW communities. Va

Re: [Pharo-project] Roassal Survey

On Tue, Sep 25, 2012 at 10:15 PM, Alexandre Bergel wrote: > This is not that we do not have ideas :-) > > Our todo list includes: > - book chapter on Roassal > - exporters (e.g., HTML, SVG, JavaScript) > - semantic zooming > - way to compose shapes > - scalability > > We obtained this li

Re: [Pharo-project] Roassal Survey

> I have a colleague who is working on epidemiological modeling and he > needs to be able to visualize epidemiological data from Vietnam from a > lot of diseases in order to discover some patterns. He already done > some work by hand and definitively need some way to automate the > process. Sound

Re: [Pharo-project] Roassal Survey

You asked for it Three scenarios... 1. Mind Mapping tool similar to http://freemind.sourceforge.net - MEDIUM priority. I think Roassal would provide a lot of advantages to such an application - and in return be a great reference case for testing interacti

Re: [Pharo-project] Roassal Survey

Thank you, Ben. And yes, this is the kind of things that are very useful. 3. Electrical Software Development Platform - CRITICAL priority Of course, my own project to complete my masters within the next couple of months!! This is implementing a model browser for the IEC 61970 Common Informatio

Re: [Pharo-project] Roassal Survey

Hello everybody, During the weekend I had a look at the Roassal project and I found it very good. Moreover I find that asking around the community for good ideas to drive the future of the project a cool initiative. About that, I completely agree with Ben's first 3 directions. Other cool ideas in

Re: [Pharo-project] Roassal Survey

Thanks Ciprian! Cheers, Alexandre On Sep 26, 2012, at 3:49 PM, Ciprian Teodorov wrote: > Hello everybody, > > During the weekend I had a look at the Roassal project and I found it very > good. Moreover I find that asking around the community for good ideas to > drive the future of the proje

Re: [Pharo-project] Roassal Survey

Thanks Torsten for your input. Indeed, many expressed a similar interest: being able to graphically edit a graph. Cheers, Alexandre On Sep 26, 2012, at 11:03 AM, Torsten Bergmann wrote: > I just wonder what is necessary to use Roassal not > only as a visualization engine of existing data > b

Re: [Pharo-project] Roassal Survey

Our todo list includes: - book chapter on Roassal Maybe don't bother with that. Write short blog posts showing the stuff you can currently do with Roassal. And keep writing as the project evolves. I feel like the time a book is out, it's already outdated by the implementation.

Re: [Pharo-project] Roassal Survey

>> Our todo list includes: >> - book chapter on Roassal > > Maybe don't bother with that. Write short blog posts showing the stuff you > can currently do with Roassal. And keep writing as the project evolves. > > I feel like the time a book is out, it's already outdated by the > implementatio

Re: [Pharo-project] Roassal Survey

On 26/09/12 15:19, Alexandre Bergel wrote: Our todo list includes: - book chapter on Roassal Maybe don't bother with that. Write short blog posts showing the stuff you can currently do with Roassal. And keep writing as the project evolves. I feel like the time a book is out, it's already

Re: [Pharo-project] Roassal Survey

Ciprian Teodorov wrote: Another feature that I think it is missing in most (if not all) graph viewers/layout systems/editors is the possibility to have connection ports on the hierarchical nodes in order to preserve the connections passing through the hierarchy. some pointers: http://www.slides

Re: [Pharo-project] Roassal Survey

Ciprian, Thanks for your detailed reply. Some comments inline... Ciprian Teodorov wrote: Hi Ben, Sorry for the delay, I was very bussy these last few days. Attached to this mail you will find some drawings showing what I mean. The first attachement [1] show the two most important graph concep

Re: [Pharo-project] Roassal Survey

> Alexandre, I think this example shows what I was badly hinting at with my > "ROElement>>mostSpecificParentCommonWith:" thread. This used to decide which > level within a hierarchy of sub-element edges are stored. Referring to the > first attachement of Cipirian's post "Figure 2(a)", I think