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

List:       kde-kuml-devel
Subject:    Re: Looking over the code a little more...
From:       Jake Fear <fear1 () home ! com>
Date:       1999-11-26 23:09:09
[Download RAW message or body]

HI, I think the propose file format in this message is a good idea.  It gives
lots of flexibility and is still quite simple.

On Thu, 25 Nov 1999, you wrote:
> Hi !
> 
> On Mit, 24 Nov 1999, you wrote:
> >That sounds like a pretty good idea.  The other tools that I use have a
> >slightly larger idea about what should be saved in a single file.  All diagrams
> >and class definitions are bundled together in a single file (kind of like all
> >thhe souce/docs/etc in kdevelop), where you can also store the URLs for
> >documentation etc...  As long as all objects remain responsible for their own
> >IO this would probably be a simple extension of what you mention above should
> >we decide its appropriate.
> How about a file format like this (an example):
> 
> File: workspace
> ===========================================
> workspace W {
>  Path = /home/kuml/workspace;
>  classrepository {
>   class A {
>    IncomingRelationship = &R;
>   }
>   class B {
>    OutgoingRelationship = &R;
>   }
>   class C;
>  }
>  relationshiprepository {
>   generalizationrelationship R {
>    Start = B;
>    End = A;
>   }
>  }
> }
> 
> File: diagram1.kuml
> ===========================================
> classdiagram diagram1 {
>  Workspace = /home/kuml/workspace;
>  drawingclass _A {
>   Class = &A;
>  }
> drawingclass _B {
>   Class = &B;
>  }
>  drawinggeneralization _R {
>   Relationship = &R;
>  }
> }
> 
> File: diagram2.kuml
> ===========================================
> classdiagram diagram2 {
>  Workspace = /home/kuml/workspace;
>  drawingclass _C {
>   Class = &C;
>  }
> }
> 
> 
> Comments ?!
> 
> 
> -- 
> Open your mind ...
> Darius Stachow
-- 
Jake Fear

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