In retrospect it would have been nice to name it something different than a
confuse the issue. I think taking the CDocument stuff out of a program will
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
See below...
"That document/view stuff is too complicated"
"I'm not saving anything to a file, so I don't have a document"
These are the Top Two Excuses. I had to explain to one client that their
embedded system
was the "document". They had gone through bizarre convolutions to remove
the
CDocument-derived class (but kept the CView-derived class!). I think it
is because they
don't recognize the notion of data-vs-display and think it is a file
issue.
****
I have been swayed into implementing small programs as dialog interfaces
on
occasion (and usually regretted it), but most of the time I use
Doc/View/MDI even when I just need one window so I can expand it when they
(as they always do) decide they need more than one set of data displaying
at
once.
****
While I will do dialog-based utility programs, any real product
programming is MDI. I
sometimes have to argue with the client: "You want MDI. Trust me, you
do". Sure enough,
six months later, I get something of the form "Can we have a <other kind
of view> of the
data?" and it is trivial to add it in. Or they'l just ask "Can we hook up
more than one
device?", and the answer is, sure. I'd already built that in. Helps
contribute to the
walks-on-water illusion it is nice to present to clients.
joe