Let's build and place an object model chart in our Idea Exchange, like this one for Inventor:
Also usefull describe charts for client applications: describe GUI and internal scheme (including links to Vault dll's):
Using this scheme we can see what are we missing, check collisions, and others.
I tried creating some sort of class diagrams for the Vault API a few years back. Unfortunately, the structure of the Vault API doesn't lend itself to these types of diagrams very well. Most of the API consists of function calls and independant objects. It's not an OO class heiarchy like with the Inventor API.
Anyway, take a look at the diagrams for yourself. Personally, I didn't find them useful, and I haven't heard of anyone else finding them useful. If you know a way to improve things, I'm open to suggestions.
This is exactly what I was looking for! Some time later I'll try to show you what's useful in this chart. Be patient.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Share and shape product ideas.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Upgrading to a 2015 product? Make sure to check these out 1st!