To: jim
Subject: Notes on the DECEMBER-DELIVERABLE
--Text Follows This Line--
Just some thoughts:

1) I think you said yesterday that a working mouse was not a #1 priority; you
should definitely down-grade the mouse to #2 status in your document.  The
prototype-phase screen requirements need to be explained further, as I'm sure
you realize.  (That is an area where some might be tempted to reinvent the
square wheel.)

2) It will be useful at some point ('tho not necessarily in the proposal) to
assign public responsibility to each person for implementing his particular
K/Mac piece.  (One each to start with!)

I've already expressed my interest in focusing on file loading and related
areas.  The sooner that formal responsibility is articulated to the group as a
whole, the more happy me.

The K/Mac files piece is a clear-cut, well-defined project.  It is to our
long-term advantage to implement this in a manner that will bridge nicely to
the existing Lambda code.  I know I can do justice to it, providing the
Montreal code is reasonable.

  K/Mac files sub-tasks:

        Pathnames -> KMAC-access -> (streams? ->)  OPEN -> LOAD
                                                        -> VIEWF etc.

3) I don't understand the following paragraph, 'tho I am sure it relates to
RG's cold-load builder efforts:

        A new internal "cold" load band for the Lambda, capable of being
        ported to the Falcon

Does this mean the new thing has to boot a lambda world?

  --Keith