PawPrint.net Forum

I have been using VersaVerter for quite some time, through several versions, and am routinely in the habit of customising it - drastically!
It has always served me very well, and it has always been a simple matter to "cut" the units.xml file to suit my needs for several smaller, specialised conversion Applications. - I create several VV Folders; VV-Scientific, VV-Engineering, VV-Domestic etc., renaming the executable as appropriate and cutting the units.xml file down to include ONLY those units which I require in each. Any additional units which I might require are readily added, and the (IMHO) superfluous yotta, zetta, exa and peta prefixes, along with the superfluous (again, IMHO), hecto, deci, femto, atto, zepto and yocto prefixes are removed to make the unit-sets more "real world". Of course, I maintain one copy in its pristine "as downloaded" state, and use that for the online updates, promulgating any required changes as I might need.
Of course, this might seem like a whole lot of work for "just a converter", but it sure makes my life easier to be able to pop up a converter specifically tailored to my needs.
For this functionality above all else, you should be congratulated; it makes VersaVerter an extremely flexible, and therefore, extremely useful part of my Desktop Toolkit. Shortcuts placed into the Quick Launch Folder ensure that my VersaVerter set is always close at hand.

The only operating Bugs I have observed are:
(Currently using VersaVerter 3.0.0.178 with Unit Base 2.2.1.0.)

Upon EXPORT XML, Versaverter SPLITS

<vv:description lang="en">DESCRIPTION</vv:description>

to:

<vv:description lang="en">DESCRIPTION
</vv:description>

and creates:

<vv:baseunit type="factor"><vv:symbol>Symbol</vv:symbol><vv:name type="SI">Unit Name</vv:name><vv:convert-from>1</vv:convert-from></vv:baseunit>
<vv:unit type="factor"><vv:symbol>Symbol</vv:symbol><vv:name type="SI">Unit Name</vv:name><vv:convert-from>1</vv:convert-from></vv:unit>

instead of:

<vv:baseunit type="factor"><vv:symbol>Symbol</vv:symbol><vv:name type="SI">Unit Name</vv:name><vv:convert-from>1</vv:convert-from></vv:baseunit>

Thus causing DUAL ENTRIES for the BASEUNIT!

The first anomaly is mentioned only for its proximity to the second - the two may be the result of the same internal logic error.

Hand correction of this, and IMPORT XML "cures" the appearance of dual entries.

To be quite honest, I have forgotten if this behaviour was evident in earlier Versions, as I used to just automatically manually edit the units.xml file to suit my needs. It has only been since reading the Posts on the Support Forum, that I have closely examined the behaviour, and come to realise that the following modification(s) may be suitable to make VersaVerter more useful for others:

1) Split the units.xml file into seperate files for each Class.
2) Allow class.xml files to reside in Group Folders.
3) Utilise the existing units.xml currency check to detect altered / new xml file(s) within the selected Group Folder, and (re)generate the ubase.vvd file for THAT particular Folder.
4) Load VersaVerter with the MRU Group set of generated ubase.vvd file.
5) Allow the User to switch the loaded Group ubase.vvd at will.

For example, dividing the Classes into the following Groups:

DOMESTIC (17 Classes)
"Acceleration"
"Angle"
"Angular Velocity"
"Area"
"Density"
"Energy"
"Flow Mass"
"Flow Volumetric"
"Force"
"Fuel Consumption"
"Length"
"Power"
"Pressure"
"Temperature"
"Time"
"Torque"
"Volume"

SCIENTIFIC (13 Classes)
"Absorbed Dose"
"Capacitance"
"Charge"
"Concentration Molar"
"Current"
"Flow Molar"
"Frequency Wavelength"
"Illumination"
"Inductance"
"Permeability"
"Radiation"
"Viscosity Dynamic"
"Viscosity Kinematic"

SPECIALISED (8 Classes)
"EU Currency"
"Data"
"Data Transfer"
"Digital Image Resolution"
"Lumber Volume"
"Telecommunications"
"Typography"
"Velocity"

Would end up with three Groups to select from:

DOMESTIC (17 Classes)
SCIENTIFIC (13 Classes)
SPECIALISED (8 Classes)

with three separate ubase.vvd files, one in each sub-Folder or whatever groupings the User cares to set up. Of course, maintenance of Custom Groupings would be entirely up to the User, as automating such would be an extreme modification. <g>

Whereas leaving all Classes in one Group Folder would end up with one Group, the same as is the current practise.

ALL_UNITS (38 Classes)

VersaVerter could then Title itself from the FolderName of the ubase.vvd file currently in use.

Although this DEFINITELY comes under the heading of "Ädvanced User", I think that the functionality would extend the versatility of VersaVerter, and end up with a much less "cluttered" interface.
Incremental Updates would then become possible, updating or adding single Classes. It would also demonstrate the intelligent usage and intended purpose of the portable XML data format.


On a lighter note, within the XML file, the spelling of "authours" should be corrected to: "authors"


Baldy.