Re: How to - SDI

From:

"Tom Serface" <tom@camaswood.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Thu, 21 Jan 2010 07:17:38 -0800

Message-ID:

<ukTHfzqmKHA.2164@TK2MSFTNGP02.phx.gbl>

I can't speak for Joe or his teaching style, but for me it's just espousing
an opinion. I would never tell anyone 'not' to do it or that it was
illegal, just that I think building apps the other way is a better idea. I
had a few bad SDI experiences years ago.

That said, my favorite applications are those like the Office apps where
they are really tied together, but each doc appears in a separate mainframe
so looks like it's on SDI.

Tom

"Hector Santos" <sant9442@nospam.gmail.com> wrote in message
news:uh38XLnmKHA.1212@TK2MSFTNGP04.phx.gbl...

Why would a teacher restrict the mindset of students with such a highly
subjective opinion, which is highly isolated to one own experiences and to
many, not really true in the market place? There are untold thousands of
SDI applications. Its unconceivable to even notice that it might even be a
rarity. Its not. SDI has its place as well as MDI and they offer two
different set of design needs. We use a MDI for our embedded p-code
language/compiler IDE. We use SDI for monitors, configuration tools, etc.
This isn't an oddity or exception.

Very odd statement.

--

Joseph M. Newcomer wrote:

The only time I have ever built an SDI app is when I teach the MFC course
and one of the
exercises is an SDI app. I tell my students that SDI apps are
exceptionally rare, usually
useless, and inevitably the client will decide that what was really
wanted was MDI, so the
simplest solution is to always start with MDI.
joe

On Wed, 20 Jan 2010 13:14:03 -0800, "Tom Serface" <tom@camaswood.com>
wrote:

I see many have responded to your question, but I wanted to just put in
that I always build new applications as MDI even if I only plan to have
one document and/or one view. It's simple to change the menus and make
the child window fill out the whole mainframe and then if you ever want
to convert in the future (which you likely will) you can easily add the
new functionality.

That's the same reason I never use dialog applications. It is just as
easy to create a formview based MDI app and build from that.

Tom

"rockdale" <rockdale.green@gmail.com> wrote in message
news:9f08bb0a-ec24-4b33-bea4-2a35be301c99@a32g2000yqm.googlegroups.com...

Hi, all:

All my experience on MFC is dialog based application. And now I try to
learn the SDI and MDI based application. I create a sample SDI
application, but then I have no idea what is the next step I need to
do. Like if I want use can enter some data in a CEdit control, how
should I do that. Do I need to create a CDialog and then load it into
the main frame, how to load a CDialog/CView into a main frame, all the
examples on the internet are showing an empty childview, how can I
make the childview doing something?

Thanks in advance.
-Rockdale

Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm

--
HLS