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
The next update, Version 1.7, will be released under two nuget names
SharpVectors.Reloaded
SharpVectors
I have received ownership of the SharpVectors nuget package and will publish the next updates with this name too. The contents will be the same.
Current users of the SharpVectors.Reloaded will be advised to move to SharpVectors package, there will be no breaking changes.
Hopefully, with Version 1.9, we will also release the scripting package as a separate nuget package. It will depend on other third-party JavaScript engine package, and we cannot ensure availability for all .NET framework versions supported by the SharpVectors.
SharpVectors.Scripting, a rename of the current unreleased project, SharpVectors.Scripting.Jint.
The plan is to use NiL.JS, as the default JavaScript engine. It has some issues, but it seems more complete than the current, Jint.
After this, the SharpVectors.Reloaded package naming will be depreciated for SharpVectors package, and finally dropped in Version 2.0.
With the Version 2.0, we will expect some (hopefully minimal breaking changes), with the split of the packages as follows. Each will be complete and independent package (except SharpVectors.Scripting):
SharpVectors, for both WPF and Windows Forms developments (targeting the current frameworks, and NET 5.0)
SharpVectors.Wpf, for WPF developments
SharpVectors.Gdi, for Windows Forms developments
SharpVectors.Skia, for Skia-Sharp developments
SharpVectors.Scripting, an add-in for scripting support
SharpVectors.Uwp, for UWP developments
SharpVectors.Standard, targeting .NET Standard 2.x platform (output with System.Drawing.Common)
If possible, the minimum .NET framework from the Version 2.0 will be .NET 4.5! Your views on these issues are welcomed.
Documentations
Starting with Version 1.9, we will provide complete API and conceptual documentations. It will use the DocFX and hosted here on Github.
Applications
The current applications will be moved to separate repositories to allow for further improvements and developments. This will make them more useful as tools for development. The target applications are
Converters.Wpf, the SharpVectors Converter will be renamed SvgXaml.
Squiggle.Wpf, the SharpVectors Viewer will be renamed SvgViewer.
Revisions
2020/08/13: Added documentation information and Application information.
2021/03/21: Documentation and Scripting moved to version 1.9.
The text was updated successfully, but these errors were encountered:
NOTE: All dates in Year/Month/Day format.
Version Planning - 2020/08/13
The next update, Version 1.7, will be released under two nuget names
I have received ownership of the SharpVectors nuget package and will publish the next updates with this name too. The contents will be the same.
Current users of the SharpVectors.Reloaded will be advised to move to SharpVectors package, there will be no breaking changes.
Hopefully, with Version 1.9, we will also release the scripting package as a separate nuget package. It will depend on other third-party JavaScript engine package, and we cannot ensure availability for all .NET framework versions supported by the SharpVectors.
The plan is to use NiL.JS, as the default JavaScript engine. It has some issues, but it seems more complete than the current, Jint.
After this, the SharpVectors.Reloaded package naming will be depreciated for SharpVectors package, and finally dropped in Version 2.0.
With the Version 2.0, we will expect some (hopefully minimal breaking changes), with the split of the packages as follows. Each will be complete and independent package (except SharpVectors.Scripting):
SharpVectors.Uwp, for UWP developmentsSharpVectors.Standard, targeting .NET Standard 2.x platform (output with System.Drawing.Common)If possible, the minimum .NET framework from the Version 2.0 will be .NET 4.5! Your views on these issues are welcomed.
Documentations
Starting with Version 1.9, we will provide complete API and conceptual documentations. It will use the DocFX and hosted here on Github.
Applications
The current applications will be moved to separate repositories to allow for further improvements and developments. This will make them more useful as tools for development. The target applications are
Revisions
The text was updated successfully, but these errors were encountered: