Layers are not exactly equivalent to object styles. Although they do more
they also take more overhead to learn and manage. Also they are objects in
their own right.
Xrefs are not that close to worksets. You cannot add any object to any xref
(without changing its location) like you can with worksets.
Display reps are not equivalent to visbility states and detail levels. They
require more overhead to learn, set up and use and again they are objects in
their own right. Visibilty states are properties of objects.
Mvblocks and families are unalike because families are parametric while
mvblocks are not. Closest thing would be styles but again these are
restrictive on parameters and geometry while Revit families are completely
flexible and expandable.
Underlying much of this difference is that Revit is explicitly database
driven while ADT is not. This points to another critical issue for the
future. Revit ,with its clean ODBC export and new API, is well poised to
integrate intelligently with downstream applications while ADT with its
complex object model will require much more effort.
"Matt Dillon" wrote in message
news:4873001@discussion.autodesk.com...
OK, now. In all fairness:
Layers -
Object Styles
xrefs -
worksets
layout tabs, paperspace/model space, viewports -
views and sheets
dimstyles, text styles, table styles, -
dimension types, text/label types
display reps -
visibility states and detail level
multiview blocks -
families
reactors -
and this is a problem where?
Sheet Sets, sheet set manager, AEC Objects, AEC Dimensions, annotations for
each scale, dimensions for each scale, text for each scale, not-so-live
updates of sections and elevations, multiple xref files for multi-story
buildings, Layer Manager, fields -
and now you're just repeating yourself
not parametric -
define parametric. It is parametric, just not in the same way
not bi-directionally associative (cha-ching!) -
true
built on AutoCAD -
some see this as a good thing.
They're both good programs - but you're comparing apples to oranges.