03-19-2018, 11:31 PM
(03-19-2018, 10:59 PM)davenovo Wrote: Hi Daniel,
I am not worried about showing the dialog contents to ther user. I am worried about my own development experience. I will have tons of extra components on my form in the IDE, some of them for the form itself, some of them for the modal dialogs. Imagine if my main form can spawn 3 modal dialogs, each with 10 controls each. That means my main form has 30 extra controls, event handlers etc. In principle, you dont want to dump controls for 3 different forms on a single form in the IDE. Its very confusing.
I guess I don't see it as confusing unless the controls are oddly out of place. If the design calls for that much detail, then that's what you need. I have forms that have seven dialogs with controls in each. The IDE manages the controls with no effort on my part at all. No sweat.
I keep the actual volume of code down by using classes to handle the detailed processing. Many of my event handlers have a single line of code inside them. I can see where it would become a burden if you are putting a lot of code inside the event handlers. That's not the proper way to develop any longer. Using classes allows you to keep the business logic separated from the interface. I can simultaneously develop mobile and desktop interfaces for the same feature because all I'm doing is applying new skin.
The other alternative is to use different forms for everything that you would place into dialogs. The downside is lots of forms to mange. The upside is a very fast and responsive design. I've used this approach a few times as well.