开发者

Surely MDI not so bad? [closed]

开发者 https://www.devze.com 2023-01-14 05:55 出处:网络
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references,or expertise, but this question will likely solicit debate, a
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 12 year开发者_高级运维s ago.

Surely MDI not so bad?

I have an ERP-type app and I have chosen a MDI UI model. The reason for this is to enable the user to multitask. Yes, many say that a user cannot multitask, but hear me out.

My app has several modules or functional areas e.g. Admin, Pricelists, Sakes Orders, Production, Stock Shipping, etc. I chose to create a MDI parent window for the main app window with a toolbar button for each module.

So let's say the user wants to create a Sales Order. He clicks the Sales Order button on the main toolbar and the Sales Order window appears. This is a MDI child that allows the user to create and edit a sales order and perform some functions on it e.g. Post, Accept, etc. So, if you are in the middle of creating a sales order and you need to change a pricelist or add some reference data you need in the SO, you simply open that module from the toolbar without having to abandon the SO. You cannot accept the SO, because it could violate business rules.

My app is not MDI in the sense of editing more than one document of the same kind like XLS or Word. The modules each have their own MDI child window.

Comments would be appreciated.


MDI is not bad. It is just pointless nowadays. SDI (Single Document interface) with nice docking manager and good tabs support is sufficient enough.

Look at your IDE for example. I am almost sure that it is SDI (like Visual Studio, Delphi, Eclipse, Net Beans, etc.)


There's nothing wrong with MDI if you have good reasons for doing so. However, the reasons you have expressed are not really valid reasons to choose MDI in my opinion. You can just as easily do what you want with SDI popup windows, so long as they are non-modal.

The disadvantage of MDI is that it doesn't work very well in multiple monitor situations. The advantage of MDI is that it provides lots of nice child window management features (ctrl-tab, etc..) that you would have to emulate in SDI.

I'm not saying that MDI is bad, or that it is bad for your circumstances, but simply being able to work with more than one window at a time is not a reason to choose MDI.

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号