Matt Overton Posted March 21, 2024 Share Posted March 21, 2024 To avoid redundancy and other management problems, Library files should not be in a specific version of the file format. They should be able to deliver the resource to the version of the app that being used regardless of what version of app saved the resource saved it. Given that most resources are fairly small objects anyway, any background data conversion that happens to get it to work would be quick. Benefits- - One True single library (per user or company-wide) - Smaller Install, smaller footprint - less management - Set and forget each version wouldn't need new locations to be set so could just read the settings from prior install. 3 Quote Link to comment
0 zoomer Posted March 21, 2024 Share Posted March 21, 2024 Better whole VW Files should be universal. Like DGN (or even DWG - although having versions !) OK, if you are using latest IFC features that an older version did not support it may be a bit lossy in exchange. Such things can happen even in Blender. Just a warning, that saving could lead to some data loss but being able to open a file and show its geometry and data would help a lot. I also keep 3-4 Workgroup Library Duplicates on disk. Basically untouched since 8 years. Just that I migrate a copy each September .... Quote Link to comment
0 Matt Overton Posted March 21, 2024 Author Share Posted March 21, 2024 Yes, Universal Vectorworks files would be great and it was put forward several times over the years as the reason for .vwx file change. Still as a show of progress and to improve the usability of the Libraries, it would be a good test bed. At a per-type level how many of the types have changed dramatically over the years? Lots of objects have got a revamp but at the same time, they moved from Red Symbols being stored in the library to Object Styles Types. The code to do the conversation if they are needed would exist, Sure doing the conversion each year isn't much work but it seems it is enough to mean people just don't use the system. 1 Quote Link to comment
Question
Matt Overton
To avoid redundancy and other management problems, Library files should not be in a specific version of the file format.
They should be able to deliver the resource to the version of the app that being used regardless of what version of app saved the resource saved it.
Given that most resources are fairly small objects anyway, any background data conversion that happens to get it to work would be quick.
Benefits-
- One True single library (per user or company-wide)
- Smaller Install, smaller footprint
- less management
- Set and forget each version wouldn't need new locations to be set so could just read the settings from prior install.
Link to comment
2 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.