Want to use the Ribbon in your app? Here, sign this.
-
It makes sense, I guess - it's just that they've never done it before. I've seen at least a half-dozen component vendors hawking Office 2007-style UI elements and I'm sure more are on the way. But if you want to use them in your application, you'll need to agree to Microsoft's new license and use their guidelines. http://msdn2.microsoft.com/en-us/office/aa973809.aspx[^]
if(!curlies){ return; }
I find the wording and license talk surprisingly refreshing from MS's typical restrictive junk. Surprisingly frank as well:
Can any applications use the license? The license is available for applications on any platform, except for applications that compete directly with the five Office applications that currently have the new UI (Microsoft Word, Excel, PowerPoint, Outlook, and Access). We wanted to make the IP available broadly to partners because it has benefits to Microsoft and the Office Ecosystem. At the same time, we wanted to preserve the uniqueness of the Office UI for the core Office productivity applications.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: God-as-Judge, God-as-Forgiver The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
yeah I figured, but....the only way I can see that happening is that they either give the source code (which they don't), or its a .Net assembly, which will run under Mono on linux, yes. But I'd think its a native library, not a .Net assembly. How they intend to linuxify it then, is beyond me.
:badger:
It's not a library at all. It's the design for their UI. The idea being, you can use the design to implement your own OfficeUI work-alike. Of course, the license prohibits developing any apps with this UI that compete with MS-Office... My take is this: it's good that Microsoft-the-maker-of-Office is doing this. Lots of 3rd-party programs try to look and act like the various Office apps, and this could help them do a better job of it. If only Microsoft-the-maker-of-Windows had such a focus on usability...
---- I just want you to be happy; That's my only little wish...
-
It's not a library at all. It's the design for their UI. The idea being, you can use the design to implement your own OfficeUI work-alike. Of course, the license prohibits developing any apps with this UI that compete with MS-Office... My take is this: it's good that Microsoft-the-maker-of-Office is doing this. Lots of 3rd-party programs try to look and act like the various Office apps, and this could help them do a better job of it. If only Microsoft-the-maker-of-Windows had such a focus on usability...
---- I just want you to be happy; That's my only little wish...
Shog9 wrote:
you can use the design to implement your own OfficeUI work-alike.
I'm pretty sure I could do that before this license too. or are they now prohibiting those without a license to copy their UI look? I guess it makes sense then, and I can then finally see the true reason for this - to show teh world how popular the new UI is.
:badger:
-
Blast! And I thought they were making public their Office UI source code :->
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. (*Sample chapter available online*)Nishant Sivakumar wrote:
Blast! And I thought they were making public their Office UI source code
:) No such luck, but word is that they're thinking about whether to do a version that would ship with Visual Studio. I wonder how that makes the current crop of 3rd party vendors feel.
if(!curlies){ return; }
-
It makes sense, I guess - it's just that they've never done it before. I've seen at least a half-dozen component vendors hawking Office 2007-style UI elements and I'm sure more are on the way. But if you want to use them in your application, you'll need to agree to Microsoft's new license and use their guidelines. http://msdn2.microsoft.com/en-us/office/aa973809.aspx[^]
if(!curlies){ return; }
-
Shog9 wrote:
you can use the design to implement your own OfficeUI work-alike.
I'm pretty sure I could do that before this license too. or are they now prohibiting those without a license to copy their UI look? I guess it makes sense then, and I can then finally see the true reason for this - to show teh world how popular the new UI is.
:badger:
Anton Afanasyev wrote:
or are they now prohibiting those without a license to copy their UI look?
The license's existence would be pretty pointless if this weren't the case. Who knows if anything would ever come of it, but I don't think going outside the license would be worth the legal risk. All they're asking is that you don't do some kind of half-assed job that makes their UI concepts look bad.
if(!curlies){ return; }
-
I'm at least 80 percent certain the real reason behind this is to stop direct competitors from making clones of Office applications. Their spinning it to something else of course.
So you're not holding your breath for OpenOffice featuring the Ribbon? ;P
if(!curlies){ return; }
-
Shog9 wrote:
you can use the design to implement your own OfficeUI work-alike.
I'm pretty sure I could do that before this license too. or are they now prohibiting those without a license to copy their UI look? I guess it makes sense then, and I can then finally see the true reason for this - to show teh world how popular the new UI is.
:badger:
You're still not getting it. This Ribbon thing isn't a toolbar. It's waay more complex. And once it's been out in the field for a while, users are gonna expect things that look like it to also work like it. Now, Charlie posted this a bit early - MS doesn't actually have links to either their license or their design guidelines. But, eventually they will. And then, upon agreeing to the license, you can use the guidelines to develop a Ribbon that actually works like the Ribbon in Word. Or Excel. Or Whatever. The point being, you won't confuse and frighten your users with a Ribbon that's actually working like a plain old Toolbar. That is, assuming the license is pretty much in line with the Q&A answers on that page. For all i know, it also requires a pledge of your first-born, a pint of blood, and promises a slow and painful death to all who defy it. But we'll just have to wait and see...
---- I just want you to be happy; That's my only little wish...
-
Anton Afanasyev wrote:
or are they now prohibiting those without a license to copy their UI look?
The license's existence would be pretty pointless if this weren't the case. Who knows if anything would ever come of it, but I don't think going outside the license would be worth the legal risk. All they're asking is that you don't do some kind of half-assed job that makes their UI concepts look bad.
if(!curlies){ return; }
no..yeah of course I understand that. I wasn't planning to make my own version(too much work ;P). But using component like those from DevComponents, I could already do that without this license. The license just makes them safe from those who'd want to roll theyre own and screw up real bad I guess. meh. Hrm, on a different note, would I need the license to use controls like from DevComponents? I'd think not, if I dont have the sources. Ideas?
:badger:
-
So you're not holding your breath for OpenOffice featuring the Ribbon? ;P
if(!curlies){ return; }
New in OpenOffice - The Bow! ;)
---- I just want you to be happy; That's my only little wish...
-
You're still not getting it. This Ribbon thing isn't a toolbar. It's waay more complex. And once it's been out in the field for a while, users are gonna expect things that look like it to also work like it. Now, Charlie posted this a bit early - MS doesn't actually have links to either their license or their design guidelines. But, eventually they will. And then, upon agreeing to the license, you can use the guidelines to develop a Ribbon that actually works like the Ribbon in Word. Or Excel. Or Whatever. The point being, you won't confuse and frighten your users with a Ribbon that's actually working like a plain old Toolbar. That is, assuming the license is pretty much in line with the Q&A answers on that page. For all i know, it also requires a pledge of your first-born, a pint of blood, and promises a slow and painful death to all who defy it. But we'll just have to wait and see...
---- I just want you to be happy; That's my only little wish...
Shog9 wrote:
you won't confuse and frighten your users with a Ribbon
Are you implying I can't program?;P
:badger:
-
New in OpenOffice - The Bow! ;)
---- I just want you to be happy; That's my only little wish...
Next up will be The Tie:laugh:
:badger:
-
Next up will be The Tie:laugh:
:badger:
I've already patented the bow tie. :-)
Tech, life, family, faith: Give me a visit. I'm currently blogging about: God-as-Judge, God-as-Forgiver The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
It makes sense, I guess - it's just that they've never done it before. I've seen at least a half-dozen component vendors hawking Office 2007-style UI elements and I'm sure more are on the way. But if you want to use them in your application, you'll need to agree to Microsoft's new license and use their guidelines. http://msdn2.microsoft.com/en-us/office/aa973809.aspx[^]
if(!curlies){ return; }
What ever happened to Lotus 1-2-3 anyway...
- S 50 cups of coffee and you know it's on!
-
What ever happened to Lotus 1-2-3 anyway...
- S 50 cups of coffee and you know it's on!
Steve Echols wrote:
What ever happened to Lotus 1-2-3 anyway...
Wiki indicates it was ultimately rolled into Smart Suite. If it’s anything like Lotus Notes then it’s a steaming pile of dung. Lotus 1-2-3[^] IBM Lotus SmartSuite[^]
I'd love to help, but unfortunatley I have prior commitments monitoring the length of my grass. :Andrew Bleakley:
-
Nishant Sivakumar wrote:
Blast! And I thought they were making public their Office UI source code
:) No such luck, but word is that they're thinking about whether to do a version that would ship with Visual Studio. I wonder how that makes the current crop of 3rd party vendors feel.
if(!curlies){ return; }
Charlie Williams wrote:
but word is that they're thinking about whether to do a version that would ship with Visual Studio. I wonder how that makes the current crop of 3rd party vendors feel.
Orcas time frame?
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. (*Sample chapter available online*) -
It makes sense, I guess - it's just that they've never done it before. I've seen at least a half-dozen component vendors hawking Office 2007-style UI elements and I'm sure more are on the way. But if you want to use them in your application, you'll need to agree to Microsoft's new license and use their guidelines. http://msdn2.microsoft.com/en-us/office/aa973809.aspx[^]
if(!curlies){ return; }
Die blast ribbon, die!
-
Die blast ribbon, die!
Have you actually used it? I have and I think it's wicked awesome!
if(!curlies){ return; }
-
It makes sense, I guess - it's just that they've never done it before. I've seen at least a half-dozen component vendors hawking Office 2007-style UI elements and I'm sure more are on the way. But if you want to use them in your application, you'll need to agree to Microsoft's new license and use their guidelines. http://msdn2.microsoft.com/en-us/office/aa973809.aspx[^]
if(!curlies){ return; }
This thread is strange because everyone is so accepting of this "licence". You can't patent or copyright UI. Anyone remember Lotus v Microsoft where Lotus went after Microsoft because Excel "stole" its look-and-feel? Lotus lost in part because the whole of the windowing UI concept is predicated on work done by Xerox years ago and because the principle of the spreadsheet was not novel. In my opinion the ribbon is not novel it's an adaptation of the rebar but consumes more screen real estate. Suppose someone asked you to agree to their licence for the air guitar or a set of the emporers new clothes. You wouldn't sign up would you. You would be especially incredulous if they then stipulated that you were not allowed to use the air guitar in the pub or while wearing jeans. However, if you did sign up, voluntarily as an adult, then you could be held to the agreement. So think of this as being an air guitar and ask yourself whether you would still sign up or be enthusistic about it. Without doubt it is great that Microsoft publish guidelines and of course the guidelines themselves are subject to copyright. But the fact that they spent a lot of time thinking about UI does not give them a right to any exclusivity. If they wanted that exclusivity they should have covered that with each of us individually *before* the release the first versions of Office 2007 and has us sign our lives away. But they didn't and that UI is in the public domain.
-
no..yeah of course I understand that. I wasn't planning to make my own version(too much work ;P). But using component like those from DevComponents, I could already do that without this license. The license just makes them safe from those who'd want to roll theyre own and screw up real bad I guess. meh. Hrm, on a different note, would I need the license to use controls like from DevComponents? I'd think not, if I dont have the sources. Ideas?
:badger:
Anton Afanasyev wrote:
Hrm, on a different note, would I need the license to use controls like from DevComponents? I'd think not, if I dont have the sources. Ideas?
According to Microsoft's Chris Bryant (from Jensen Harris' blog[^]), you need to agree to the license even if you're using a 3rd party control. The license doesn't pass through from DevComponents to you. A lot of people seem to be questioning the legitimacy and/or enforceability of this type of license, though. If it were me, I'd probably sign the darn thing and let someone with deeper pockets than me worry about whether it has any teeth.
if(!curlies){ return; }
