Message-Id: <9301182335.AA28105@Athena.MIT.EDU>
To: jud@ceci.mit.edu, pbailey@ceci.mit.edu, harada@ceci.mit.edu,
        htomi@ceci.mit.edu, mau@ceci.mit.edu, lerman@Athena.MIT.EDU,
        davis@Athena.MIT.EDU, lynne@Athena.MIT.EDU, schluss@Athena.MIT.EDU,
        aybee@Athena.MIT.EDU, wjeuerle@Athena.MIT.EDU, jert@Athena.MIT.EDU,
        chess@Athena.MIT.EDU, samaa@Athena.MIT.EDU, mohcm@Athena.MIT.EDU,
        sigmund@nora.hd.uib.no, achiqui@roman.uib.no
Subject: Design Spec draft
Date: Mon, 18 Jan 93 18:39:19 -0500
From: Judson Harward <jud@ceci.mit.edu>


I am distributing the current draft of the following chapters:

	Overview
	Basic Services
	Control Classes
	ADL
	Coding Practice Appendix

Adam has commented and contributed to all of it, and has written most of
the section on the Object Model as well as the sections on metaclass
services and method objects.  Ebe's work on editors has driven much of Adam's
and my thinking on the object model and metaclass services.

There are clearly gaps to be filled in.  In particular, the following
pieces are missing:

	> section in Chap 2 on thread of control and the base event loop
	> completed discussions of all the control classes in Chap 3
	> sections in Chap 3 on
		) application life cycle
		) control engine processing loop
		) control synchronization
	> section in Chap 4 on how a persistent ADL description gets
	  written

There also needs to be whole chapters written on the resource manager
and error handling.  Since these two topics are heavily platform
dependent, I do not expect to have reasonable drafts before we have
Sigmund and the Windows engineer here.  I am not even sure who will be
responsible for writing those chapters.  But we will need place holders
before this version of the spec can go out.  Sigh.

The version of this doc that I am circulating lives in read-only form in

	/mit/ceci/musedev/doc/Publish/CC_ADL.1.18.fm

I am clearing the change bars on my personal copy, and will continue to
add and edit.  I expect to circulate an updated version on the 24th, but
will pass around sections to those most concerned or curious sooner.

Please, let's all pass around what we have now so we can see where the
gaps are, and so we can start to deal with the yawning gaps between
modules.  I also believe that Steve would like a snapshot of current
work before he heads out to the West Coast tomorrow afternoon.