Hi David Dorst,
Thanks for the writing.
From a purely technical point of view, yes, you should use RadRibbonBar as specified in the guidelines, because the control is designed to handle the described cases. However, the guidelines are not strict laws that you have to obey. They provide important information about the design of RadRibbonBar which you should have in mind when you are customizing your instance.
Let me illustrate this with an example. Many of our customers would like to have a RadRibbonBar with a height of 200 px, while the guidelines state that, for example, the height should be no more than 100 px. Since the control is not designed to be that high, there might appear visual glitches, wrong layout or unexpected behavior. In this case our clients are certain that they are experiencing a bug of RadRibbonBar, even though it is not.
The particular reason we sent you the guidelines is to support our argument that you should avoid nesting composite input controls like calendars, grids, schedulers in a RadRibbonBar and keep the user interface as simple as possible. However, the explanations you have provided afterwards implied that you are already familiar with this control and well informed about its design.
I hope you find my answer helpful. Let me know if you have further questions.
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items