Showing posts with label Dept. of Questions. Show all posts
Showing posts with label Dept. of Questions. Show all posts

Friday, August 28, 2015

Save Icon Diskette

This is just one of those things that runs through my head as I use and teach others to use Revit. We've been using this icon for Save in most if not all of our software for a long time.


When was the last time we really used one? Does your computer even allow for its use now?

If that's so 1980-90's then what icon would be better for Save these days? A life preserver? I know one product that uses it now, a product called Workspace from Union Square. It looks a bit like these.


If the icon was a $ would people use it more?

Monday, March 02, 2015

Saving Backward

It is a common question and the answer is no, Revit does not save backward, to an older version. 

People often regard saving a file from one format to another as a trivial matter. As software evolves and new features are introduced these new things have no equivalent representation in the older format. Even Microsoft Word or Excel warns us when we save a file to an older version and those are much simpler elements.

For example, when Revit Parts were introduced. If we could save to an older version that did not know what Parts are how should that transition be handled? What should the developers decide to do with them? What can they become and retain some usefulness?

With AutoCAD there are new features that can survive a trip backward, like Tables can be reduced to text and lines so it still looks like a table but is really less elegant than the Tables they came from. If the file is then saved in the most current version there is no "make me back into a table assumption" so fidelity is lost.

It is difficult to allow for forward saving (upgrading) too. Nobody is very pleased if they upgrade a file and something breaks. Saving backward is most assuredly going to break elements the more object oriented our design tools become and evolve.

Revit's founders chose to eliminate the complexity and development distraction of saving backward at the outset. Most software like Revit does too even if they don't acknowledge it outright. They may allow saving backward in concept but there is always some loss of fidelity or utility in the process.

Revit does permit exporting data to other formats to permit it being referenced in some way by other tools but it remains impractical to expect casual backward and forward file translation.

When Revit was introduced in 2000 it was a rental, we paid monthly and internet access was required. Using the latest version was expected, required. That's never changed even when Autodesk purchased Revit Technology Corporation in 2002. They just made it possible to buy a perpetual license like their other software. Conceptually though nothing has changed.

Autodesk has a legacy of customers who transition from AutoCAD where it is normal to ignore a new release for several years before upgrading. That is possible because the rate of change for AutoCAD has generally been much less aggressive than with Revit which is much younger and has different objectives. 

It is easy to have access to the latest version at all times, via subscription. Fwiw Autodesk recently announced that new licenses will soon be all subscription based (rental) going forward so the concept that Revit embraced in 2000 has come full circle.

I'm not always pleased with Autodesk's choices and how they affect me as a customer but no company is perfect. For example, I'm writing this post on an iPad that can't just give me bloody arrow keys (without an external keyboard). Instead I have to use a goofy fussy magnifying glass to reposition the cursor.


Thursday, December 06, 2012

Upgrading and Reloading Families

I overhead a conversation the other day at Autodesk University. One person suggested to the other that we should always upgrade families to the latest release and then reload them all into our project after it has been upgraded. They theorized that Revit was having to "upgrade" them each time we open a project, like the message we see when a linked file is still based on an earlier version. Assuming that is true they went on to say that upgrading the families and reloading them would avoid this repeated upgrading of content when you open a project.

My gut feeling is that is not true after the project is initially upgraded. I believe that the process of upgrading a project is taking into account the content that is part of the project as well. If I'm correct then the content inside the project is effectively upgraded as well. Saving a family out of the project results in a new family based on that version of Revit too, not the previous one.

Only a developer or product designer/manager could say for certain though.

Friday, August 20, 2010

Dept. of Questions - Can Revit?

I've been encountering questions, over the years, where someone asks if "something" is possible. That something is usually quite specific that they do or their firm does. Often it is something we all do or reasonably close. Occasionally it is really specific and perhaps even peculiar to a firm, a person, an off-hand idea...something.

I provide a tongue-in-cheek reply that attempts to get the idea across that Revit is pretty capable and many of the typical things we do have been accounted for. I thought that I should scientifically provide evidence that what I've claimed over the years is true. Here are three pie charts that clearly show what I have claimed all along is true.


Scientifically true? Okay, busted! I didn't do this scientifically. I did use a pie chart in Excel though, does that count for something? Notice how I carefully put Revit MEP at a slightly less percentage of YES? That's because it is younger.

How well does Revit live up to this? Pretty well overall in my opinion. The more specific your focus, the more peculiar or unique your desire the greater the chances you get a small piece of pie. It isn't likely they'll satisfy every last one of us so I don't think they'll ever hit 100% Yes. Regardless, I like pie...Lemon Meringue and Boston Cream Pie (which is a cake, I know). Want some milk with your pie?