[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kuml-devel
Subject:    Re: Automatic Graph Layout
From:       flynn () lure ! u-psud ! fr
Date:       2000-10-19 9:42:46
[Download RAW message or body]

On Thu, Oct 19, 2000 at 10:18:53AM +0200, Thomas Förster wrote:
> I've browsed a bit in the web, starting from the link Gerard gave. For me it
> seems quite possible to implement automatic graph layout by ourselves. If you
> look to ftp://wilma.cs.brown.edu/pub/papers/compgeo/gdbiblio.ps.Z (the link
> from the paper), the paper contains an ANNOTATED bibliography listing over 300
> papers about many, many  aspects of graph drawing. Sure most of them are not
> online, but hey it seems most of us have an academic background (according to
> email domains), so know the way to a library.
> 
> But the problem is anyhow of high risk, as I think we
> can do it, but not how much time this will cost. 
> 
> GraphViz itself seems not to be a candidate, as for me also the license seems
> to be not GPL compliant. But hopefully there is someone who knows licensing
> issues better than Gerard and I. The license file for GraphViz is at
> http://www.research.att.com/sw/tools/graphviz/license/source.html
> 
> So I agree with Ed stating that we should first implement the minimum
> functionality that is needed in ANY case. This is for me a prototype which
> lets me load/save an XMI model and edit it. This means not yet graph editing.
> I want to create say a class and methods for it, even in a tree like
> representation: 
> 
> class Testclass
> |--Method Testclass()
> +--Method setValue(int bla)
> 
> .. (I think you get the point)
> 
> All other import/export, diagram editing, interoperability with similar
> applications is for me not part of the first iteration. 
> 
> Maybe we should use iteration cycles as proposed by Kent Beck for Extreme
> Programming (http://www.extremeprogramming.org for novizes) - 3 weeks for one
> iteration. So we learn to decide an issue of manageable size and to implement
> it, then to decide next issue ... This makes even requirements change
> management more easy. 
> 
> Thomas
> 

  I fully agree that automatic graph generation is definitely not for he first iteration.
Its just that the question has come up and I think its worth keeping in the back of our
minds for later on.

  Gerard

[prev in list] [next in list] [prev in thread] [next in thread]