For molecular modelers, ensuring the seamless functionality of software tools is a cornerstone of maintaining efficient workflows. One recurring pain point can be compatibility issues between software platforms and their extensions, which might disrupt processes and reduce productivity. If you’ve experienced such frustrations, understanding how SAMSON handles extension compatibility could provide powerful solutions.
How SAMSON Ensures Compatibility
SAMSON uses a robust system to check the compatibility of SAMSON Extensions with its core version. Each SAMSON version employs a specific Software Development Kit (SDK) version, identified by the familiar major.minor.patch numbering format. At startup, SAMSON compares its SDK version with the version used to develop each SAMSON Extension. This process prevents incompatible extensions from loading, ensuring smooth performance and avoiding potential system conflicts.
For example, SAMSON version 1.7.8 is compatible with all SDK versions where:
- The major SDK version number matches SAMSON’s (in this case,
1). - The minor SDK version number is less than SAMSON’s minor version number (
7).
This means SDK versions such as 1.3.5 or 1.7.7 would work without issue, while an SDK version like 1.8.5 would not be compatible. Incompatible extensions could utilize functions or resources absent in the installed SAMSON version, leading to errors.
Automatic Updates Simplify the Process
SAMSON strives to minimize user interruptions by automatically updating SAMSON Extensions when new compatible versions are published on SAMSON Connect. To demonstrate, let’s consider a scenario:
Suppose your installed SAMSON version is 1.7.8, and you have an extension built with SDK version 1.5.2. This extension is loaded seamlessly due to version compatibility. Now, if a new compatible version of the extension—built with SDK version 1.6.4—is published, SAMSON will automatically update to this new version upon startup, as long as an Internet connection is available.
However, if SAMSON version 2.0.0 and its SDK are released, and new extensions are built with this updated SDK, your older SAMSON installation (e.g., version 1.7.8) will not load extensions requiring SDK 2.0.0. This ensures system integrity and avoids potential conflicts.
Keeping SAMSON Up-to-Date
Given the importance of compatibility, the SAMSON development team encourages users to update their installations regularly. Updates bring new features, improvements, and fixes, enhancing the overall experience while ensuring compatibility with the latest extensions.
To delve deeper into SAMSON’s versioning system and compatibility policy, visit the official documentation at this page.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON today at SAMSON Connect!