+1  A: 

IMO, if you're saying that you probably would be specifically denied a license due to the product similarity, proceeding anyway without a license probably isn't going to turn out well for you if Microsoft ever catches wind of it.

I would go with Option 3 to be safe.

rmz
+2  A: 

I realize you say that you don't care about the patents issue, but that's really the only issue. Even if you were to aquire a 3rd party ribbon control, Microsoft has the patents on it and can come after you for violating them. They've explicitly come out and said that people can use it for non-competing products.

The Office UI license restrictions are for the concept of the ribbon, not just MFC's specific implementation of it. See this page for more information.

Eclipse
"Even if you were to aquire a 3rd party ribbon control, Microsoft has the patents on it and can come after you for violating them" - are you sure about that?
demoncodemonkey
There's enough prior art for the ribbon that any such patent Microsoft may have is almost certainly invalid. On the other hand, no one wants to be the test case for that.
Adam Lassek
Adam's right. There were Delphi components doing this years ago.
Matt Olenik
Like Adam said, I sure wouldn't want to be the test case for that.
Eclipse
+1  A: 

I suppose what it really comes down to is whether I'm a direct competitor to MS. Any product can use the ribbon as long as it's not a "competing product", whatever that means.

In the context of my theoretical question, I would certainly be a competitor, and so I'd say it's too risky to use any kind of ribbon.

Of course in real life, whether or not you're a competitor isn't quite so black and white. I'd probably go with Option #2 for any product apart from OpenOffice.


EDIT
I watched this video and here's a quote from the MS lawyer in it:

"The license is not available for applications that have the same primary functionality as the 5 applications that currently have the ribbon in office. That's Word, Excel, Powerpoint, Outlook and Access."

The word primary gives the impression that a product containing a rich-text editor could have a ribbon bar on it, as long as the product's main purpose is different to Word. e.g. a version control system which allowed rich-text comments on checkin, would probably be OK. (I guess)

demoncodemonkey
+1  A: 

Even if you are using a Ribbon from a 3rd party control, isn't it the case that you still have to acquire the license to use it in your application?

Dmitri Nesteruk
Depends on exactly what legal claims Microsoft has. A third-party control would avoid any copyright issues, so the question is (a) what patents Microsoft has, (b) how valid they are, and (c) how many megabucks you want to throw into a court case to upset them.
David Thornley
"(a) what patents Microsoft has" - any ideas how to find this out?
demoncodemonkey
The MS video I watched (see my answer below) seemed to say the major 3rd party ISV's have already signed up for the license. So I guess if you buy a 3rd party control it would already be covered by that company's license. But what about direct Office ripoffs? Maybe not...
demoncodemonkey
+1  A: 

If you're interested in exploring the third party component route, the article on CodeProject that I link below features a ribbon that looks a lot like Microsoft's and is freely available (though you'd have to credit the author).

A Professional Ribbon you will use (Now with orb!)

I haven't tried it but the article is highly rated (FWTW).

Jay Riggs
I tried out the previous version of this control, but I found it was seriously lacking in some of the features of the MFC version. It might be getting there slowly but surely, I'll keep checking it.
demoncodemonkey
A: 

If Microsoft ever decides to come after you, you're dead. Regardless of the merits of the case, you'll be forced to settle just to keep from bleeding to death with lawyers fees. They have much deeper pockets than you do.

And remember that in the U.S. at least, damages for patent infringement are much greater if they can prove you knew about the patent and willfully violated it. Posting in a public forum would be proof enough, I think.

Mark Ransom
What you say is kinda scary but I don't actually "know about the patent" - I haven't even seen any patent. Just something that says they won't give me a license to use the Office UI in my application if it's a competing product. That's completely different to any patent.
demoncodemonkey
Just the fact that people mentioned a possible patent means you could be legally obligated to check it out now. But I'm not a lawyer, so ignore everything I say.
Mark Ransom
:) Yeah I do want to check it out, but I have no idea how.
demoncodemonkey
I really can't help you there, and Microsoft has no obligation to do so either. This is the point where if you're serious, you talk to a lawyer.
Mark Ransom
A: 

Or don't use the Ribbon.

Knowing Microsoft it may not even make an appearance in the next version of Office...

Save your money (and reputation!)

Be creative, but also come up with stuff that your users want. The Ribbon is a design nightmare. Don't make the same mistake!