When I started this project I knew I wanted to work towards these high-level minimum requirements:
Must support Windows, macOS and Linux
Must support at least .NET 6 or higher
Must run with as little hassle as possible for end users.
However I had yet to figure out how the pieces will fall on the board. I initially took a layered approach to structuring the solution, this helped me clearly understand the different components, abstractions and dependencies that will make up the app during development. That has now served its purpose, and its time for a simpler structure that's easier to understand and maintain. This restructure aims to:
Make the solution easier to maintain by reducing separation between components and bringing more related functionality together.
Make the solution easier to review by the community and easier to understand and contribute to.
I plan to add documentation explaining the high level concepts and structure of the solution to help facilitate review and contribution.
Some notable technical changes:
Reduced number of projects. Most of the core functionality of NetPad is now in a new NetPad.Runtime project
The concept of a "ScriptRuntime" is now called a "ScriptRunner" and is part of the "Execution Model"
Use Directory.Build.props file and C# 12 features
No refactoring was done to the JS app
Fix web version 'process' pollyfill
Passing --swagger flag to NetPad.Apps.App generates Swagger client code
Refactoring that is also planned soon:
Upgrading to .NET 8
Refactoring of the JS app
Changing the name of the NetPad.Apps.App project and the folder containing the JS client app, currently named "App"
Solution restructure
When I started this project I knew I wanted to work towards these high-level minimum requirements:
However I had yet to figure out how the pieces will fall on the board. I initially took a layered approach to structuring the solution, this helped me clearly understand the different components, abstractions and dependencies that will make up the app during development. That has now served its purpose, and its time for a simpler structure that's easier to understand and maintain. This restructure aims to:
I plan to add documentation explaining the high level concepts and structure of the solution to help facilitate review and contribution.
Some notable technical changes:
Refactoring that is also planned soon: