SDI vs. MDI: Old question, new parameters
-
I'll be interested in the expert opinions to this one. I have never in 20+ year developing worked on an MDI solution (Access in the early 90 doesn't count) and simply don't give the client an option. Even MS, who promoted MDI heavily in the late 90's, shied away from using it in later development. Oh I remember one in VB5 and what a what a PITA that was.
Never underestimate the power of human stupidity RAH
My latest MDI project is a plant information system where instead of an elaborate menu system, it has a very simple main menu structure calling MDI's and the MDI's have a more elaborate menu structure pertaining to a specific operations area - makes application security also easier... The latest SDI is a SMS Admin system, this time round which is tabbed...
"the confused are confused beyond confusion" - Pik Botha (1990)
-
This question is as old as the dawn of windows itself, but this time round with more parameters added. I know all about SDI and MDI development, but I want to rest a case of which is best in terms of processing power. I have used both in my developing career and fully understand the pains and gains of each except: In terms of .NET 2+ and C#: Which is best in terms of performance: a MDI with a menu bar and two child forms - no matter the content - or two SDI's with the same menu bar and corresponding content. Forget the effeort to link the forms and carra data over from the one to the other - performance only, processing power, memory usage/footprint, JIT, GC etc. The real reason for this is I need to have some expert advice to shut some mouths shooting off in only one direction. If you can point me, give expert advice, direction or whatever to state a case I'll appreciate it dearly. Oh and I need it before the weekend - I want to enjoy the Bokke vis NZ and not bother myself about SDI's and MDI's. Cheers
"the confused are confused beyond confusion" - Pik Botha (1990)
Well I don't know about performance or anything like that, but have you noticed that WPF doesn't have any inbuilt support for MDI, if you want it you have to roll it yourself. Does suggest that it's no longer the 'recommend' way of doing things.
Simon
-
This question is as old as the dawn of windows itself, but this time round with more parameters added. I know all about SDI and MDI development, but I want to rest a case of which is best in terms of processing power. I have used both in my developing career and fully understand the pains and gains of each except: In terms of .NET 2+ and C#: Which is best in terms of performance: a MDI with a menu bar and two child forms - no matter the content - or two SDI's with the same menu bar and corresponding content. Forget the effeort to link the forms and carra data over from the one to the other - performance only, processing power, memory usage/footprint, JIT, GC etc. The real reason for this is I need to have some expert advice to shut some mouths shooting off in only one direction. If you can point me, give expert advice, direction or whatever to state a case I'll appreciate it dearly. Oh and I need it before the weekend - I want to enjoy the Bokke vis NZ and not bother myself about SDI's and MDI's. Cheers
"the confused are confused beyond confusion" - Pik Botha (1990)
If it's only possible to work on one project or workbook or database, then either is fine. I'd lean towards the SDI layout personally. The window is the document & all that... However, if you want to support working on -multiple- projects/workbooks/databases... Everything as SDI sheets could prove confusing to the user. Which workbook does a given SDI belong to? It better be clearly indicated somehow. I'd think an MDI window would be less ambiguous there. Just sayin... -- Ian
-
This question is as old as the dawn of windows itself, but this time round with more parameters added. I know all about SDI and MDI development, but I want to rest a case of which is best in terms of processing power. I have used both in my developing career and fully understand the pains and gains of each except: In terms of .NET 2+ and C#: Which is best in terms of performance: a MDI with a menu bar and two child forms - no matter the content - or two SDI's with the same menu bar and corresponding content. Forget the effeort to link the forms and carra data over from the one to the other - performance only, processing power, memory usage/footprint, JIT, GC etc. The real reason for this is I need to have some expert advice to shut some mouths shooting off in only one direction. If you can point me, give expert advice, direction or whatever to state a case I'll appreciate it dearly. Oh and I need it before the weekend - I want to enjoy the Bokke vis NZ and not bother myself about SDI's and MDI's. Cheers
"the confused are confused beyond confusion" - Pik Botha (1990)
I have thought of another way instead of using MDI or SDI, by using a panel container in a SDI form and show the forms through the panel container, and perhaps creating tabs at the bottom (or top) for each form opened... just a thought. This will act as both MDI or SDI. ...or start doing what MS or FF is doing with tabs. Select what you want to do and show it in a tab container. With WPF we have a bit of an issue using Terminal Services / Citrix / RDP. Good band with is not always available and we tend not to use to much "color" in the systems. I gave it a lot of thought, but millions of colors slow down the apps considerably. For stand-alone systems, WPF would be an answer.
"the confused are confused beyond confusion" - Pik Botha (1990)
-
This question is as old as the dawn of windows itself, but this time round with more parameters added. I know all about SDI and MDI development, but I want to rest a case of which is best in terms of processing power. I have used both in my developing career and fully understand the pains and gains of each except: In terms of .NET 2+ and C#: Which is best in terms of performance: a MDI with a menu bar and two child forms - no matter the content - or two SDI's with the same menu bar and corresponding content. Forget the effeort to link the forms and carra data over from the one to the other - performance only, processing power, memory usage/footprint, JIT, GC etc. The real reason for this is I need to have some expert advice to shut some mouths shooting off in only one direction. If you can point me, give expert advice, direction or whatever to state a case I'll appreciate it dearly. Oh and I need it before the weekend - I want to enjoy the Bokke vis NZ and not bother myself about SDI's and MDI's. Cheers
"the confused are confused beyond confusion" - Pik Botha (1990)
I think if you posted this on the Windows Forms forum, clarified exactly what you meant by "performance," and took off the "I need it before the weekend" (a variant of "send codez plz" ?) you might get some helpful responses. best, Bill
"Many : not conversant with mathematical studies, imagine that because it [the Analytical Engine] is to give results in numerical notation, its processes must consequently be arithmetical, numerical, rather than algebraical and analytical. This is an error. The engine can arrange and combine numerical quantities as if they were letters or any other general symbols; and it fact it might bring out its results in algebraical notation, were provisions made accordingly." Ada, Countess Lovelace, 1844
-
This question is as old as the dawn of windows itself, but this time round with more parameters added. I know all about SDI and MDI development, but I want to rest a case of which is best in terms of processing power. I have used both in my developing career and fully understand the pains and gains of each except: In terms of .NET 2+ and C#: Which is best in terms of performance: a MDI with a menu bar and two child forms - no matter the content - or two SDI's with the same menu bar and corresponding content. Forget the effeort to link the forms and carra data over from the one to the other - performance only, processing power, memory usage/footprint, JIT, GC etc. The real reason for this is I need to have some expert advice to shut some mouths shooting off in only one direction. If you can point me, give expert advice, direction or whatever to state a case I'll appreciate it dearly. Oh and I need it before the weekend - I want to enjoy the Bokke vis NZ and not bother myself about SDI's and MDI's. Cheers
"the confused are confused beyond confusion" - Pik Botha (1990)
I've made some MDI apps in the past. I once had a customer that wanted to display an app of mine across 4 monitors from 1 machine. Unfortunately, with MDI you are stuck in 1 monitor... and stretching an MDI app across 4 monitors would have looked stupid. If it was an SDI app, I could have supported all monitors by putting an SDI app window instance in each monitor. So that said, I think SDI's biggest advantage is multiple monitor support.
-
I think if you posted this on the Windows Forms forum, clarified exactly what you meant by "performance," and took off the "I need it before the weekend" (a variant of "send codez plz" ?) you might get some helpful responses. best, Bill
"Many : not conversant with mathematical studies, imagine that because it [the Analytical Engine] is to give results in numerical notation, its processes must consequently be arithmetical, numerical, rather than algebraical and analytical. This is an error. The engine can arrange and combine numerical quantities as if they were letters or any other general symbols; and it fact it might bring out its results in algebraical notation, were provisions made accordingly." Ada, Countess Lovelace, 1844
Thanks Bill, Code I do not need - have more than enough - have some of the best books in www.books24x7.com and next to me. However I gave it a thought too to take this to other forums as well. I merely wanted to hear what other say. Cheers
"the confused are confused beyond confusion" - Pik Botha (1990)
-
Thanks Bill, Code I do not need - have more than enough - have some of the best books in www.books24x7.com and next to me. However I gave it a thought too to take this to other forums as well. I merely wanted to hear what other say. Cheers
"the confused are confused beyond confusion" - Pik Botha (1990)
Hi Pierre, I did not mean to imply that if you posted this question on the technical forums you would "get code" in response; sorry if that's how you interpreted my response. What I meant to imply was that the technical forums are the place where you might find responses to your query that would be more helpful than the Lounge. The Lounge is supposed to be for "fanciful" things, personal things, sharing everything but programming questions. In practice, it is not, but that's another story. best, Bill
"Many : not conversant with mathematical studies, imagine that because it [the Analytical Engine] is to give results in numerical notation, its processes must consequently be arithmetical, numerical, rather than algebraical and analytical. This is an error. The engine can arrange and combine numerical quantities as if they were letters or any other general symbols; and it fact it might bring out its results in algebraical notation, were provisions made accordingly." Ada, Countess Lovelace, 1844
-
Hi Pierre, I did not mean to imply that if you posted this question on the technical forums you would "get code" in response; sorry if that's how you interpreted my response. What I meant to imply was that the technical forums are the place where you might find responses to your query that would be more helpful than the Lounge. The Lounge is supposed to be for "fanciful" things, personal things, sharing everything but programming questions. In practice, it is not, but that's another story. best, Bill
"Many : not conversant with mathematical studies, imagine that because it [the Analytical Engine] is to give results in numerical notation, its processes must consequently be arithmetical, numerical, rather than algebraical and analytical. This is an error. The engine can arrange and combine numerical quantities as if they were letters or any other general symbols; and it fact it might bring out its results in algebraical notation, were provisions made accordingly." Ada, Countess Lovelace, 1844
No offence taken. But I msut mention I got somewhere an answer out of the responses - now wars between SDI or MDI - have a clear understanding of the Pros and Cons use what is necessary. Cheers PS have posted in Windows...
"the confused are confused beyond confusion" - Pik Botha (1990)
-
This question is as old as the dawn of windows itself, but this time round with more parameters added. I know all about SDI and MDI development, but I want to rest a case of which is best in terms of processing power. I have used both in my developing career and fully understand the pains and gains of each except: In terms of .NET 2+ and C#: Which is best in terms of performance: a MDI with a menu bar and two child forms - no matter the content - or two SDI's with the same menu bar and corresponding content. Forget the effeort to link the forms and carra data over from the one to the other - performance only, processing power, memory usage/footprint, JIT, GC etc. The real reason for this is I need to have some expert advice to shut some mouths shooting off in only one direction. If you can point me, give expert advice, direction or whatever to state a case I'll appreciate it dearly. Oh and I need it before the weekend - I want to enjoy the Bokke vis NZ and not bother myself about SDI's and MDI's. Cheers
"the confused are confused beyond confusion" - Pik Botha (1990)
I hate SDI type image editors. I love SDI type browsers (do tabs count as SDI or MDI?) As for your question, I would assume performance to be better with an MDI application. Each "process" in a .NET app has a heavy memory footprint.
Todd Smith
-
I hate SDI type image editors. I love SDI type browsers (do tabs count as SDI or MDI?) As for your question, I would assume performance to be better with an MDI application. Each "process" in a .NET app has a heavy memory footprint.
Todd Smith
Todd Smith wrote:
I love SDI type browsers (do tabs count as SDI or MDI?)
SDI unless you're talking about Opera which is an real MDI implementation. eg you can unmaximize individual tabs within the browser; this means that popups can be represented as tabs within the browser without mangling their size/layout.
The European Way of War: Blow your own continent up. The American Way of War: Go over and help them.