Reprinted, good learning article
After reading it, I didn't quite understand it at first, but after a few tests, I realized the power of dev. I have been engaged in Winform development for many years. Due to the needs of the project, I have designed various interface effects. Generally speaking, by using traditional interface control elements and rationally designing the layout, a relatively standard interface can be designed; using some skinnable controls or some interface components, it is possible to design relatively good-looking interface effects, such as the popular ones in the past. ActiveSkin, IrisSkin and DotNetSkin, etc., which can skin the traditional interface elements, are indeed much better than the standard gray interface controls. However, with the development of interface control components, it is generally preferred to use relatively large control groups. In addition to providing well-designed interface controls, they also provide a variety of colorful interface styles to choose from, such as DotNetBar, netadvantage, DevExpress and other large interface control groups.
No matter how the interface design changes, the general basic principle is to provide customers with interface effects that are intuitive, easy to use, and experience better. From the development of Office, we can also see the overall trend of interface effects, from standard controls to The current Ribbon form, from monochromatic to colorful interface styles, provides us with a good interface design reference, and large interface components also imitate this trend. Closer to home, let's talk about things in detail, currently I tend to use a Ribbon-based interface, and an interface design based on the traditional interface combined with the OutLook style.
1. Interface based on Ribbon style
The above interface style is a relatively elegant interface layout that conforms to the Office interface effect. By focusing different function blocks on different panels to display, it is indeed concise and beautiful. This article will not repeat the advantages and disadvantages of the interface effect. We mainly focus on the following another interface effect.
2. Interface design based on OutLook style
In fact, the OutLook style has been around for a long time, and it can also be seen in many public control groups. If you only pursue part of the OutLook interface effect, rather than the overall solution, then this open source Outlook component on CodeProject is estimated to be one of them. The standout ( http://www.codeproject.com/Articles/43181/A-Serious-Outlook-Style-Navigation-Pane-Control ). However, since the overall effect is required, and the consistency and aesthetics of more control interface styles must be considered, we still design such an OutLook interface effect based on the DevExpress interface group, which will be more beautiful and elegant. The interface effect is as follows.
By putting many related functional modules of a system into a tree for classification and display, it is also a reasonable layout for a more complex human resource management system or other complex systems. In addition, the OutLook toolbar can still be used. Hide it to save the data display space of the multi-document interface on the right, so that the whole is more reasonable and beautiful. The layout on the right can also be divided into multiple modules by means of SplitContainer, and then the customer wants which data display panel is larger, just drag it, so that when there is a lot of data, the display layout is not good. . Let's introduce how to achieve the above interface layout effect.
1. Create a form based on the DevExpress.XtraEditors.XtraForm base class. as shown in the code below
public partial class MainForm : DevExpress.XtraEditors.XtraForm
{
public MainForm()
{
InitializeComponent();
}
}
2. In the interface design, drag and add a BarManager control to the form in the DevExpress toolbox Navigation & Layout, delete the default toolbar Tools, and add some menu items and status bar data. As follows.
3. Add PanelControl and NavBarControl, and add some test function buttons.
Since we need to use the MDI multi-document interface effect, first set the IsMdiContainer property of Mainform to True.
Then add a PanelControl, set its Dock as the Top layout, set a background image for the control ContentImage (pre-designed with PS, save it in png format), add a few small Labels, and set its pictures and text.
Finally, drag a NavBarControl control into the interface, set its Dock to the Left layout, and enter the design interface through "Run Designer" on the right-click menu of the control. First, add some NavBarGroup and NavBarItem items casually, and the interface effect is as shown below.
Note that in NavBarcontrol, by default, no Panel can add some special controls, such as trees, buttons, etc. By default, only BarItem objects can be added. In order to add such a control in a NavBarGroup, you need to modify the properties of the NavBarGroup, as shown below.
4. Add DockManager and XtraTabbedMdiManager controls to achieve multi-document layout, which will eventually be displayed in Tab mode.
Continue to add the DockManager control and the XTraTabbedMdiManager control to the above form. These two controls can display the multi-document layout in Tab mode on the right side, so that for user operations, multiple forms can be opened for operation at one time, which is very convenient. , will also be beautiful, is a common layout display. In order to display the close button at the top when the form is activated, and the others are not displayed, then you need to set the ClosePageButtonShowMode=InActiveTabPageHeader of the XTraTabbedMdiManager control to achieve this. The final Tab effect is shown below.
The above is the specific operation process of a system interface I designed. In fact, many times, the introduction is always fast, and the exploration is always slow. This is the efficiency improvement of knowledge accumulation. Of course, to design a system interface, in addition to considering the aesthetics of the interface layout, the coordination of icons, and the overall framework, it must be able to better adapt to the operation of these layout controls, and not be too bloated or difficult. read.
After reading it, I didn't quite understand it at first, but after a few tests, I realized the power of dev. I have been engaged in Winform development for many years. Due to the needs of the project, I have designed various interface effects. Generally speaking, by using traditional interface control elements and rationally designing the layout, a relatively standard interface can be designed; using some skinnable controls or some interface components, it is possible to design relatively good-looking interface effects, such as the popular ones in the past. ActiveSkin, IrisSkin and DotNetSkin, etc., which can skin the traditional interface elements, are indeed much better than the standard gray interface controls. However, with the development of interface control components, it is generally preferred to use relatively large control groups. In addition to providing well-designed interface controls, they also provide a variety of colorful interface styles to choose from, such as DotNetBar, netadvantage, DevExpress and other large interface control groups.
No matter how the interface design changes, the general basic principle is to provide customers with interface effects that are intuitive, easy to use, and experience better. From the development of Office, we can also see the overall trend of interface effects, from standard controls to The current Ribbon form, from monochromatic to colorful interface styles, provides us with a good interface design reference, and large interface components also imitate this trend. Closer to home, let's talk about things in detail, currently I tend to use a Ribbon-based interface, and an interface design based on the traditional interface combined with the OutLook style.
1. Interface based on Ribbon style
The above interface style is a relatively elegant interface layout that conforms to the Office interface effect. By focusing different function blocks on different panels to display, it is indeed concise and beautiful. This article will not repeat the advantages and disadvantages of the interface effect. We mainly focus on the following another interface effect.
2. Interface design based on OutLook style
In fact, the OutLook style has been around for a long time, and it can also be seen in many public control groups. If you only pursue part of the OutLook interface effect, rather than the overall solution, then this open source Outlook component on CodeProject is estimated to be one of them. The standout ( http://www.codeproject.com/Articles/43181/A-Serious-Outlook-Style-Navigation-Pane-Control ). However, since the overall effect is required, and the consistency and aesthetics of more control interface styles must be considered, we still design such an OutLook interface effect based on the DevExpress interface group, which will be more beautiful and elegant. The interface effect is as follows.
By putting many related functional modules of a system into a tree for classification and display, it is also a reasonable layout for a more complex human resource management system or other complex systems. In addition, the OutLook toolbar can still be used. Hide it to save the data display space of the multi-document interface on the right, so that the whole is more reasonable and beautiful. The layout on the right can also be divided into multiple modules by means of SplitContainer, and then the customer wants which data display panel is larger, just drag it, so that when there is a lot of data, the display layout is not good. . Let's introduce how to achieve the above interface layout effect.
1. Create a form based on the DevExpress.XtraEditors.XtraForm base class. as shown in the code below
public partial class MainForm : DevExpress.XtraEditors.XtraForm
{
public MainForm()
{
InitializeComponent();
}
}
2. In the interface design, drag and add a BarManager control to the form in the DevExpress toolbox Navigation & Layout, delete the default toolbar Tools, and add some menu items and status bar data. As follows.
3. Add PanelControl and NavBarControl, and add some test function buttons.
Since we need to use the MDI multi-document interface effect, first set the IsMdiContainer property of Mainform to True.
Then add a PanelControl, set its Dock as the Top layout, set a background image for the control ContentImage (pre-designed with PS, save it in png format), add a few small Labels, and set its pictures and text.
Finally, drag a NavBarControl control into the interface, set its Dock to the Left layout, and enter the design interface through "Run Designer" on the right-click menu of the control. First, add some NavBarGroup and NavBarItem items casually, and the interface effect is as shown below.
Note that in NavBarcontrol, by default, no Panel can add some special controls, such as trees, buttons, etc. By default, only BarItem objects can be added. In order to add such a control in a NavBarGroup, you need to modify the properties of the NavBarGroup, as shown below.
4. Add DockManager and XtraTabbedMdiManager controls to achieve multi-document layout, which will eventually be displayed in Tab mode.
Continue to add the DockManager control and the XTraTabbedMdiManager control to the above form. These two controls can display the multi-document layout in Tab mode on the right side, so that for user operations, multiple forms can be opened for operation at one time, which is very convenient. , will also be beautiful, is a common layout display. In order to display the close button at the top when the form is activated, and the others are not displayed, then you need to set the ClosePageButtonShowMode=InActiveTabPageHeader of the XTraTabbedMdiManager control to achieve this. The final Tab effect is shown below.
The above is the specific operation process of a system interface I designed. In fact, many times, the introduction is always fast, and the exploration is always slow. This is the efficiency improvement of knowledge accumulation. Of course, to design a system interface, in addition to considering the aesthetics of the interface layout, the coordination of icons, and the overall framework, it must be able to better adapt to the operation of these layout controls, and not be too bloated or difficult. read.