I am designing a WinForms CRUD “like” app for a large group of Nurses and Social Workers to interact with Client information.
There are many different forms(about 30ish) that they need to “possiblly” interact with for any given client and they “can be” required to jump from one to another for a specific person.
I am strugghling with the design of the user interface. I have only designed very simple linear WEBForm CRUDs where you do what you need on a page and click next.
What makes the mont sense for a non-linear WINForm CRUD app?
I had started down the path of tabs with embedded forms in those tabs but, possibly due to my lack of ability, the program feels very bulky. I am not sure straight MDI is the way to go as I have very simple users who may be confused easily if windows are “hidden.”
I would GREATLY appreciate any advice, insight, or examples anyone might have. Espeacially if anyone has had to make a WINForm CRUD app themselves.
What UI layout worked(or didn’t) for you?
An example of what mine currently looks like is here –>
From DevFiles
There are a few accepted patterns here, and you can sometimes combine them productively:
Visual Studio’s Tools|Options)
Mail/Calendar/Contacts)
The Collapsing Panels are not a standard control but there are several implementations available (here’s just one)
And your not alone, for some inspiration see this SO answer.