Merge pull request #3 from Stone-Red-Code/develop

Add snapcraft & chocolatey manifests and move code to src

choco/ReadMe.md

@@ -0,0 +1,133 @@
+## Summary
+How do I create packages? See https://docs.chocolatey.org/en-us/create/create-packages
+
+If you are submitting packages to the community feed (https://community.chocolatey.org)
+always try to ensure you have read, understood and adhere to the create
+packages wiki link above.
+
+## Automatic Packaging Updates?
+Consider making this package an automatic package, for the best
+maintainability over time. Read up at https://docs.chocolatey.org/en-us/create/automatic-packages
+
+## Shim Generation
+Any executables you include in the package or download (but don't call
+install against using the built-in functions) will be automatically shimmed.
+
+This means those executables will automatically be included on the path.
+Shim generation runs whether the package is self-contained or uses automation
+scripts.
+
+By default, these are considered console applications.
+
+If the application is a GUI, you should create an empty file next to the exe
+named 'name.exe.gui' e.g. 'bob.exe' would need a file named 'bob.exe.gui'.
+See https://docs.chocolatey.org/en-us/create/create-packages#how-do-i-set-up-shims-for-applications-that-have-a-gui
+
+If you want to ignore the executable, create an empty file next to the exe
+named 'name.exe.ignore' e.g. 'bob.exe' would need a file named
+'bob.exe.ignore'.
+See https://docs.chocolatey.org/en-us/create/create-packages#how-do-i-exclude-executables-from-getting-shims
+
+## Self-Contained?
+If you have a self-contained package, you can remove the automation scripts
+entirely and just include the executables, they will automatically get shimmed,
+which puts them on the path. Ensure you have the legal right to distribute
+the application though. See https://docs.chocolatey.org/en-us/information/legal.
+
+You should read up on the Shim Generation section to familiarize yourself
+on what to do with GUI applications and/or ignoring shims.
+
+## Automation Scripts
+You have a powerful use of Chocolatey, as you are using PowerShell. So you
+can do just about anything you need. Choco has some very handy built-in
+functions that you can use, these are sometimes called the helpers.
+
+### Built-In Functions
+https://docs.chocolatey.org/en-us/create/functions
+
+A note about a couple:
+* Get-ToolsLocation - used to get you the 'tools' root, which by default is set to 'c:\tools', not the chocolateyInstall bin folder - see https://docs.chocolatey.org/en-us/create/functions/get-toolslocation
+* Install-BinFile - used for non-exe files - executables are automatically shimmed... - see https://docs.chocolatey.org/en-us/create/functions/install-binfile
+* Uninstall-BinFile - used for non-exe files - executables are automatically shimmed - see https://docs.chocolatey.org/en-us/create/functions/uninstall-binfile
+
+### Getting package specific information
+Use the package parameters pattern - see https://docs.chocolatey.org/en-us/guides/create/parse-packageparameters-argument
+
+### Need to mount an ISO?
+https://docs.chocolatey.org/en-us/guides/create/mount-an-iso-in-chocolatey-package
+
+### Environment Variables
+Chocolatey makes a number of environment variables available (You can access any of these with $env:TheVariableNameBelow):
+
+ * TEMP/TMP - Overridden to the CacheLocation, but may be the same as the original TEMP folder
+ * ChocolateyInstall - Top level folder where Chocolatey is installed
+ * ChocolateyPackageName - The name of the package, equivalent to the `<id />` field in the nuspec
+ * ChocolateyPackageTitle - The title of the package, equivalent to the `<title />` field in the nuspec
+ * ChocolateyPackageVersion - The normalized version of the package, equivalent to a normalized edition of the `<version />` field in the nuspec
+ * ChocolateyPackageFolder - The top level location of the package folder  - the folder where Chocolatey has downloaded and extracted the NuGet package, typically `C:\ProgramData\chocolatey\lib\packageName`.
+
+#### Advanced Environment Variables
+The following are more advanced settings:
+
+ * ChocolateyPackageParameters - Parameters to use with packaging, not the same as install arguments (which are passed directly to the native installer). Based on `--package-parameters`.
+ * CHOCOLATEY_VERSION - The version of Choco you normally see. Use if you are 'lighting' things up based on choco version. Otherwise take a dependency on the specific version you need.
+ * ChocolateyForceX86 = If available and set to 'true', then user has requested 32bit version. Automatically handled in built in Choco functions.
+ * OS_PLATFORM - Like Windows, macOS, Linux.
+ * OS_VERSION - The version of OS, like 10.0 something something for Windows.
+ * OS_NAME - The reported name of the OS.
+ * USER_NAME = The user name
+ * USER_DOMAIN = The user domain name (could also be local computer name)
+ * IS_PROCESSELEVATED = Is the process elevated?
+ * IS_SYSTEM = Is the user the system account?
+ * IS_REMOTEDESKTOP = Is the user in a terminal services session?
+ * ChocolateyToolsLocation - formerly 'ChocolateyBinRoot' ('ChocolateyBinRoot' will be removed with Chocolatey v2.0.0), this is where tools being installed outside of Chocolatey packaging will go.
+
+#### Set By Options and Configuration
+Some environment variables are set based on options that are passed, configuration and/or features that are turned on:
+
+ * ChocolateyEnvironmentDebug - Was `--debug` passed? If using the built-in PowerShell host, this is always true (but only logs debug messages to console if `--debug` was passed)
+ * ChocolateyEnvironmentVerbose - Was `--verbose` passed? If using the built-in PowerShell host, this is always true (but only logs verbose messages to console if `--verbose` was passed).
+ * ChocolateyExitOnRebootDetected - Are we exiting on a detected reboot? Set by ` --exit-when-reboot-detected`  or the feature `exitOnRebootDetected`
+ * ChocolateyForce - Was `--force` passed?
+ * ChocolateyForceX86 - Was `-x86` passed?
+ * ChocolateyRequestTimeout - How long before a web request will time out. Set by config `webRequestTimeoutSeconds`
+ * ChocolateyResponseTimeout - How long to wait for a download to complete? Set by config `commandExecutionTimeoutSeconds`
+ * ChocolateyPowerShellHost - Are we using the built-in PowerShell host? Set by `--use-system-powershell` or the feature `powershellHost`
+
+#### Business Edition Variables
+
+ * ChocolateyInstallArgumentsSensitive - Encrypted arguments passed from command line `--install-arguments-sensitive` that are not logged anywhere.
+ * ChocolateyPackageParametersSensitive - Package parameters passed from command line `--package-parameters-sensitive` that are not logged anywhere.
+ * ChocolateyLicensedVersion - What version is the licensed edition on?
+ * ChocolateyLicenseType - What edition / type of the licensed edition is installed?
+ * USER_CONTEXT - The original user context - different when self-service is used (Licensed)
+
+#### Experimental Environment Variables
+The following are experimental or use not recommended:
+
+ * OS_IS64BIT = This may not return correctly - it may depend on the process the app is running under
+ * CHOCOLATEY_VERSION_PRODUCT = the version of Choco that may match CHOCOLATEY_VERSION but may be different - based on git describe
+ * IS_ADMIN = Is the user an administrator? But doesn't tell you if the process is elevated.
+ * IS_REMOTE = Is the user in a remote session?
+
+#### Not Useful Or Anti-Pattern If Used
+
+ * ChocolateyInstallOverride = Not for use in package automation scripts. Based on `--override-arguments` being passed.
+ * ChocolateyInstallArguments = The installer arguments meant for the native installer. You should use chocolateyPackageParameters instead. Based on `--install-arguments` being passed.
+ * ChocolateyIgnoreChecksums - Was `--ignore-checksums` passed or the feature `checksumFiles` turned off?
+ * ChocolateyAllowEmptyChecksums - Was `--allow-empty-checksums` passed or the feature `allowEmptyChecksums` turned on?
+ * ChocolateyAllowEmptyChecksumsSecure - Was `--allow-empty-checksums-secure` passed or the feature `allowEmptyChecksumsSecure` turned on?
+ * ChocolateyChecksum32 - Was `--download-checksum` passed?
+ * ChocolateyChecksumType32 - Was `--download-checksum-type` passed?
+ * ChocolateyChecksum64 - Was `--download-checksum-x64` passed?
+ * ChocolateyChecksumType64 - Was `--download-checksum-type-x64` passed?
+ * ChocolateyPackageExitCode - The exit code of the script that just ran - usually set by `Set-PowerShellExitCode`
+ * ChocolateyLastPathUpdate - Set by Chocolatey as part of install, but not used for anything in particular in packaging.
+ * ChocolateyProxyLocation - The explicit proxy location as set in the configuration `proxy`
+ * ChocolateyDownloadCache - Use available download cache? Set by `--skip-download-cache`, `--use-download-cache`, or feature `downloadCache`
+ * ChocolateyProxyBypassList - Explicitly set locations to ignore in configuration `proxyBypassList`
+ * ChocolateyProxyBypassOnLocal - Should the proxy bypass on local connections? Set based on configuration `proxyBypassOnLocal`
+ * http_proxy - Set by original `http_proxy` passthrough, or same as `ChocolateyProxyLocation` if explicitly set.
+ * https_proxy - Set by original `https_proxy` passthrough, or same as `ChocolateyProxyLocation` if explicitly set.
+ * no_proxy- Set by original `no_proxy` passthrough, or same as `ChocolateyProxyBypassList` if explicitly set.
+

choco/build.ps1

@@ -0,0 +1,36 @@
+# YesNt Chocolatey Build & Pack Automation Script
+
+$ErrorActionPreference = "Stop"
+
+$nuspecPath = "yesnt.nuspec"
+$projectRoot = Get-Location
+
+Write-Host "--- Step 1: Building Projects in Release Mode ---" -ForegroundColor Cyan
+dotnet build ../src/YesNt.Interpreter.App/YesNt.Interpreter.App.csproj -c Release
+dotnet build ../src/YesNt.CodeEditor/YesNt.CodeEditor.csproj -c Release
+
+Write-Host "`n--- Step 2: Packing Chocolatey Package ---" -ForegroundColor Cyan
+# Remove old nupkg files if they exist
+Get-ChildItem *.nupkg | Remove-Item -Force -ErrorAction SilentlyContinue
+
+choco pack $nuspecPath
+
+$package = Get-ChildItem *.nupkg | Select-Object -First 1
+
+if ($package) {
+    Write-Host "`nSuccessfully created: $($package.Name)" -ForegroundColor Green
+    
+    $push = Read-Host "`nDo you want to push '$($package.Name)' to Chocolatey? (y/N)"
+    if ($push -eq 'y') {
+        $apiKey = Read-Host "Enter your Chocolatey API Key (or press enter if already configured)"
+        if ($apiKey) {
+            choco push $($package.Name) --source "'https://push.chocolatey.org/'" --api-key $apiKey
+        }
+        else {
+            choco push $($package.Name) --source "'https://push.chocolatey.org/'"
+        }
+    }
+}
+else {
+    Write-Error "Failed to generate .nupkg file."
+}

choco/tools/LICENSE.txt

@@ -0,0 +1,25 @@
+From: https://github.com/Stone-Red-Code/YesNt-Interpreter
+
+LICENSE
+
+MIT License
+
+Copyright (c) 2026 Stone_Red
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

choco/tools/VERIFICATION.txt

@@ -0,0 +1,9 @@
+VERIFICATION
+Verification is intended to assist the Chocolatey moderators and community
+in verifying that this package's contents are trustworthy.
+
+Source Code: https://github.com/Stone-Red-Code/YesNt-Interpreter
+Releases: https://github.com/Stone-Red-Code/YesNt-Interpreter/releases
+Checksum: [PLACEHOLDER]
+Verify using: certutil -hashfile C:\ProgramData\Chocolatey\lib\yesnt\yesnt.exe sha512
+Verify using: certutil -hashfile C:\ProgramData\Chocolatey\lib\yesnt\yesntcode.exe sha512

choco/yesnt.nuspec

@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="utf-8"?>
+<package xmlns="http://schemas.microsoft.com/packaging/2015/06/nuspec.xsd">
+  <metadata>
+    <id>yesnt</id>
+    <version>1.0.0.0</version>
+    <title>YesNt</title>
+    <authors>Stone_Red</authors>
+    <projectUrl>https://github.com/Stone-Red-Code/YesNt-Interpreter</projectUrl>
+    <licenseUrl>https://github.com/Stone-Red-Code/YesNt-Interpreter/blob/main/LICENSE</licenseUrl>
+    <requireLicenseAcceptance>true</requireLicenseAcceptance>
+    <projectSourceUrl>https://github.com/Stone-Red-Code/YesNt-Interpreter</projectSourceUrl>
+    <bugTrackerUrl>https://github.com/Stone-Red-Code/YesNt-Interpreter/issues</bugTrackerUrl>
+    <tags>yesnt scripting language interpreter code-editor</tags>
+    <summary>A line-based, interpreted scripting language and terminal code editor</summary>
+    <description>
+      **Usage**
+
+      1. Download &amp; install the latest release
+      - Chocolatey (Windows): `choco install yesnt`
+      - Snapcraft (Linux): `snap install yesnt`
+      - GitHub (Windows/Linux): [releases](https://github.com/Stone-Red-Code/YesNt-Interpreter/releases)
+      2. Run a script with the interpreter CLI
+      - `yesnt script.ynt` runs a script
+      3. Or use the terminal code editor
+      - `yesntcode` opens the editor (optional path to load a file)
+      - `run` / `debug` to execute the open script
+      - `format` to auto-format indentation
+    </description>
+    <releaseNotes>https://github.com/Stone-Red-Code/YesNt-Interpreter/releases/latest</releaseNotes>
+  </metadata>
+  <files>
+    <file src="tools\**" target="tools" />
+    <file src="..\src\YesNt.Interpreter.App\bin\Release\net10.0\**" target="tools" />
+    <file src="..\src\YesNt.CodeEditor\bin\Release\net10.0\**" target="tools" exclude="..\src\YesNt.CodeEditor\bin\Release\net10.0\YesNt.Interpreter.*" />
+  </files>
+</package>

snap/snapcraft.yaml

@@ -0,0 +1,58 @@
+name: yesnt
+version: "1.0.0.0"
+grade: stable
+summary: A line-based, interpreted scripting language and terminal code editor
+description: |
+  YesNt is a line-based, interpreted scripting language. The core idea is simple: each line maps to one primary statement. Lines are processed top-to-bottom, and inline tokens (like `${variable}` or `%read_line`) are substituted before the statement executes. Postfix modifiers like `calc` and `task` can also appear at the end of a line to evaluate arithmetic or fork execution into a background thread.
+
+  **Usage**
+
+  1. Download & install the latest release
+   - Chocolatey (Windows): `choco install yesnt`
+   - Snapcraft (Linux): `snap install yesnt`
+   - GitHub (Windows/Linux): [releases](https://github.com/Stone-Red-Code/YesNt-Interpreter/releases)
+  2. Run a script with the interpreter CLI
+   - `yesnt script.ynt` runs a script
+  3. Or use the terminal code editor
+   - `yesntcode` opens the editor (optional path to load a file)
+   - `run` / `debug` to execute the open script
+   - `format` to auto-format indentation
+
+base: core22
+architectures:
+  - build-on: amd64
+  - build-on: arm64
+
+confinement: strict
+
+parts:
+  yesnt:
+    plugin: dotnet
+    dotnet-build-configuration: Release
+    dotnet-self-contained-runtime-identifier: linux-x64
+    source: ./src/YesNt.Interpreter.App
+    build-packages:
+      - dotnet-sdk-10.0
+    stage-packages:
+      - libicu70
+  yesntcode:
+    plugin: dotnet
+    dotnet-build-configuration: Release
+    dotnet-self-contained-runtime-identifier: linux-x64
+    source: ./src/YesNt.CodeEditor
+    build-packages:
+      - dotnet-sdk-10.0
+    stage-packages:
+      - libicu70
+
+apps:
+  yesnt:
+    command: yesnt
+    plugs:
+      - home
+      - network
+  yesntcode:
+    command: yesntcode
+    plugs:
+      - home
+      - network

src/YesNt-Interpreter.sln

@@ -9,7 +9,7 @@ Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "YesNt.Interpreter", "YesNt.
 EndProject
 Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Solution Items", "Solution Items", "{52024699-4F8E-40F6-AF03-71DDB4A1DC06}"
 	ProjectSection(SolutionItems) = preProject
-		.editorconfig = .editorconfig
+		..\.editorconfig = ..\.editorconfig
 	EndProjectSection
 EndProject
 Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "YesNt.Interpreter.Tests", "YesNt.Interpreter.Tests\YesNt.Interpreter.Tests.csproj", "{2F95DCA7-3E43-4F2E-8FB2-067F0EC962B1}"

src/YesNt.CodeEditor/YesNt.CodeEditor.csproj

@@ -9,7 +9,7 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <None Include="..\.editorconfig" Link=".editorconfig" />
+    <None Include="..\..\.editorconfig" Link=".editorconfig" />
   </ItemGroup>
 
   <ItemGroup>

src/YesNt.Interpreter/YesNt.Interpreter.csproj

@@ -33,15 +33,15 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <None Include="..\assets\Logo.png">
+    <None Include="..\..\assets\Logo.png">
       <Pack>True</Pack>
       <PackagePath>\</PackagePath>
     </None>
-    <None Include="..\LICENSE">
+    <None Include="..\..\LICENSE">
       <Pack>True</Pack>
       <PackagePath>\</PackagePath>
     </None>
-    <None Include="..\README.md">
+    <None Include="..\..\README.md">
       <Pack>True</Pack>
       <PackagePath>\</PackagePath>
     </None>