RC3: SMath Studio 0.98.6096 (09 September 2016) - Messages
- Added ability to retrieve submatrix of specified rows and columns using ranges within el(..) function;
- Plug-ins management improved to support single Extensions folder by multiple versions of SMath Studio (extensions installed for newer SMath Studio versions will not break previous installations anymore);
- Protected Area Regions fully supported in SMath Viewer applications now;
- [SV-2396]: Possible exceptions on language change in SMath Viewer fixed;
- [SS-15], [SS-2384]: Handling of zero, infinity and strings by symbolic library improved;
- Plug-ins compatibility dialog now always shown on top of other windows because it is not displayed in taskbar and can be lost from users view;
- Missing required parenthesis when using Calculations menu items fixed.
- Desktop Windows (desktop computer with Windows OS):
SMathStudioDesktop.0_98_6096.Setup.msi (Date: 09.09.2016. File size: 2.07MB)
- Desktop Linux (desktop computer with Linux OS):
SMathStudioDesktop.0_98_6096.Mono.tar.gz (Date: 09.09.2016. File size: 1.21MB) - last version of Mono distributive required!
- Cloud version (all modern browsers supported):
SMath Studio in the Cloud (Date: 09.09.2016.)
The remove (dustbin) button does not work (plugin remains in the list)
The indicated version is different from the one offered in the installed SMath (6011.17119)
Edit: Also no success with the following plugins in the portable version (no problems in the installer version)
SQLite
Text Region Utilities
I've finally reproduced issue you have mentioned. It happened because you have put not supported HyperlinkRegion.dll version directly into plugins directory.
- First of all, Hyperlink Region ver. 1.0.5958.15351 not supported by latest version of SMath Studio. You have to use beta version (please see http://en.smath.info/view/HyperlinkRegion for the link).
- Second, plugins directory designed to support only plug-ins which are 100% compatible with current version of SMath Studio (usually you can find only built-in plig-ins). All others are better to put under extensions\plugins\
\ , even if we are talking about portable version. But be aware, in addition to such a complex path config.\ .ini must be available under extensions\plugins\\ and it should contain a text with version (i.e. folder) of the plug-in to use.
Regarding item 2: to understand it properly just try to install any plug-in using Extensions Manager and then go to extensions folder next to SMath Studio EXE (if portable.version exists) or to %APPDATA%\SMath\extensions (otherwise).
So, if you will correct location of the HyperlinkRegion.dll (and other plug-ins manually put into plugins folder) issue will gone.
Best regards, Andrey Ivashov.
WroteMartin, thank you!
- First of all, Hyperlink Region ver. 1.0.5958.15351 not supported by latest version of SMath Studio. You have to use beta version (please see http://en.smath.info/view/HyperlinkRegion for the link).
Thank you Andrey. Your response reminded me that I simply forgot to activate the beta versions in the online gallery. This might have lead to different experiences in the update manager between the installer version (where beta versions were activated) and the portable version.
I didn't mess around with the hyperlink region but manually exchanged the contents of the Maxima plugin directory for test purposes.
I'll do a second install of the portable version and see if I get a clean set of plug-ins with the betas activated.
Edit: Test results for a new installation.
- download linux version
- add empty portable.region file
- open SMath
- Tools> Plugins: Online gallery, unselect "exclude beta versions"
Install plugins in the following order:
Checkbox region
Checkbox list region
Combobox region
Combobox list region
Conditional Expression...
CF label
Currency units
Custom functions
Custom glyphs
Data exchange
Development tools
DotNumerics
Excel files
Excel IO
FFTpack
Gnu Scientific lib
GPC Wrapper
Hyperlink region
Image region
Mathcad file access
Maxima (fail)
Modeller
Nonlinear Solvers
Numeric UD
Octave
ODE Solvers
PDF files
Pie chart region
Slider region
Snapshot region
SQLite (fail)
Statistical tools
Text region utilities (fail)
Writer region
XLSX import/export
X-Y plot region
Close SMath and restart:
Message: Plugins failed to start:
Maxima
SQLite
Close the dialog
Check for Text region utilities -> Insert> Text region utilities> add.. Dialog works.
No idea why the fail message appeared upon installation.
In the extension manager it is green now.
Next action: Test Maxima Plugin
- tools> Plugins> Interactive books> online gallery, download Interactive SMath Handbook, check use by default. Press "open"
- Launch interactive handbook: [?] Plugins, in plugins page follow link to plugin dir (green button next to plugin name (Maxima)
- Close SMath (otherwise you can't remove the Maxima dll in the plugin dir)
- Exchange contents of the single subdirectory by the contents of SVN 2175 version (see SS 2347
- Start SMath
Main restrictions of this Maxima version: No replacement of sum(4), det(), int(4) and diff(2) and diff(3) due to changed policy in SMath. The remainder seems to work more or less. Thanks to Davide for fixing compatibility issues!
This simple example reports an error in 9096.
I found it in a few worksheets.
File not found.File not found.
Best regards.
It is an issue of cases(..) function defined in Custom Functions plug-in. Issue is not related to specific version of the program.
F.e. you can try to use if(..) instead of cases(..) to see how it should really behave.
Best regards.
Sorry, I thought it was related to 9096, because of it was working fine with the Smath version couple of days older.
Has the plugin changed ? I didn't notice it.
Thanks
In the case of k>5 as condition (screenshot above), this happens because cases is running in symbolic evaluation and because this:
Wrote[SS-15], [SS-2384]: Handling of zero, infinity and strings by symbolic library improved;
Handling of zero is changed with symbolic evaluation (internal of cases: sum of booleans); before everything multiplied by 0 was considered 0 (that was a bug), hence no exception was thrown before this version.
fix for cases: switch to numerical evaluation if you are outside of a programming function, use eval() otherwise
edit: nevermind, I think I found a way to have a uniform behavior without breaking the back-compatibility

I thank you for this testing the possible continuing on the portable version (I reproduced your instructions), but I have to admit that having a portable version with the plugins (which I would prefer) is quite a mess at the moment.
Regards,
Radovan
WroteHello Martin,
I thank you for this testing the possible continuing on the portable version (I reproduced your instructions), but I have to admit that having a portable version with the plugins (which I would prefer) is quite a mess at the moment.
Regards,
Radovan
Thanks for the feedback. What do you mean is a mess?
The process of getting a portable version (installation) or the result/user experience?
Once the image region is fixed and the interactive handbook updated, I can make a new portable version for download. Then getting the distribution would be easy.
If the result is a mess - what could be improved?
WroteWroteHello Martin,
I thank you for this testing the possible continuing on the portable version (I reproduced your instructions), but I have to admit that having a portable version with the plugins (which I would prefer) is quite a mess at the moment.
Regards,
Radovan
Thanks for the feedback. What do you mean is a mess?
The process of getting a portable version (installation) or the result/user experience?
Once the image region is fixed and the interactive handbook updated, I can make a new portable version for download. Then getting the distribution would be easy.
If the result is a mess - what could be improved?
I am very grateful to you for having in mind and keeping the idea of making a portable, downloadable version - the most easy way of using SMATH (IMHO) . I just have a feeling as a user - not developer (might be wrong, of course) that there were so many changes regarding plugins inside SMath that the plugin makers had quite a lot of troubles to cope with them. To repeat, I just have an impression of that and just want that SMath get into some "calm waters" after such a long time, nothing else.
Regarding the improvements, we had quite a many comments about it. For example, many times mentioned, but there is still quite a critical problem to have an efficient tracking of the SMath functions - "which one is which, and what they do?", regarding the plugins. I do not have the answer how to solve this.
Regards,
Radovan
Wrote
I am very grateful to you for having in mind and keeping the idea of making a portable, downloadable version - the most easy way of using SMATH (IMHO) . I just have a feeling as a user - not developer (might be wrong, of course) that there were so many changes regarding plugins inside SMath that the plugin makers had quite a lot of troubles to cope with them. To repeat, I just have an impression of that and just want that SMath get into some "calm waters" after such a long time, nothing else.
Regarding the improvements, we had quite a many comments about it. For example, many times mentioned, but there is still quite a critical problem to have an efficient tracking of the SMath functions - "which one is which, and what they do?", regarding the plugins. I do not have the answer how to solve this.
Regards,
Radovan
As to the tracking of the functions:
- An important improvement was that the dynamic assistant now shows the name of the plugin, where the function is defined. That helps a lot in searching for documentation or for reporting bugs.
- Every plugin developer can specify, what explanation the dynamic assistant shows. Some care more about this, some care less. Perhaps you can't expect uni to write custom strings for all the bulk function libs, which he wrote interfaces for.
- Davide has started to contribute pages on his plugins for the interactive handbook, that will also improve the access to documentation.
For me, a weak point (and a nightmare for teaching) of SMath is the complex logic of user function definition. Davide's handbook in the extension manager would be helpful, if I was capable to memorize all the side effects and name space particularities, which he really tried hard to explain. Would be nice if we could just get along without all these underscores, apostrophes, hashmarks and the like, which are there just to prevent them from eventually coinciding with outer space names...
I still remember how upset I was when I realized, that names of dummy parameters in function definitions matter! Took me almost as long as to find out how to input 1..3
-
New Posts
-
No New Posts