> I appreciate to have a status update on the activities that everybody has
> been assigned to.
U9-U15 checked-in.
> Can I hope to have something to discuss for the first week of November?
How do you want design documentation checked-in? I don't think it
should go in the use cases, but rather as a separate programming
specification.
For example, my programming specification for the Microsoft integ.
(MSO and eventually Wexplo) would describe the design of a
"package" (I use that term loosely) covering U9-U15.
I'm assuming format will follow the use cases, more or less (a big
question is what sorts of "headings" you want ... or I can just
propose some in my draft).
How do we want to structure the source code directories in CVS?
I'd like to check the Word prototype and proof-of-concept source code into
directories like,
edocs/src/proto/interop/mso/
edocs/src/proof/interop/mso/
to keep them seperate from the development code. Prototypes and Proofs
are meant to be illustrative, not prescriptive, so they shouldn't be mixed into
the Development tree, IMO, since the "production" code may be slightly or
wholly different.
> Derek, I'm always waiting the requirements for the windows coder you need to
> do the hard work.
The ideal "Wexplo" programmer,
+ Expert Microsoft Windows coder.
+ COM a must.
+ Windows Shell API a strong plus.
Windows Shell API experience will make it easier for the person;
approximately 40 hrs coding (I can't estimate the amount of debugging
that'll be required tho). A bad shell extension will crash Windows as
fast as a bad device driver.
Derek Harmon
|
