Non-exhaustive and outdated list on what's still to be fixed.
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.
$machinesounded more pleasing initially. But everyone else is just using
$computer. So: rewriting time...)
- Try Start-Process -ArgumentList @() again for starting external powershell.exe (type: cli|window) - instead of Convert-VarsToCmdArgs()
generic Read-Host alias (to retain variable states, e.g. computername)
Come up with a plan to enter/pass multiline/Read-Host params (
Read-ComputerName alias (with cached value)
combine core plugins/funcs_*.ps1 into menu or a more generic module, once stable
general enable PSRemoting shortcut
stubs for Add-Printer etc.
- net view \target /all
proper HTML clipboard building from current GUI output pane
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