Use the dotnetbar interface control in the cab

Cab provides a very powerful framework structure. After using it, our development habits and code elasticity have been greatly improved. In particular, it provides weak event associations, removing the coupling relationship between modules. However, the workspace provided in the cab is very small. Only the space of tabworkspace, deckworkspace, and so on that can hold smartpart, And the Scalable areas of menustrip, toolstrip, and statusbar are available, you often want to use an excellent interface control and find that there is no way to use it directly in the cab.

Think about it. There are so many excellent interface controls on the Internet. Using the last two on the internet can greatly improve your software experience. On the other hand, using cab and scsf makes development easier to organize and manage. Is there really no way to coordinate the user experience and development difficulty?

P & P's team are not so stupid of course. You can add all these interface elements to the cab framework through expansion, and the expansion is very difficult. Someone must have done similar work. There is one on codeplex, but they do not extend dotnetbar6.9, but another control. So I had to complete the task myself.
Some implementations are implemented, but not all. Here we will first put the devcomponents. dotnetbar. tabcontrol extension, and if someone needs it, then put the others. If you find it through the search engine, you should know how to use it.

Download