|Mini tool to look up some basic infos on servers/hostnames|
|mario authored 23 days ago last checkin 8d7d5133e ⎘|
|📂 UserTools||Derived from current base version 0.8.0; some sample and generic scri‹›||25 days ago|
|📂 data||Comment on UserTools/ dir working without CSV description‹›||25 days ago|
|📂 dev||comment on PMD extractor‹›||25 days ago|
|📂 img||Derived from current base version 0.8.0; some sample and generic scri‹›||25 days ago|
|📂 modules||Add new project url: (fossil repo)‹›||24 days ago|
|📂 tools||Swap directories‹›||25 days ago|
|📄 ClickyColoury.cmd||Tag release 0.8.0‹›||24 days ago|
|📄 LICENSE||Tag release 0.8.0‹›||24 days ago|
|📄 NEWS||Tag release 0.8.0‹›||24 days ago|
|📄 TextyTypey.cmd||Derived from current base version 0.8.0; some sample and generic scri‹›||25 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, code duplication, not enough documentation
- Only works on PowerShell -Version 2.0 for now
- Building the GUI is quite slow (mostly due to WPF and the W wrapper)
- Still a lot of ToDos
- Scripts cannot be overly interactive (Read-Host just yields a VB 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)
- Basic forms (text/dropdown) field support
- GUI is somewhat unstructured, but adds icons for orientation
- 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 in general). Originally this tool 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 in particular is in dire need of at least an basic effort at standardization. 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.