New framework needed: Object Types

[Christiaan]

I started this thread back in 2007 asking for a different way to edit similar plugin objects in one go:

http://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Number=77220

What we need is a new framework that allows us to group plugin objects into Types based on common parameters that we define (while allowing other parameters to vary) so we can schedule them and edit them en masse, without having to resort to the sledgehammer that is the Symbol.

The most ripe objects for this treatment are windows/doors, given that grouping them into types has long been common drafting practice.

The 3rd party plugin Info Editor takes a shot at dealing with this issue but it only scratches the surface. We need to be able to work visually with objects rather than tabular data.

For instance object Types should reside in the Resource Browser. When editing them we need some sort of visual feedback letting us know the location of all the instances we're about to edit.

We should be able to create visual window/door schedules that include an elevation of the window/door.

We should be able to define Wall Types so that we can make minor variations to wall linings without the need to create an entirely new wall.

[Chris D]

I missed this in 2007, but count me in.

I was idly musing the same thing earlier after the discussion about window/door types.

[Chris D]

To extend the discussion a little further:

I think here lies the way to less abstraction too. If there was a generic 'parametric element' PIO that were customisable to the extent that you can create whole new building components that were nameable, scheduleable, parametric, etc, there would be less overhead for the NVInc engineers, as we could create components and elements and share them. The Object Info palette and the Worksheets would report them directly as building components. This might be a bit open ended, but some of the technology is already there....i'm thinking semi useless tools like the linear material tool, as well as the door/window tools and the wall tools - they all have generic behaviours which could be repurposed - linearity, repeating units, hole forming, joining behaviours, limits, associations, etc.

Where Types then come in handy is that if this was an available function of all PIOs, then any new parametric element created could be used by Type, which would be extremely powerful.

[Stan Rostas]

In Revit (Families) are the same as VW symbols that have PIO within them. In ArchiCAD (Library Objects) are the same as VW symbols. The difference being the method by which to view and or manipulate these object types. Interface for editing in all is lacking. In 2012 VW the user can edit in place in relation to other objects.

Chris, your last point is a recurring request by our office that would expand the objects we can create greatly.

[AndiACD]

Excellent suggestion Chris D.

NAG would be very unlikely to comply though as it might take their "Module Selling Power" away from them. They'd be pushed into a Designer only based product which probably gives them their edge.

Love the idea though . . . . .