Andrey,

prior to your API adjustments I committed some improvements to the Maxima Plugin. Is there a way to publish these also for build 6671 (except by temporary reverting and afterwards re-committing your changes)?

I think of pointing not just to the SVN path but also to a particular SVN revision in the release manager.

Would the above-mentioned procedure worth the effort or do you consider support of 6671 now being obsolete?

EDIT: I found out how to do it: just append the revision to the path:

https://smath.info:8443/svn/public/plugins/MaximaPlugin@2740

Hello Martin.

Of course it is possible to revert changes, make an update/release and re-apply initial changes again. It will take some time, but we can do it if you wish (let me know if any help is required).

I plan to release new stable version in 1 or 2 weeks. Actually I needed this beta just because not all plug-ins are ready and tested. So if your changes are not very urgent then it may be more convenient to wait a bit. But it is up to you!

Best regards.

Wrote

Hello Martin.

Of course it is possible to revert changes, make an update/release and re-apply initial changes again. It will take some time, but we can do it if you wish (let me know if any help is required).

I plan to release new stable version in 1 or 2 weeks. Actually I needed this beta just because not all plug-ins are ready and tested. So if your changes are not very urgent then it may be more convenient to wait a bit. But it is up to you!

Best regards.

I wasn't aware of that the release manager accepts SVN paths with revision tag (should have asked this to google before asking here). This did the trick, so the Maxima Plugin is updated for 6671 stable and 6824 beta without messing with the repository.

BTW thanks for doing all the API adjustment work for us!

The Extension manager in 6824 doesn't fetch the correct version of the Maxima plugin. Andrey has released a stable version of the plugin for 6824 and later I did a stable version for 6671. Now 6824 always downloads the version for 6671 and then complains that installation fails.

I'd expect that the specification of which SMath is used for release is honoured by the extension manager. How can this be resolved?

Any release is for the targeted version and later, thus you have to publish several releases targeting from the older target to the newer (first make a release for 6671, then make another for the latest)

The problem was that the plugin has been released for 6824 before it was released for 6671. Repeating the release without any changes for 6824 seems to solve the problem. Maxima now loads correctly in 6824. Yet, due to lack of other important plugins (custom glyphs, X-Y plot) fun is limited in that version.

As for the X-Y Plot and other (ZedGraph, NPlot). New API does not fully cover the requirements of these plugins. For now I can't port X-Y Plot.

Wrote

As for the X-Y Plot and other (ZedGraph, NPlot). New API does not fully cover the requirements of these plugins. For now I can't port X-Y Plot.

The hint is IGraphics.Unwrap(). After you've got native GDI+ Graphics object you can do what you need until API is updated according to your requirements. Currently all the plug-ins support .Net Framework 2.0 or later so they can be used for SMath Studio Desktop only.

I plan to allow plug-ins for other platforms and will extend API with all required by plug-ins, but it will be a bit later. For now this should be not an issue.

Please contact me by Skype in case of any questions.

Best regards.

Wrote

The hint is IGraphics.Unwrap(). After you've got native GDI+ Graphics object you can do what you need until API is updated according to your requirements. Currently all the plug-ins support .Net Framework 2.0 or later so they can be used for SMath Studio Desktop only.

Ok, this trick helped me. But Release Manager makes the assembly which I can't install.

Wrote

Ok, this trick helped me. But Release Manager makes the assembly which I can't install.

Thank you for updates!

I've just checked your NPlot, X-Y Plot and Zed Graph - everything works ok on my machine with latest SMath Studio.

Please could you provide some details about what happens on your environment. The most important change I did on build machine is that now system using MSBuild v.15 during compilation of plug-ins.

Citazione

I've just checked your NPlot, X-Y Plot and Zed Graph - everything works ok on my machine with latest SMath Studio.

It was SMath Studio 0.99.6823. Now it works fine.

There seems to be a problem with the Insert menu entries. The controls entry is cloned with each installation of one of the controls.

Wrote

The controls entry is cloned with each installation of one of the controls.

Thank you! Fixed.

The new text region is loaded, but fails. No update for Excel I/O

Wrote

The new text region is loaded, but fails

Seems that the WriterRegion assemblies are copied to the extension archive even if the msbuild projects is set to not do it... I'll check for workarounds...

Hi,

I can't launch this new version 0.99.6824 on linux (Ubuntu 18.04 - mono 4.2.1)

Message diplayed:
Unhandled Exception:
System.Exception: Can't find a proper language file. Try to reinstall the program.
at SMath.Manager.SessionsManager.ReloadLanguages () <0x4155feb0 + 0x0017b> in :0
at SMath.UI.SessionsManagerPaths.Create (System.String[] paths) <0x4154b9b0 + 0x0005b> in :0
at SMath.UI.AppSettingsDesktop.Initialize (SMath.Manager.PluginsStatusEventHandler loaded) <0x41544960 + 0x0017b> in :0
at SMath.UI.Desktop.Program.
(System.String[] ) <0x414c1fb0 + 0x001c7> in :0
[ERROR] FATAL UNHANDLED EXCEPTION: System.Exception: Can't find a proper language file. Try to reinstall the program.
at SMath.Manager.SessionsManager.ReloadLanguages () <0x4155feb0 + 0x0017b> in :0
at SMath.UI.SessionsManagerPaths.Create (System.String[] paths) <0x4154b9b0 + 0x0005b> in :0
at SMath.UI.AppSettingsDesktop.Initialize (SMath.Manager.PluginsStatusEventHandler loaded) <0x41544960 + 0x0017b> in :0
at SMath.UI.Desktop.Program.
(System.String[] ) <0x414c1fb0 + 0x001c7> in :0
Thanks
Philippe.

Wrote

Hi,

I can't launch this new version 0.99.6824 on linux (Ubuntu 18.04 - mono 4.2.1)

Hello Philippe,

this is a known bug and should be already solved in the next release (see here for testing)