[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re: Presentation on Xanalogical Data Structures
- To: xanadu@xxxxxxxxxx
- Subject: Re: Presentation on Xanalogical Data Structures
- From: Don Dwiggins <d.l.dwiggins@xxxxxxxxxxxx>
- Date: Mon, 16 Aug 2004 10:43:48 -0700
- In-reply-to: <1092290997.10235.82.camel@xxxxxxxxxxxxxxxxxxxx> (Jeff Rush's message of "Thu, 12 Aug 2004 01:09:58 -0500")
- References: <1088593794.19829.81.camel@xxxxxxxxxxxxxxxxxxxx> <1091854291.4865.14.camel@xxxxxxxxxxxxxxxxxxxx> <p06002005bd3d69f7ba3f@[10.0.1.102]> <1092290997.10235.82.camel@xxxxxxxxxxxxxxxxxxxx>
Jeff, definitely good stuff. As one who's been interested in
Xanadu for quite a while, but never had occassion to get involved
more deeply, I'm happy to see the concepts being made more
publicly accessible.
In reply to:
Definitely magic stuff. One question - in explaining all of
Xanadu, say in a book or presentation, would you start at the
top and work down to the details, or start with the details and
assemble the architecture piece by piece?
For a good presentation, you'll have to do both, and maybe some
middle-out as well. Off the top of my head, I'd say start with
the goals to be achieved, and how it's supposed to look/work at
the interfaces (user, automated client, peer); then discuss the
issues that arise, and the problems to be solved, as a lead-in to
the architecture, algorithms and constructs that address the
problems and issues (this provides a hook for discussing
performance, open issues, TBDs, etc.). Then, work back toward the
top (outer) level, showing by some examples (use cases) how it all
hangs/works together.
FWIW,
--
Don Dwiggins I'm sorry for creating such a complex design,
d.l.dwiggins@xxxxxxxxxxxx but I didn't have time to make a simple one.
-- Hermann Püterschein