To drive adoption, let's change the way we think about Dialogshell. Previously, we viewed this as an application suite built in the powershell language, let's regear this.
Going forward, we will view Dialogshell as a powershell module, and will restructure the installation and use around this scenario ~ since this is no longer a collection of exectuable files that output executable files this just makes more sense.
As part of this, may want to consider rebranding some of the utility of the module ~ right now Dialogshell exists in an awkward space. Let's try and conform a bit.
To drive adoption, let's change the way we think about Dialogshell. Previously, we viewed this as an application suite built in the powershell language, let's regear this.
Going forward, we will view Dialogshell as a powershell module, and will restructure the installation and use around this scenario ~ since this is no longer a collection of exectuable files that output executable files this just makes more sense.
As part of this, may want to consider rebranding some of the utility of the module ~ right now Dialogshell exists in an awkward space. Let's try and conform a bit.