[Logo] VUE Users Forum
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Groups] Back to home page 
[Login] Login 
If this is your first visit to the new VUE forums, you can login using the same username and password you currently use on VUE's website. If you need an account, please create one through VUE's website. If you have problems, please contact us via the contact form on http://vue.tufts.edu
altenative to nesting vpk files  XML
Forum Index » Wish List
Author Message
Rich Rath


Joined: 08/08/2008 11:36:13
Messages: 12
Offline

In VPK files, I would like to see an option for having any links to vue or vpk files be external to the vpk rather than mashed in, with the external files linked relatively, perhaps with a requirement that they be in the same folder as the parent. That way, the small chunks could be maintained without opening up everything. Relative paths, with perhaps a "same folder" requirement would allow partability to be maintained. The option could be either in prefs or as a checkbox in the save dialog.

As it stands now, an edited nested vpk child map does not update in the master vpk and the changes get lost. see https://vue-forums.uit.tufts.edu/posts/list/0/1172.page#4557.
Valentine Cadieux


Joined: 01/07/2011 09:38:58
Messages: 5
Offline

Yes! The VPK format is currently a bit of a rabbithole -- we use it in order to keep things sharable, but it's very hard to work with the relative links when you move the packages around. Is there a way, for example, to specify that everything is a relative location, rather than have absolute links? And to be able to figure out when something is internally linked ("in the package", and is there a way to make it automatically update?), vs. just an external file that needs to be transported along with the package?

Also, it would be great to get clearer instructions about the implications of transforming from VPK into HTML (e.g. how to get all the layers to export, and remain linked?)
 
Forum Index » Wish List
Go to:   
Powered by JForum 2.1.8 © JForum Team