So MS hat geantwortet.
Zitat von
cookie22s Mail an MS:
...Does it mean I can't use 3rd party ribbons in my projects anymore?
Zitat von
Antwort von Microsoft:
You can use any 3rd party control. But the 3rd party ribbon control no longer comes with a special Microsoft license via a separate licensing program involving adherence to Office UI guidelines. Really, this is the very same situation as exists, and has always existed, for any control found in the Windows
SDK - a grid control, a treeview control, a tab control, or any other control. 3rd party controls that emulate those items are not licensed under separate guideline programs either. It is important to recognize that they may be licensed by other means - for example, the 3rd party control may call APIs found in the Windows
SDK.
Since the ribbon control was placed into the Windows 7
SDK, it made no sense to have the older and separate licensing program requiring adherence to guidelines, while the Windows
SDK ribbon license did not require guideline adherence. We wish to treat the ribbon in the same way as the other controls that are also in the Windows
SDK and also in other Microsoft developer frameworks (again - the grid, the tab, the treeview, etc).
Ribbons sind jetzt ganz normale Controls, wie andere auch.
Was übrigens auch interessant ist, ist folgendes.
Zitat von
Antwort von Microsoft:
If, for example, the 3rd party control uses the Windows
SDK, then those 3rd party controls are licensed via the
SDK license. In general, the Windows
SDK and Windows EULA give generous licensing terms to developers calling the APIs, whether directly or via an intermediary (such as a 3rd party control calling Windows APIs).
Damit dürften dann, aus Micosofts Sicht, sowieso fast alle
VCL Komponenten unter die Windows
SDK Lizenz fallen.