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

List:       kde-kuml-devel
Subject:    Re: Project file format
From:       Jake Fear <fear1 () home ! com>
Date:       2000-01-31 21:46:14
[Download RAW message or body]

We do need a drawing item for the data/Package class, but I don't think any
work has been done on it yet.  For the file output, I dont' know the details of
XML myself, but I also know it is built on fairly simple concepts for things
like IO.  If there are any standards that exist  (DTD's) for representing UML
data in XML we should certainly follow them.  I think we have lots of work
coming up for IO, as part of a feature freeze.

Right now KUML is little more than a bunch of neat features barley holding on
my a thread.  We REALLY need to refine it itteratively.  If we go to far and
then try to integrate all at once we are going to find ourselves throwing out
LOTS of code, and possibly (I hate to say it) failing in the long run.  Simple
is better,  and if we freeze with our current feature set we are still ( I
think ) going to require 6-8 weeks just to stabilize enough to call it a
pre-alpha.....  Well, I'm done ranting now.

P.S. Pascal, running java on a P133 must be painfull ;-)  Is this ArgoUML you
mention a free program?

Cheers

On Mon, 31 Jan 2000, you wrote:
> Darius Stachow wrote:
> > 
> > Hi !
> > 
> > XML will be part of KDE2 (take a look at www.mosfet.org) and so I think we
> > should wait till KDE2 is available before we support XML.
> > 
> > BTW: Holger Knust is still in the team to do the XML support although we
> > haven't read much from him on this list in the last time.
> > 
> > Many of the current IO is already done and so I mean to keep this in the
> > spanning time (and maybe later, too).
> > Let's see how XML works when it's implemented and than we can make a decision
> > what we should use (kuml or XML or both).
> 
> I played again today with argouml, and found it good except that it is
> very slow (Java). 
> It saves its files in xml and xmi formats (it uses the java lib
> xml4j.jar).
> 
> As XML seems to be the future standard, it should be the one used for
> kuml, but we also need a working save/open feature for a 0.5 version,
> version that should be usable (a kind of demo-pre-alpha-vaporware).
> Unfortunately, and I don't know neither XML, nor XMI ...
> 
> What I liked the most in argouml is that it has a feature that gives you
> hints on your classes and reminds you of essential OO stuff. For
> example, if a class has no attributes, it tells you that it should
> implement the singleton pattern, and it explains you why. Maybe this
> kind of feature could be implemented in kuml, taking argo's rules :
> imagine an info window that displays all what is wrong in your class
> structures.
> 
> Argouml also supports the package drawing object, in a very neat way :
> is there some work in preparation for that in kuml ?
-- 
Jake Fear

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