A workspace plugin can obtain the version string associated with the oXygen Editor/Author/Developer that it is being run in by using the getVersion method of the StandalonePluginWorkspace object that is provided to it. It would be useful if we could also obtain the build number (and possibly the release date)* from within a plugin, so that its behaviour can be adjusted depending on the build-number (or release date). *The build numbers alone are probably fine, as they are likely to be monotonically increasing, so we can simply test to see if the current build number is greater than a specified build number to determine if it is later release. Example: If a feature of a plugin is known to work with some, but not all patch releases of a given oXygen release, then it would be possible to tailor the behaviour of the plugin to: (1) switch off the feature for oXygen patch releases that it is known not to work in; (2) let the user know why a given feature is not available; and potentially (3) let the user know that in order to get access to the feature they need to get the latest version of say the '15.2' version of oXygen. Best regards, Anthony. -- Michael Anthony Smith Senior Software Engineer DeltaXML Ltd "Experts in information change" T: +44 1684 532 140 E: anthony.smith@deltaxml.com W: http://www.deltaxml.com Malvern Hills Science Park, Malvern, Worcs, WR14 3SZ, UK Registered in England 02528681 Reg. Office: Monsell House, WR8 0QN, UK