NO! NO! YOU ARE WRONG!!!
Just kidding....
We all use different workflows, and using clones has worked for me like a charm.
I agree with you that sometimes clones give you a lot of views that won't be used, but I'd usually need the views inside a cloned folder with the same options. If I create four section viewpoints, when placed on layout I try to use the same options for each (that's why I prefer to clone) and not different options (scale, layers, etc.) for
each
section. For instance, if I'm layout
ing
sections at 1:100, I'd clone "Sections" and
name the clone
(not the individual views) "Sections 1:100". If I then need one or two of those at a different scale, I'd do the same, and name the clone "Sections 1:50".
The base name of each viewpoint is taken care at the project map (section 1-1, section 2-2). If a view, inside a clone is to be renamed it's because it will be used several times in layouts (one could use the custom name in layout, but it would be an instance name; changing the name in the view map, would change the name in all placed instances). So in the end, there's little need for renaming views. The only thing to name accurately is the cloned folder, to keep track of basic options that it stores.
Clones also give me the advantage that when I move to a different phase in the project, I can easily ctrl-drag the cloned folder in the view map (to a different, regular folder) and quickly change options like layer combo, model view options, scale etc, and prepare a new set of plans or sections by again ctrl-dragging sets of layouts and linking to the new cloned views.
I could copy the clones for "design" process "Sections 1:100" and "Sections 1:50" that had "presentation layer combo" and put the new clones in a "construction" folder, change layer combo to "construction phase", and relink new layouts to the new clones.
For me, creating manual views for each viewpoint in the project map to be used like this would need more time, and a lot of attention to manage settings when saving each view.
I rarely publish views. I usually publish the layouts; but I guess its the same. While you can rename the views in the publisher set, I never do this, as, like you said, it's error prone. I always create the
shortcut
(not drag in view organizer) to the set or subset of layouts. Rename the layout, the publisher linked view gets renamed. Same thing for views, I guess. With the shorcut, published views/layouts are always complete, and with correct names.
Didn't quite follow you with the
"Consider if we could clone actual view maps! No renaming needed!" thing...
In the end, like I said, is a personal thing.
Best regards.