Powershell GUI fronted (WPF) to run categorized console scripts

⌈⌋ ⎇ branch:  ClickyColoury


Update of "ToDo"

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview

Artifact ID: 214d9fa8b8895b616f80576d55a48959a2cc9cca
Page Name:ToDo
Date: 2018-04-09 20:35:40
Original User: mario
Mimetype:text/x-markdown
Parent: c21f3f40b707d0ebefa193879af1520844c64aa7 (diff)
Next ede99b302cbb31fcac2a0c9878822dc99a8e04a7
Content

Non-exhaustive and outdated list on what's still to be fixed.

general

  • docs docs docs, albeit it's a bit too early to document most of the GUI startup e.g.

  • $machine → $computer
    (Made up my mind. $machine sounded more pleasing initially. But everyone else is just using $computer. So: rewriting time...)

GUI

  • HTML export is gone. Temporary workaround: RTF. Still needs a proper WD widget to HTML traverser, or simpler perhaps: XAML to HTML converter.

CLI

  • Read-Host alias (to retain variable states, e.g. computername)

modules

  • combine core plugins/funcs_*.ps1 into menu or a more generic module, once stable

  • general enable PSRemoting shortcut

  • unifiy Create-TaskSched

  • stubs for Add-Printer etc.

CLI

  • Read-ComputerName alias (with cached value)

  • or better another generic Read-Host alias

Script ideas

  • net view \target /all

Done

  • Powershell 5.0 compatility

    • non-threading mode for starters (not implemented yet)
    • Wasn't much of a scoping issue, but the runspace building / function redeclarations. (Simple fix: use dumb module reimports.)
    • Still runs on PowerShell 2.0; albeit the WPF widgets have somewhat different signatures here and there. So keeping it that way requires some concessions..
  • Out-Gui BEGIN/PROCESS/END for capturing live pipe output (no more Write-Host)

  • Default for Out-String to 120 chars

  • Wider WPF TextBlock output window

  • selection hack for TextBlock (C#)

  • ribbon: Unicode clipboard

  • ribbon: App shortcuts

  • HTML clipboard conversion

  • $cfg.domain

  • Fossil repo