J
Jon
We have an application written in VB6 which performs a lot of different
functionality for a helpdesk (create orders, create invoices, manage
employees, etc). It's written as an MDI application. Nearly everything I see
says MDI is really not a great design choice and I somewhat agree with that.
So, as we go over concepts for rewriting this app in .Net 2, I'm trying to
come up with how to convert it to an SDI application. We have nearly 150
different mdi child forms in the app, about 30 of those are directly
accessible from menu items, the others are forms that come up when using
those 30 main function forms.
Do you have a main form with your menus and task options which is always
shown and then simply open the new functional forms as standard windows
forms that will have their own taskbar item and menu bar, etc? (this seems
like the type of interface that outlook uses - the main frame of the
application and then a new form to write an email or open a task in). I
think this is the right design method, I'm just having trouble wrapping my
brain around the right method.
Thanks for any ideas on how this should be designed.
functionality for a helpdesk (create orders, create invoices, manage
employees, etc). It's written as an MDI application. Nearly everything I see
says MDI is really not a great design choice and I somewhat agree with that.
So, as we go over concepts for rewriting this app in .Net 2, I'm trying to
come up with how to convert it to an SDI application. We have nearly 150
different mdi child forms in the app, about 30 of those are directly
accessible from menu items, the others are forms that come up when using
those 30 main function forms.
Do you have a main form with your menus and task options which is always
shown and then simply open the new functional forms as standard windows
forms that will have their own taskbar item and menu bar, etc? (this seems
like the type of interface that outlook uses - the main frame of the
application and then a new form to write an email or open a task in). I
think this is the right design method, I'm just having trouble wrapping my
brain around the right method.
Thanks for any ideas on how this should be designed.