b0f32811eb
* Tons of API doc updates * Removed stale test * Removed stale tests * Fixed Skipped Shadow test 1 * Fixed Skipped Shadow test 2 * Fixed Skipped Shadow test 3 * Removed stale test * Removed stale test2 * Explicit unregister of event handler on Application.Driver!.ClearedContents * Added Toplevels to dict * code cleanup * spelling error * Removed stale test3 * Removed stale test4 * Removed stale test5 * added script * tweaked script * tweaked script * Created StressTests project; moved some tests * Created IntegrationTests project; moved some tests * New yml * made old yml just unit tests * Tweaked Button_IsDefault_Raises_Accepted_Correctly * tweaked script * cleaned up ymls * tweakled up ymls * stress tests... * stress tests on ubuntu only * Fixed WindowsDriver in InvokeLeakTest * Fixed WindowsDriver in InvokeLeakTest2 * Added Directory.Packages.props. Added Directory.Build.props * Shortened StressTest time * Removed dupe file. * DemoFiles * Moved all tests to ./Tests dir. * Fixed release build issue * Fixed .sln file * Fixed .sl* files * Fixing ymls * Fixing interation tests * Create link to the file TestHelpers. * Created Tests/UnitTestsParallelizable. Moved all obviously parallelizable tests. Updated yml. * fixing logs * fixing logs2 * fixing logs3 * don't require stress to pass for PRs * Fix a failure? * tweaked script * Coudl this be it? * Moved tons of tests to parallelizable * Fixed some stuff * Script to find duplicate tests * Testing workflows * Updated to v4 * Fix RelativeBasePath issue * Replace powershell to pwsh * Add ignore projects. * Removed dupe unit tests * Code cleanup of tests * Cleaned up test warnings * yml tweak * Moved setter * tweak ymls * just randomly throwing spaghetti at a wall * Enable runing 5 test runners in par * Turned off DEBUG_DISPOSABLE for par tests * RunningUnitTests=true * code cleanup (forcing more Action runs) * DISABLE_DEBUG_IDISPOSABLE * Added View.DebugIDisposable. False by default. * Remobed bogus tareet * Remobed bogus tareet2 * fixed warning * added api doc * fixed warning * fixed warning * fixed warning2 * fixed warning3 * fixed warning4 --------- Co-authored-by: BDisp <bd.bdisp@gmail.com>
Development and Design-Time PowerShell Modules
This directory contains PowerShell modules for use when working with Terminal.sln
Purpose
These modules will be modifed and extended as time goes on, whenever someone decides to add something to make life easier.
Requirements
These modules are designed for PowerShell Core, version 7.4 or higher, on any platform, and must be run directly within a pwsh process.
If you want to use them from within another application, such as PowerShell hosted inside VSCode, you must first run pwsh in that terminal.
As the primary development environment for Terminal.Gui is Visual Studio 2022+, some functionality may be limited, unavailable, or not work on platforms other than Windows.
Most should still work on Linux, however.
Functions which are platform-specific will be documented as such in their Get-Help documentation.
Specific requirements for each module can be found in the module manifests and will be automatically imported or, if unavailable, PowerShell will tell you what's missing.
Usage
From a PowerShell 7.4 or higher prompt, navigate to your Terminal.Gui repository directory, and then into the Scripts directory (the same directory as this document).
Import Module and Configure Environment
Run the following command to import all Terminal.Gui.PowerShell.* modules:
Import-Module ./Terminal.Gui.PowerShell.psd1
If the environment meets the requirements, the modules will now be loaded into the current powershell session and exported commands will be immediately available for use.
Getting Help
All exported functions and commandlets are provided with full PowerShell help annotations compatible with Get-Help.
See The Get-Help documentation at Microsoft Learn for Get-Help information.
Cleaning Up/Resetting Environment
No environment changes made by the modules on import are persistent.
When you are finished using the modules, you can optionally unload the modules, which will also reset the configuration changes made on import, by simply exiting the PowerShell session (exit) or by running the following command:
NOTE DIFFERENT TEXT FROM IMPORT COMMAND!
Remove-Module Terminal.Gui.PowerShell
LICENSE
MIT License
Original Author: Brandon Thetford (@dodexahedron)
See COPYRIGHT in this directory for license text.