Solved

Theoretical Question: Which is the better interface - MDI or SDI?

Posted on 2009-07-15
4
385 Views
Last Modified: 2013-12-17
I am about to embark on a software project that involves Windows Forms. I have approximately 10 forms that will maintain the data and another that will allow for reporting. I have a relatively novice set of users in this department.
Which would be the better path to travel given the number of forms and the skill level of the user base?
0
Comment
Question by:Euless_Tech
  • 2
4 Comments
 
LVL 4

Expert Comment

by:j_s_kelley
ID: 24863518
I am not sure I understand your question.  Do you have several paths to choose from?  What are the options?  The way the question is phrased, it is very broad in scope.  What do you mean by the "best" path?  People write books on the best way to write applications.  Thanks.
0
 
LVL 8

Assisted Solution

by:RyanAndres
RyanAndres earned 50 total points
ID: 24863557
Personally I would go with MDI for a couple of reasons:

1) It makes it easier for the user to switch between windows
2) Allows all forms to communicate with each other / share data

Make sure your novice users try to avoid coupling the forms. By decoupling each form it provides better maintainability. Ie, In a managed code environment developers can work on each form without affecting the others.
0
 
LVL 4

Accepted Solution

by:
j_s_kelley earned 75 total points
ID: 24863584
Sorry, didn't read the original question to begin with.  My fault.  :(  To choose between MDI and SDI really depends on the nature of the application.  I have seen both used well and both done completely wrong.  I like MDI if truly, each child represents a "document" in some way.  With beginners, modal dialogs work fine because it makes them finish their thought before moving on.  Modal dialogs (SDI) is easier to control what happens when.  With MDI, if there is ANY interrelation between the documents, you can get yourself into a coordination nightmare (i.e. update one screen which might cause another to be invalid.)  As for user level, there are many very common applications that use MDI, for example, the suite of Office products are mostly MDI.  I don't think that will throw anyone.  Just make sure that the model fits the nature of the application.
0
 

Author Closing Comment

by:Euless_Tech
ID: 31603960
Thanks for the input. Being a somewhat beginner to intermediate developer in C#, I will probably go with SDI since it's easier to control.
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

A long time ago (May 2011), I have written an article showing you how to create a DLL using Visual Studio 2005 to be hosted in SQL Server 2005. That was valid at that time and it is still valid if you are still using these versions. You can still re…
"Disruption" is the most feared word for C-level executives these days. They agonize over their industry being disturbed by another player - most likely by startups.
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, Just open a new email message.  In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…
In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now