Revit 2010 - New Ribbon UI

[alan.61903]

AECbytes Newsletter #39 (February 12, 2009)

The article is about Autodesk’s two webcasts to officially launch the next version of its design software portfolio, one focused on AutoCAD and the other on its building, transportation, and geospatial products.

Quoting the article:-

“With version 2010, Revit sports a slightly different look and feel in contrast to the interface the application has had since it was introduced, so existing users will have to go through an adjustment period to get used to it. Instead of the toolbar on the left, Revit now sports the ribbon-based tabbed UI running at the top of the application window that Microsoft has popularized with its Office 2007 applications (see Figure 4).”

The question has to be WHY?

Why not more content and less cosmetic **** that make you feel like your getting more for your money or subscription. There are lots of add ons for those on subscription and who in there right mind would buy Revit without subscription? It’s the only way of getting what should be a full package anyway.

For too long software companies have got away with, “we will fix that in the next release” or "please download the latest service patch” to fix the buggy software we have just sold you.

It’s got to be said, I used Microsoft Word from the start, and recently I had a new computer with Office 2007 and I hate the bloody Ribbon.

Why move everything around from where I knew where it was, my productivity dropped considerably whilst I looked for the new locations of known features.

There are now software companies offering bolt ons to Word 2007 to replace the known interface. In AutoCAD 2009 they at least provided a Classic AutoCAD radio button to get rid of the Ribbon.

Can anyone please confirm that they have done the same in Revit Structure and Architecture 2010?

From one of the 2010 brochures

“Improved User Interface

• New customizable ribbon toolbar is task-oriented with redesigned, intuitive icons.”

You can smell the marketing bull**** from here.

[Wes Macaulay]

The Ribbon is an intelligent response to feature bloat. I would encourage everyone who is opposed to the Ribbon to look at the Microsoft video on why the Ribbon was developed.
http://blogs.msdn.com/jensenh/archiv...he-ribbon.aspx

I think the Ribbon IS a good idea, but it has to be implemented right. Evidently Acad 2010's ribbon is better than 2009's so even the Ribbon we get in Revit 2010 could be improved upon.

The Ribbon isn't marketing balderdash at all -- you have no idea about the thought that went into it. But should they have finished the site tools in this release instead of the Ribbon? Maybe... or maybe getting the Ribbon needed to happen now, because at some point, Windoze users are going to have to come to terms with the Ribbon. I didn't like it either, but the video in the link above made me see why they're doing it. And the Factory might as well get us accustomed to the new era of UI design sooner rather than later.

[PaperStreet SoapCO]

I don't really have a problem with the ribbon per se, but that there are numerous other things that actually effect what I can and cannot do in Revit that should have been addressed first.

[Steve_Stafford]

Well the Ribbon is coming, like it or not. Autodesk is applying it to everything (and it is Revit's turn) they make in an attempt to make their software easier to transition between, collaborate between... a big job and it isn't done. It is the first few steps of many in a larger concept or plan that presenters have been alluding to (without specifics naturally) in various Revit user groups lately.

I'm sure there are aspects of the Ribbon that users will appreciate AND dislike. Sounds like software to me

[alan.61903]

Wes

I downloaded and watched the video,

I can see what you mean about the amount of thought that went into it...... In Word It just makes me feel like I've lost control, and I really don't want that again, just as I'm finding my feet with Revit.

I was one of the first to jump from DOS to Windows, and that did not feel as awkward as the move from menus to ribbon!

Perhaps it's just my age catching up with me?

[Brian Myers]

Originally Posted by Wes Macaulay

I think the Ribbon IS a good idea, but it has to be implemented right. Evidently Acad 2010's ribbon is better than 2009's so even the Ribbon we get in Revit 2010 could be improved upon.

The Ribbon isn't marketing balderdash at all -- you have no idea about the thought that went into it.

Actually, I would argue it is about marketing. Now I'm not stating that it can't be a good idea, it can be, but it's marketing driven. The Ribbon in Revit and Ribbon in ACA will be eerily similar in terms of tools and locations. This is a user benefit move, true, but its also a marketing move to get people to make the transition between programs. That doesn't mean it has to be a bad thing, its simply one of the factors behind choosing to adopt it and making Autodesk product features the standards in the market place.

[dpasa]

The new UI is great and probably helpful, no matter how much time we will have to spend to get used to it...
What is very annoying is that this was already done in ACAD, just "translated" to fit to Revit and advertised as a great improvement, a one year's work.... well, it's not enough for one's year development, because the users wishlist is so long that you will need 10 years and you still won't be finished...
I was very glad to see the new modeling tools but I was also very disappointed to learn that they can be used just for massing....Well, I never use massing tools (almost never) because there are architects before me that decide the final shape of the building....
On the contrary, all these big or small wishes that exist in the wishlist could improve 100% my everyday's work...
So, a very nice UI but nobody needed it...

[fernando]

Originally Posted by dpasa

The new UI is great and probably helpful, no matter how much time we will have to spend to get used to it... So, a very nice UI but nobody needed it...

I desagree about this, the new UI turns very easy to understand, as usual in Revit is very context sensitive, not like the one froms Autocad, that´s a mix of menus and toolbars.

And we need to understand that Autodesk as a goal to achieve a lot of new users that understand very well a UI like this one, generation PS there are a lot of new professional's new ones that grew with internet, games, consoles, phones and are use to interfaces much more user delivered than complex structured menus.

[Liamnacuac]

Originally Posted by fernando

I desagree about this, the new UI turns very easy to understand, as usual in Revit is very context sensitive, not like the one froms Autocad, that´s a mix of menus and toolbars.

And we need to understand that Autodesk as a goal to achieve a lot of new users that understand very well a UI like this one, generation PS there are a lot of new professional's new ones that grew with internet, games, consoles, phones and are use to interfaces much more user delivered than complex structured menus.

Why do we need to understand Autodesk as a goal to achieve understanding? What we need is a usable tool, not a marketing strategy! Maybe they should port their products to Xbox and we can learn to model with a game controller!
I also produce a product, but that product needs to meet the customers' needs. I however, don't have the luxury of market dominance-i have to be highly competitve with what i offer. One way for me to do this, is to reduce my expenses, and I can do that through efficient use of time and tools.
Let's help Autodesk, by letting them know priorities for their next updates, instead of having so many resources working on so many projects. Jack-of-all-trades, master of none??...

[sfaust]

Originally Posted by Liamnacuac

I also produce a product, but that product needs to meet the customers' needs...

True enough, but when was the last time you designed a building for 200,000 unrelated parties? We have enough trouble trying to make people happy designing for a school board & Facilities Management staff, and that's only like 10 or 12 people!