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.
So, what this seems to say: Microsoft will allow anybody and everybody to plant their seed (the ribbon UI), to start the viral/grassroots campaign to their way of doing things. Unless and until it conflicts with their existing products.
It's royalty free... translation: Microsoft gets a free ad campaign. But for those who may not be familiar with the company Microsoft, Microsoft is not likely to be friendly about anyone using their UI on any product down the road they decide should be protected.
So are these the dying rattle breaths of a behemoth unable to compete today? Or is it one more salvo (consider Ballmer and his innuendo about Microsoft's Novell-Linux pact) in a war to control even more tightly the computing business world?
Ingenuity is Microsoft's best friend when it comes to fight GPL-licenced products. We are seeing the beginning of that.
You can copy any UI that you want to.
This is just a clear threat to competitors that they're going to be spending millions defending frivolous law suits. Interesting that Microsoft have decided that their business model is now to sue competitors.
Deleted
What does this mean for OpenOffice?
Of course I didn't RTFA, but considering that OO.o is a) multiplatform, b) open source, and c) doing fine as it is, I'd imagine the folks at OO.o will be filing this under D for Don't Give A Shit.
Seriously - would you lose any sleep because MS won't give you a new toy? Even if OO.o wanted it, and even if MS gave them it, they probably couldn't use it because it'll probably be Vista- (or at least Windows-)only.
And seeing as most critics have slammed the new MS Office UI as being generally awful, it's not beyond the realms of possibility that OO.o's similarity to the "old" MS Office UI might pick them up a few users.
C
While I love to sell OO to my friends on the fact that it's so compatible with Office that's the only thing about it's compatibility that I like.
Office for the most part has had a good UI. It has served people well over the years with millions of people getting used to it and being productive with it. Copying the interface and features of Office is a good way to get people to switch (Hey, it's free and it does the same thing, cool!).
But in the end I think all this "we can do that too" mentality ends up stifling free software. While I applaud the efforts of OO and am grateful for it's inclusion in modern distros I would also love to see them wake up one day and deceide they were going to take a "and now for something completely different" approach. Forget chasing the MS UI. Come up with your own, or stick to the one that's in there already and work on optimizing OO's use of resources. Create more filters for different file formats. Expand on the scripting capabilities to make OO a better tool for office automation. The UI is fine the way it is! Tweak it, yeah, but redo it to make it look like MS every few years? Screw that!
I understand why they do it but watching the OO team spend the next few years implementing knock offs of ribbons only to see these supplanted by some new inane concept in Office 2010 just seems like a waste to me.
Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
The license isn't royalty-free if you're building Office-style apps. So I ask, why would anyone want a royalty-free license for the user interface for Office applications (word processor, spreadsheet, database, personal info manager) unless they were building applications that would compete against Office?
Brain explodes.
"There is no night so forlorn, no mood so bleak, that it cannot be infused with pleasure by tender meat..." - R.W. Apple
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.
I hope companies will see this for what it is: An attempt by Microsoft to do with a license trick what they are not able to accomplish with product quality.
There is a social breakdown happening at Microsoft. Bill Gates is, apparently, no longer interested. The company is becoming more and more unable to complete projects.
Microsoft never competed very well on technological merits, but now things are becoming worse. People think that Microsoft has been successful, but the company's success has always depended on tricking customers who don't have much technical knowledge. As customers become more technically knowledgeable, they realize more and more that Microsoft is adversarial.
We who read Slashdot can make a difference. We can explain the issues to everyone we know and meet.
--
Comedy and Tragedy of the Bush administration
"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?"
How about turning that on it's head? "Will the paradigm of an ever-increasing number of features hold up to the reality of having to present them in a UI of some sort?"
I've been using office-style apps heavily since about Office 4, and I haven't seen many new features at all that I consider essential -- *especially* not ones that require adding UI elements to accommodate them. MS's own focus group studies show time and time again that 90% of Office features end up in the "rarely used" category anyway.
I use Office 2007 some, and I'm pretty neutral on the ribbon since I do most tasks via keyboard shortcut anyway. For my money (or lack thereof), let OOo keep its traditional menus & toolbars. Just make keyboard shortcuts consistent across an office suite, get the fundamental features right, minimize the bugs & make the memory & disk footprints as light as you can.
The Ribbon may be da new shiznit and whatnot, and by virtue of MS's market penetration may even end up being the "look" that all others are compared to. Even if that happens, though, I have a hard time seeing *feature bloat* being the driving factor behind what UI paradigm wins out.
Pi Ran Out
I'm glad Microsoft is so innovative, because, you know, shaping a menu and toolbar differently is new, non-obvious, novel, and there is certainly no prior art containing anything similar, certainly not anything preceding it by a decade.
Given the obvious use of technology here and the subjectiveness of what may constitute a ribbon, and how broadly companies like Microsoft tend to paint their patents, I would contend that their "ribbon" is simply taking the Adobe Creative Suite's toolbar scheme that has been around for a decade and simply repainting it to fit in Microsoft Office components. Likewise, one can argue that since context-sensitive toolbars have been around for about 20 years, and buttons in those toolbars have optionally spawned menus when clicked for at least ten years, that there is NOTHING AT ALL new about a Microsoft "ribbon" aside from the artwork, which is covered by COPYRIGHT, not a patent.
The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
"Developers, Developers, Developers" may be a running joke around here, and you may not be a fan of MSDN and the other tool sets, but if you code Windows solutions for pay, fuck you, I'm using them.
I've said it before and I'll say it again. Part of the reason that MS is successful is because there is nobody out there that makes development for their platform as easy as MS. Maybe if some other companies would have somebody screaming about developers and throwing chairs, then those companies would be just as successful in this way. MS gives me tools, and makes it EASY. The OSS community tells me to RTFM. I'll give ya' one guess what I use to develop my business tools.