|Undo $results._proceed=1 default, as window closing would leave it default.|
|mario authored 3 days ago last checkin c12edca42 ⎘|
|📂 UserTools||Derived from current base version 0.8.0; some sample and generic scri‹›||215 days ago|
|📂 data||Comment on UserTools/ dir working without CSV description‹›||214 days ago|
|📂 dev||text file fixup (evil Notepad!!)‹›||3 days ago|
|📂 img||Derived from current base version 0.8.0; some sample and generic scri‹›||215 days ago|
|📂 modules||Undo $results._proceed=1 default, as window closing would leave it de‹›||3 days ago|
|📂 tools||Swap directories‹›||215 days ago|
|📄 ClickyColoury.cmd||Write-Splash fix for PS2. Release a 0.9.0‹›||10 days ago|
|📄 LICENSE||Tag release 0.8.0‹›||214 days ago|
|📄 NEWS||Write-Splash fix for PS2. Release a 0.9.0‹›||10 days ago|
|📄 TextyTypey.cmd||Derived from current base version 0.8.0; some sample and generic scri‹›||215 days ago|
ClickyColoury is a WPF GUI frontend for PowerShell scripts. It also comes with a rudimentary CLI alternative. It's currently just a prototype however.
- Prototype stage, some code duplication still, not enough documentation
- Building the GUI is quite slow (mostly due to WPF widget creation, less the W wrapper)
- Still a lot of ToDos
- Scripts cannot be overly interactive (Read-Host yields an input popup)
- The CLI version is not on par with the GUI features
- Distributed only with a few generic scripts initially
- Implements plugin meta data for easy extension
- Allows CLI scripts to run nearly unchanged in a GUI
- Provides a color-aware Write-Host and a crude Read-Host wrapper
- Convenient $machine + $username toolbar input (w/ gimmicks)
- Additional input (text/combo boxes/boolean) support for scripts
- GUI is somewhat plain now, but adds icons in menus
- Overall design goal is to allow scripts to run alike in GUI or CLI, and (mostly) standalone
- "ClickyColoury" is a lowbrow approximation of the german term "KlickiBunti" (a common diss for GUI tools). Originally this was called "MultiTool" even. (Well, at least it keeps in line with being an overly generic title.)
init_intro.ps1shows a summary/"sigma" version of all installed scripts, rather than its main version.
Will you add more scripts?
- Sure. But sharing is caring. It's intially just a few cleansed tools, rather than the more complex custom ones. More to come, if there's enough interest and contributing back!
What is Fossil?
Why force that godawful "plugin meta data" upon us?
- The Powershell ecosystem is also in need of a bit standardization there. This feature/plugin scheme is used alike in other tools and languages, and highly convenient long-term. I'm aware "cross-platform" does not usually entice Windows programmers ;} But, still.
- It's not a dependency, btw. Nonetheless keeps everything more open-sourcy in its current form.
"It doesn't work"?
- Now that's not an actual error message. - And this project might not be useful to you.