You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some people @psi would like to see the library centrally deployed and configured in our Matlab instances. So when Matlab starts up on a Console that ca_matlab is already there ...
The text was updated successfully, but these errors were encountered:
We strongly suggest to bundle the ca_matlab library with your Matlab application. This brings several advantages.
Self-contained applications - Your applications can be easily executed on any machine that runs Matlab
(e.g. just git clone and execute). You are not dependent on any kind of PSI infrastructure (e.g. Network shares, etc.)
Upgrade at your own speed - Once a new version of the library is out you can upgrade to it at your own speed. There is also not the case that a centrally deployed library gets updated and your application starts behaving differently.
Adding the library, disk space wise is not a big deal, its just around 600k (and will be even smaller in future)
Therefore we don't foresee a central deployment and automatic configuration.
Some more notes about what is the "production version". The latest officially released version we regard as recommended "production version". However it is in the freedom and the task of the application developer to upgrade to this version.
(Code fixing) Support will only be given to the very latest version of the library.
Some people @psi would like to see the library centrally deployed and configured in our Matlab instances. So when Matlab starts up on a Console that ca_matlab is already there ...
The text was updated successfully, but these errors were encountered: