UI design like Outlook
-
Hi, I have a question about UI design in NET. I am creating a scientific application with C# and VS2008. Currently I am using a tab conrol were till now I have 3 level tab depth (eg tab inside tab etc) which is not very convenient, nor user friendly. I am thinking to switch to an outlook UI style were the general tabs will be moved to left panel with the form of buttons. While the right panel will have the detail form again with tabs but lesser depth. So my question is what is the best approach of doing this? Should I move to a MDI where in the right panel will load detail form's in full mode? Or should I search for some specific tab component?
-
Hi, I have a question about UI design in NET. I am creating a scientific application with C# and VS2008. Currently I am using a tab conrol were till now I have 3 level tab depth (eg tab inside tab etc) which is not very convenient, nor user friendly. I am thinking to switch to an outlook UI style were the general tabs will be moved to left panel with the form of buttons. While the right panel will have the detail form again with tabs but lesser depth. So my question is what is the best approach of doing this? Should I move to a MDI where in the right panel will load detail form's in full mode? Or should I search for some specific tab component?
We use Infragistics Listbar, one of the few controls of theirs I like. It gives an excellent outlook style listbar, relatively easy to use which is a huge bonus from them. The only trouble with the ui design like you are proposing (I use it also) is when there is a large amount of detail to be displayed. I have a standard toolbar somewhere with alphabet buttons for filtering large sets. Use a DGV for detail, it's faster than a listview and easier to format.
Never underestimate the power of human stupidity RAH
-
Hi, I have a question about UI design in NET. I am creating a scientific application with C# and VS2008. Currently I am using a tab conrol were till now I have 3 level tab depth (eg tab inside tab etc) which is not very convenient, nor user friendly. I am thinking to switch to an outlook UI style were the general tabs will be moved to left panel with the form of buttons. While the right panel will have the detail form again with tabs but lesser depth. So my question is what is the best approach of doing this? Should I move to a MDI where in the right panel will load detail form's in full mode? Or should I search for some specific tab component?
Check out http://www.dotnetmagic.com/[^]
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
The woods are lovely, dark and deep, But I have promises to keep, And miles to go before I sleep, And miles to go before I sleep! -
We use Infragistics Listbar, one of the few controls of theirs I like. It gives an excellent outlook style listbar, relatively easy to use which is a huge bonus from them. The only trouble with the ui design like you are proposing (I use it also) is when there is a large amount of detail to be displayed. I have a standard toolbar somewhere with alphabet buttons for filtering large sets. Use a DGV for detail, it's faster than a listview and easier to format.
Never underestimate the power of human stupidity RAH
In my situation, I don't have large amount of detail to be displayed, rather data grouped in distinct way... I saw (don't remember where) an approach where instead of MDI the SDI is used with custom controls. A custom control in my situation would be a detail form which could show or hide depended on which button is clicked. Not quite sure if this approach is best.
-
In my situation, I don't have large amount of detail to be displayed, rather data grouped in distinct way... I saw (don't remember where) an approach where instead of MDI the SDI is used with custom controls. A custom control in my situation would be a detail form which could show or hide depended on which button is clicked. Not quite sure if this approach is best.
I let the listbar do the grouping, content is database driven. The details are only available in lists in the main form and any further information/work is done via dialogs. No data is manipulated in the main form. Dialogs of course are customised for each data type. I dislike the disappearing control paradign as I find it difficult to support and the main form becomes very bloated.
-
I let the listbar do the grouping, content is database driven. The details are only available in lists in the main form and any further information/work is done via dialogs. No data is manipulated in the main form. Dialogs of course are customised for each data type. I dislike the disappearing control paradign as I find it difficult to support and the main form becomes very bloated.
I see, However I am busting my head know how to implement the outlook approach... I mean is it MDI app and show/hide each time new form? Or do they use other pattern?
-
I see, However I am busting my head know how to implement the outlook approach... I mean is it MDI app and show/hide each time new form? Or do they use other pattern?
I can see only 2 types of data, list and calendar. Outlook may treat the sections differently but that is their choice, I suspect there are a number of user controls and a datalist tool. In my corporate CRUD life there is basically 1 type of data, lists, how you display them is just candy, can be very important but still candy. Where you do your data manipulation is more important to me as that is where the nasty bits like validation come into play. I never do this in the main form.
Never underestimate the power of human stupidity RAH
-
I can see only 2 types of data, list and calendar. Outlook may treat the sections differently but that is their choice, I suspect there are a number of user controls and a datalist tool. In my corporate CRUD life there is basically 1 type of data, lists, how you display them is just candy, can be very important but still candy. Where you do your data manipulation is more important to me as that is where the nasty bits like validation come into play. I never do this in the main form.
Never underestimate the power of human stupidity RAH
So you are saying that outlook uses the approach of manipulating controls in SDI? I found an article http://richnewman.wordpress.com/2007/10/26/user-interface-design-for-business-applications/[^] Where I like the UI design "Montage Tabbed Interfaces – ‘IDE-style’ interfaces" also in the below article http://social.msdn.microsoft.com/Forums/en-US/winforms/thread/e073c18f-1ffc-462b-b9d1-67444395a75c/[^] They suggest to use controls. Do you agree?
-
So you are saying that outlook uses the approach of manipulating controls in SDI? I found an article http://richnewman.wordpress.com/2007/10/26/user-interface-design-for-business-applications/[^] Where I like the UI design "Montage Tabbed Interfaces – ‘IDE-style’ interfaces" also in the below article http://social.msdn.microsoft.com/Forums/en-US/winforms/thread/e073c18f-1ffc-462b-b9d1-67444395a75c/[^] They suggest to use controls. Do you agree?
Net nazi stops me on the wordpress link but I understand the reply from JRQ I just don't have a requirement for that many disparate data types. I have not used MDI for many years, always was a kludge, so I can't compare, I like SDI. B/c I have only 1 basic type of data and 1 presentation style I have very limited need to communicate between controls. Mine is mainform calls dialog with an ID for the data required. Dialog return a dialogresult to the main form which updates the list from the database if required. I must admit my UI is VERY BORING for the users but then my environment is corporate CRUD where they are interested in the DATA not the eye candy. Whenever I have time I like to play with the UI a little but there is not a lot of time for pretties.
Never underestimate the power of human stupidity RAH
-
Net nazi stops me on the wordpress link but I understand the reply from JRQ I just don't have a requirement for that many disparate data types. I have not used MDI for many years, always was a kludge, so I can't compare, I like SDI. B/c I have only 1 basic type of data and 1 presentation style I have very limited need to communicate between controls. Mine is mainform calls dialog with an ID for the data required. Dialog return a dialogresult to the main form which updates the list from the database if required. I must admit my UI is VERY BORING for the users but then my environment is corporate CRUD where they are interested in the DATA not the eye candy. Whenever I have time I like to play with the UI a little but there is not a lot of time for pretties.
Never underestimate the power of human stupidity RAH
I completely agree with you ... first of all the app should function wout problems and after it should have "eye candies":) By the way I found an sample at http://windowsclient.net/downloads/folders/applications/entry1340.aspx[^] witch might suit my needs, but it uses a control manipulation approach.
-
I completely agree with you ... first of all the app should function wout problems and after it should have "eye candies":) By the way I found an sample at http://windowsclient.net/downloads/folders/applications/entry1340.aspx[^] witch might suit my needs, but it uses a control manipulation approach.
DevEx do some nice stuff and have a good rep here on CP.
Never underestimate the power of human stupidity RAH
-
DevEx do some nice stuff and have a good rep here on CP.
Never underestimate the power of human stupidity RAH
Do you mean commercial components?