I've used Together/J off-and-on since June 1998. Like most tools, there are
some things that I like about it, some things that I don't. Though I agree
with your comments regarding the merit of Together/J as well as the
complexity of writing a modelling tool, a reimplementation of Together/J is
not the solution that I'm offering.
There are some drawbacks with Together/J for my purposes. For one, using
the Whiteboard edition, you cannot specify an external editor and therefore,
to link Emacs into it, I need to buy at least the developer's edition
license, and since we already have a UML modelling tool, that is not an
option. Secondly, what I'm proposing is NOT a modelling tool, but a means
by which you can do class browsing. For instance, we had a situation here
where some of our modal dialogs were working correctly with JavaHelp, and
others were not. By parsing the entire project in OO-Browser and showing
all project descendants of JDialog, we were able to trace common ancestry
between of working and non-working dialogs, and make fixes to top-level
classes. Note that these graphical views are not models; they are trees
that show descendants of a given class.
Stephen L. Faustino
Senior Software Engineer
SecureLogix Corporation
Direct/Vmail (210)402-9669x949
mailto:[EMAIL PROTECTED]
This email is intended for the named recipient(s) only and may contain
information that is privileged and/or confidential. Nothing in this
email is intended to constitute a waiver of any privilege or the
confidentiality of this message. If you have received this email in
error, please notify me immediately by reply and delete this message.
-----Original Message-----
From: John Olsson [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 17, 2000 6:30 AM
Cc: [EMAIL PROTECTED]
Subject: Re: JDE with OO-Browser
> I'm curious if anyone else is interested in having the capability of
> viewing a graphical class structure for a given class. I've been trying
> to evaluate how much effort it would take to implement this functionality
> (not that I'm trying to make more work for anyone). With the integration
> of the beanshell, we would have the capability to add the graphical class
> tree.
>
Depending on how much information you want to have in the diagram, this
can be very complicated to implement. I suggest that you take a look at
Together/J, which is an OO modelling tool implemented compleatly in
Java. It comes in two versions, on for free and one that costs money. In
the free version there is no limitation on the number of classes etc.,
but you can't print the diagrams. One nice thing with Together/J is that
it does not store the object model in a special file (only the diagram
layout), instead it uses the source code as the model and stores link
information etc. as JavaDoc comments.
This means that there is no reverse engineering (or export) button in
Together/J, it dynamically updates the diagrams as the source code
changes.
Together/J can also be manipulated through a Java API, so you can add
your own menu items, dialogs, configuration panels, ...
You can find Together/J on http://www.togethersoft.com/ .
And no, I *don't* work for Togethersoft. ;)
/John
--
LM/ERA/LVA/KD John Olsson mailto:[EMAIL PROTECTED]
Ericsson Radio Systems AB, Box 1248, S-581 12 Linkoping
-------------------------------------------------------------
Phone: +46 13 321070 ECN: 868 1070 Fax: +46 13 287370
-------------------------------------------------------------
I was doing object-oriented assembly when I was 1 year old...
For some reason my mom insists on calling it "Playing with blocks"
