[Info] Why multiple ribbon frameworks?

Mar 23, 2010 at 6:04 PM

Windows 7 has one.

Office 2010 has one.

SharePoint 2010 has one.

Why are there do so many? Which one is going to win?  Office 2010 seems to be the leader because it includes a designer in Visual Studio but it is only useful for extending Office ribbons.


Mar 23, 2010 at 6:14 PM

Correction: Microsoft has 4 competing Ribbon XML schemas: the 4th is WPF/XAML.

Why are there do so many? Which one is going to win?

Mar 23, 2010 at 11:01 PM

Actually you forgot another Ribbon, the MFC version.

There is no competition between them because each ribbon has it on purpose and users and provides a familiar programming experience for their users.

WPF provides a ribbon with XAML syntax and other WPF properties.
MFC version provides a ribbon that uses the familiar MFC object model.
Office ribbon is useful only for office add-on.
Windows 7 is used by native win32 developers and WinForms developers (using my wrapper library)
I didn't heard about SharePoint Ribbon, but I assume it has its own benefits.

Hopefully, this clarifies the mess.

Mar 27, 2010 at 1:07 AM

The need for multiple implementations is obvious ...the need for multiple XML scehmas is not.