Alfred Van Hoek wrote:
Don't know exactly what the problem is. The plugin format is
determined by RS, and has been published. All you need to do is to
encapsulate the folder hierarchy into a virtual volume. Some
people do it from the command line, others create a small app to
do so.
This discussion is not about the RBX virtual volume format itself,
it is about standardizing the version information so end users can
manage their plugins.
Some developers mentioned they want to go from a vers resource to
the new format. So something has to be written to do this with the
end purpose in mind that we want them to get on board and support
a common version format. The more people that support it, the more
successful it will be.
I agree this is a really simple thing to do for most developers,
but the real answer is it depends on what kind of build
environment that each developer has set up.
With respect to the version info, the format was given here on
this list. All you need to do is to put this text file at the root
of vv.root.
True, but there needs to be a consensus if this going to work.
This also need to be brought to the attention of the plugin
authors which is what I am trying to accomplish here.
Likewise you can make a converter to convert from a vv to real
folders if you want to investigate .rbx volumes.
So the infrastructure is defined by RS, not by Björn, not by me,
nor by other third parties.
The focus of my discussion is not the virtual volumn structure of
the RBX format , but how to store version information in the RBX
file so that we can create tools for the end user to manage their
plugins.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|