ClickyColoury is a WPF GUI frontend for PowerShell scripts. It also comes with
a rudimentary CLI alternative. It's currently just a prototype however.

### Cons     <img width=420 height=320 align=right style="padding-left: 10px">

 * Prototype stage, some code duplication still, not enough documentation
 * Building the GUI is quite slow (mostly due to WPF widget creation, less the [W](wiki/W) wrapper)
 * Still a lot of [ToDo](wiki/ToDo)s
 * 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

### Pros

 * Implements [plugin meta data](wiki/plugin+meta+data) for [easy extension](wiki/new-script)
 * Allows CLI scripts to run nearly unchanged in a GUI
   <img width=350 height=172 align=right style="padding-left: 10px">
 * Provides a color-aware Write-Host and a crude Read-Host wrapper
 * Convenient $machine + $username [toolbar](wiki/toolbar) input (w/ gimmicks)
 * Additional input (text/combo boxes/boolean) support for scripts
 * GUI is somewhat plain now, but adds [icons](wiki/img) in menus
 * Overall design goal is to allow scripts to run alike in GUI or CLI, and (mostly) standalone

### Trivia

- license

   - MITL

- project name

   - "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.)

- version

   - `init_intro.ps1` shows a summary/"sigma" version of all installed scripts, rather than its main version.

### FAQ

- 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?

    - See - It's a convenient distributed version control system. It's much more cross-platform than GIT, as it comes in a single EXE even for Windows. Just [clone this](wiki/fossil-tutorial) repository, and try `fossil ui`

- Why *force* that godawful "[plugin meta data](wiki/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.