Office 2007 UI License
MikeWeller writes, "Microsoft has recently announced a new licensing program for the Office 2007 user interface. This page links to the license and an MSDN Channel9 interview about the program (featuring a lawyer). The program 'allows virtually anyone to obtain a royalty-free license to use the new Office UI in a software product. There's only one limitation: if you are building a program which directly competes with Word, Excel, PowerPoint, Outlook, or Access (the Microsoft applications with the new UI), you can't obtain the royalty-free license.' What does this mean for OpenOffice? Will traditional menus/toolbars hold up to an ever-increasing number of features, or will OO be forced to take on a new UI paradigm? With the gap between OO and MS Office widening, how is this going to affect users trying to move between the two platforms?" You need to sign the license before you can get the 120-page UI implementation guidelines, which are confidential.
the funny thing is that Quanta+ in KDE has had a similar UI with a ribbon for years now:g n g
http://quanta.kdewebdev.org/screenshots//shot2.pn
http://quanta.kdewebdev.org/screenshots//shot13.p
Do they need a license too?
download and burn linux with one click on windows
Well, obviously, X has *NO* consistency because it has no standard widgets. Windows has. WINAPI contains buttons, sliders, scrollbars, text edits, menus etc. So the *base* for consistency is there, which cannot be said for X.
...) Very little programs create their own widgets from the ground up. In X, Qt does everything from scratch, just like GTK, FOX, Athena, Motif, etc. The important thing is that their behaviour is not fully consistent. Aside from funny Office/IE widgets, I can reuse my knowledge with one Windows GUI when using another. Most Windows apps do NOT use custom widgets.
But MS violate their own standards by creating custom widgets for Office and IE. This is something widely criticized by UI designers.
However, usually the WinAPI widgets are the core of Windows GUIs (tweaked buttons, menus
However, nowadays GTK and Qt have little custom quirks of this sort. Their differences are mostly optical (but it is a visual inconsistency when 90% of all apps are Qt/KDE-based and only one program uses GTK). However, the presence of two major TKs is a problem because distros tend to choose only one of these two. In this case you end up with a dependency that may be big enough to turn users and more importantly distro makers away (like "oh no, my system is purely GTK-based, I dont want Qt anywhere").
This sig does not contain any SCO code.
Nope, nothing to do with the library. It's the User Interface they're licensing.
From the announcement:
"For those that want to build their own UI that takes advantage of our design guidelines, they will need a license."
Deleted