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 terms of ergonomy can be found in the Yed<http://www.yworks.com/en/products_yed_about.html>graph drawing tool. >From my experience working on computer-aided design tools for the electrical (electronical) industry i can say that one very important feature that these kind of tools need is the ability to create/edit large hierarchical graphs. From my perspective a electrical circuit is nothing more than a large graph of interconnected elements with each node representing a physical device. Hierarchical composition of such structures is necessary to ease the understanding of the system. In consequence IMHO being able to easily dive-in and get-out of hierarchical components is the most important feature that Roassal is missing right now. Just imagine looking at a layed-out graph of ten interconnected nodes, then just by clicking on one of these nodes the view is replaced by another graph representing the inner components. Furthermore I believe that such an approach can be abstracted away to more complex interactions (opening a view with an editor window on that particular instance of the node, etc). 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.slideshare.net/teodorov/tools-and-crossbarbased-nanocmos-architectures http://stiff.univ-brest.fr/~cteodorov/manuscript-teodorov_FINAL.pdf Cheers, Ciprian Teodorov On Sep 26, 2012 6:16 PM, "Vanessa Peña Araya" <[email protected]> wrote: > 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 >> Information Model. I showed this to Alex a while ago and am just now >> getting back to the point I was at before switching from Mondrian to >> Roassal. While this has taken a while I am very happy with the additional >> control I have with Roassal (and a lot of this time has been too many >> demands by my day job). Perhaps a rough early release is not too far away. >> > I'm sorry but I don't know this, so I don't understand really. Is there > some place I can see it? > > As yes, the features you mentioned are interesting. You are not the first > to mention features 4, for example. > > Thank you very much :) > > Vanessa. > > >> 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 list from our personal needs and the need of the Moose >>> and VW communities. >>> >>> Vanessa is working on a proposal for ESUG to help us on the development >>> of Roassal. We are therefore surveying the Pharo community in case of there >>> is a wished feature that we did not see or did not put high on our >>> todolist. We are currently maintaining Roassal (i.e., fixing bugs) and >>> pursuing our innovation effort (i.e., implementing cool ideas). The ESUG >>> support will help us increase our productivity. >>> >>> And yes, we would love to see someone use Roassal to visualize genome, >>> DNA and other biological data. We are ready to provide a strong support. >>> >>> Cheers, >>> Alexandre >>> >>> >>> On Sep 25, 2012, at 12:33 PM, Hernán Morales Durand < >>> [email protected]> wrote: >>> >>> 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 <http://www.tm4.org/mev/features> >>>> >>>> Also take a look into the Circular Genome Viewer: >>>> http://wishart.biology.**ualberta.ca/cgview/gallery.**html<http://wishart.biology.ualberta.ca/cgview/gallery.html> >>>> >>>> specially the browsable maps >>>> >>>> http://wishart.biology.**ualberta.ca/BacMap/cgview_** >>>> linked_maps/NC_003198/index.**html<http://wishart.biology.ualberta.ca/BacMap/cgview_linked_maps/NC_003198/index.html> >>>> >>>> check out the Expand+ and Rotate+ operations >>>> >>>> Other very nice engine is Circos >>>> >>>> http://circos.ca/ >>>> >>>> which contains plots that has been published in Science, Nature and >>>> PLOS. >>>> >>>> Cheers, >>>> >>>> Hernán >>>> >>>> >>>> On 25/09/2012 11:48, Vanessa Peña Araya wrote: >>>> >>>>> 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 community about >>>>> 1 - what are the features you would like to see in Roassal. Please, >>>>> provide a list of features requests and tell us about their priority >>>>> 2 - scenarios where you would like to use Roassal. >>>>> >>>>> Thank you very much, >>>>> Vanessa. >>>>> >>>>> >>>>> >>> >> >> >> > >
