Computator.NET is a special kind of numerical software that is fast and easy to use but not worse than others feature-wise. It's features include: - Real and complex functions charts - Real and complex calculator - Real functions numerical calculations including different methods - Over 107 Elementary functions - Over 141 Special functions - Over 21 Matrix functions and operations - Scripting language with power to easy computations including matrices - You can declare your own custom functions with scripting language
Computator.NET.Core project should target .NET Core / PCL so it can be used as logic for all platforms (Desktop, Mobile, ...)
Since we would like to develop mobile (and possibly even web) versions of Computator.NET and since there is global strive towards unified NETStandard we should move all non-UI code to .NET Core if possible.
It will be a tremendous effort and it can require vast array of ifdefs within the code since we still would like to target older runtimes such as NET40 (and NETStandard is for NET45 and higher). However I think it is worth it because the architecture could become more clean thanks to it.
It should introduce hard architecture boundary between shared code (.NET Core) and platform specific code (Xamarin or Mono or NET Framework) which is really good for the whole project.
First tasks to do:
[ ] Computator.NET.Core should not reference Computator.NET.Charting #51
[ ] Computator.NET.Core should not reference any platform specific assemblies like:
Computator.NET.Core project should target .NET Core / PCL so it can be used as logic for all platforms (Desktop, Mobile, ...)
Since we would like to develop mobile (and possibly even web) versions of Computator.NET and since there is global strive towards unified NETStandard we should move all non-UI code to .NET Core if possible.
It will be a tremendous effort and it can require vast array of ifdefs within the code since we still would like to target older runtimes such as NET40 (and NETStandard is for NET45 and higher). However I think it is worth it because the architecture could become more clean thanks to it.
It should introduce hard architecture boundary between shared code (.NET Core) and platform specific code (Xamarin or Mono or NET Framework) which is really good for the whole project.
First tasks to do: