What do now winform procedure, the use of framework or the third party tools?
One is the need to keep the style of each list and edit interface unification, relatively beautiful,
Another is easy to expand,

CodePudding user response:

DevExpress

CodePudding user response:

The eldest brother dotnetbar calculate

CodePudding user response:

In.net and vs enough under the condition of production efficiency, it is not necessary to put complicated problem is many times, the main is exactly have on person, exactly grasp how much? !

I have seen many projects in the loss of millions of yuan, many are "know money will skip stone" in a variety of tools debate, just because want to solve the problem of infighting, and regardless of the development efficiency,

CodePudding user response:

Convenient extension is the cost of flexibility, not how to extend to play rascal "convenient extension" belong to

CodePudding user response:

It is more excellent under winform dev... But it's too fat..

We do not deny that powerful. But is the true card...

CodePudding user response:

Telerik

CodePudding user response:

refer to fifth floor by_ love reply:

dev is indeed under winform is good... But it's too fat..

We do not deny that powerful. But is the true card...

How did in dev keep each list and edit interface style is unified, use the method of inheriting parent form? A relevant example,

CodePudding user response:

refer to 7th floor weisai response:

Quote: refer to fifth floor by_ love reply:

It is more excellent under winform dev... But it's too fat..

We do not deny that powerful. But is the true card...

How did in dev keep each list and edit interface style is unified, use the method of inheriting parent form? Have a relevant example,

Dev has a theme

CodePudding user response:

1 a unified style
This is very simple, use of third party default styles, how are unified,
2 easy extensibility
The extension you said is what's
Three commercial/free, baidu once, you really not line, also can consider WPF

CodePudding user response:

refer to the eighth floor Summer_djz response:

Quote: refer to 7th floor weisai response:

Quote: refer to fifth floor by_ love reply:

It is more excellent under winform dev... But it's too fat..

We do not deny that powerful. But is the true card...

How did in dev keep each list and edit interface style is unified, use the method of inheriting parent form? Have a relevant example,

Dev has a theme

Need to be more specific, such as editing interface location toolbar, style; Save, print button icon, location, etc.,
Can't every form to draw again for me, specific what method?

CodePudding user response:

references are anger, 9/f, in god's response:

1 a unified style
This is very simple, use of third party default styles, how are unified,
2 easy extensibility
The extension you said is what's
Three commercial/free, baidu once, you really not line, also can consider WPF

Need to be more specific, such as editing interface location toolbar, style; Save, print button icon, location, etc.,
Can't every form to draw again for me, specific what method?

CodePudding user response:

11 references weisai response:

Quote: reference is anger, 9/f, god reply:

1 a unified style
This is very simple, use of third party default styles, how are unified,
2 easy extensibility
The extension you said is what's
Three commercial/free, baidu once, you really not line, also can consider WPF

Need to be more specific, such as editing interface location toolbar, style; Save, print button icon, location, etc.,
Can't every form to draw again for me, specific what method?

You can do it directly userControl,
Then entrust each button events,

This generally don't have to paint, the family controls the basic have a button, you are responsible for it is good to show or hide,

CodePudding user response:

references to the tenth floor weisai response:

Quote: refer to the eighth floor Summer_djz response:

Quote: refer to 7th floor weisai response:

Quote: refer to fifth floor by_ love reply:

It is more excellent under winform dev... But it's too fat..

We do not deny that powerful. But is the true card...

How did in dev keep each list and edit interface style is unified, use the method of inheriting parent form? Have a relevant example,

Dev has a theme

Need to be more specific, such as editing interface location toolbar, style; Save, print button icon, location, etc.,
Can't every form to draw again for me, specific what method?

Toolbar menu bar or something just don't have to move in the main interface, the other is on the main interface of the container, the switch is the inside of the main interface easy things
There are some public interface is made custom controls

CodePudding user response:

In a post, how can the specific? Post, also means a road, the road still have to go,
Devexpress the entire document, always can't give you move to a post? It is best to see,
https://docs.devexpress.com/

And Telerik optional, simple point, is the dotnetbar,

If you don't have the patience, may still dotnetbar is suitable for you, because it is the most simple,

CodePudding user response:

refer to 12th floor is nu month god reply:

Quote: reference 11 floor weisai response:

Quote: references 9 floor is nu month god reply:

1 a unified style
This is very simple, use of third party default styles, how are unified,
2 easy extensibility
The extension you said is what's
Three commercial/free, baidu once, you really not line, also can consider WPF

Need to be more specific, such as editing interface location toolbar, style; Save, print button icon, location, etc.,
Can't every form to draw again for me, specific what method?

You can do it directly userControl,
Then entrust each button events,

This generally don't have to paint, the family controls the basic have a button, you are responsible for it is good to show or hide,

It is as you say, such as editing interface in the toolbar, to make a custom control? Or edit interface parent form, the toolbar design good, other forms inherit the parent form?