RE: [Modus-devs] Modus Developer's Guide

[Nathan D. <na...@ch...>]

Jeremy:

Wow, this is great.  I'll have to give it another look to make substantive
comments, but this is fantastic.  BTW, do you have a SourceForge ID?  You're
not even listed on the project team there ;)

 - n
  -----Original Message-----
  From: mod...@li...
[mailto:mod...@li...]On Behalf Of Jeremy
Firsenbaum
  Sent: Monday, November 18, 2002 9:49 AM
  To: modus devs
  Subject: [Modus-devs] Modus Developer's Guide


  Gentlemen

  It seems to me that we're in need of terminological clarity. There are
still some facets of the redesigned framework we do not have a handle on,
and much of the debate this past week has been about the meaning of the
content object model. To this end I have put together a document that
describes the code base as it currently stands. This is not meant to be
prescriptive in any way - much of the design is still up for grabs in my
opinion. I've tweaked things half a dozen times in the past week alone after
some great suggestions by Nathan and Sean.

  I hope this addresses many of the concerns Nathan raised on Friday, some
of which Sean has already addressed. Just writing this has caused be to get
much clearer on what I've done - see the lengthy note on the contentType
declaration in the Descriptors section. What I hope is that this will
provide some grounding to our discussions and allow us to solidify the
architecture so that we can concentrate on implementation.  In other words,
if we build a near-operational developer's guide, then we can easily build
an operational framework - as Hal Helms always insists: code your
documentation.

  -Jeremy