CheckBox and ToggleButton
In short, I’ve added support for CheckBox and ToggleButton ribbon controls.
A new sample, named “10-CheckBox” has been added to the project site. The result look like this:
Using CheckBox and ToggleButton – Ribbon Markup
Commands and Views sections:
Using CheckBox and ToggleButton – Code Behind
Connect IUICommandHandler implementation with the helper classes implementations: [If this the first time you see this, you should really check the previous posts..]
Update (18.11.2009): The updated version of the Ribbon class provides an implementation for IUICommandHandler, so the user doesn’t need to implement Execute and UpdateProperty methods anymore.
Get / Set CheckBox status:
Windows Ribbon for WinForms Library Internal Design Issues
Warning: the rest of this post is extremely boring. It discusses internal details of my ribbon library implementation. This doesn’t change anything for the user of the library. Also, it has nothing to do with the checkbox feature.
So now that I’m the only one left, I can discuss some internal details of the library. I’ve just made a major refactoring of the ribbon library.
The ribbon library is composed of:
- Windows Ribbon Framework API wrappers
- Main ribbon class
- Helper classes for different ribbon controls, such as Button, ComboBox, DropDownGallery etc.
In the old version of the RibbonLib, the controls helper classes had lots of duplicated code. For instance, each control that had images attached to it (LargeImage, SmallImage, … properties) needed to handle those images in the same way (manipulating internal variables, notifying the parent ribbon that an image has invalidated etc.). Now, I don’t know about you, but whenever I copy-paste code I always get this strange feeling that something is wrong. So after several sample projects I couldn’t take it anymore and decided to redesign this section.
What I’ve done was encapsulate common code in classes, so they can be reused in several controls without duplicating code.
So now every ribbon control is composed from several properties providers (like ImagePropertiesProvider and TooltipPropertiesProvider) and events providers (like ExeciteEventsProvider and PreviewEventsProvider).
Note: The following sentence is hard, but there is an example right after, so be strong.
Each provider component has its own interface which the using-control also implements by delegating the execution to the component.
For example, I have an ImagePropertiesProvider class that implements the interface IImagePropertiesProvider, which exposes 4 image properties (LargeImage, SmallImage, ..).
In my Button helper class I create a member variable of type ImagePropertiesProvider and make the Button class also implement IImagePropertiesProvider by calling the corresponding methods on the member variable.
This is one of those cases where multiple inheritance was really missing. As a substitute, what I did was used multiple inheritance of interfaces, aggregation and delegation pattern. So the controls still has some duplicated code (the delegation code) but this code is really simple and has no logic in it.
Also, each ribbon control has an Execute and UpdateProperty methods it needs to implement according to the properties and events it exposes. So I’ve made a general implementation which resided in the BaseRibbonControl class that search the implementation of a property or event inside one of the registered providers, thus simplifying this code section in every control (now it doesn’t exists, the simplest way I know).
The results of all these changes are:
- Shorter code with less duplications.
- Developing of new helper classes is extremely simple.
- Cool class diagrams..
Properties Providers Class Diagram
Events Providers Class Diagram
Ribbon Controls Class Diagram
That’s it for now,