>From dougo@ccs.neu.edu Sun Jun 22 18:39:04 1997
>
>Karl Lieberherr writes:
> > Demeter/Java is a little long, but clear and shows the alternatives:
> > Demeter/CLOS
> > Demeter/Perl
> > which are implemented elsewhere in a simple form.
> > 
> > Should we systematically use the name Demeter/Java in our documentation?
>
>I have tried to consistently use Demeter/Java when referring to the
>system as a whole, and demjava (lowercase) when talking about that
>particular program.  I think this is reasonable, although at the
>moment there's not much to Demeter/Java besides demjava-- basically
>j-gen-make (which may go away soon anyway in favor of option files).
>Or should AP Studio be part of Demeter/Java?  I think maybe it's
>separate because it's not necessarily language dependent-- one could
>design Demeter/C++ class dictionaries equally well.

I think that AP Studio is the name of the Demeter/Java Graphical User Interface.
So it is part of Demeter/Java. It will get a button to call the demjava
compiler. Demeter/Java consists of two programs: the compiler
demjava and the GUI: AP Studio. AP Studio will also have some dependency
on Java, for example, the part which allows us to browse and edit
behavior files.
>
>--Doug
>

-- Karl