Kent West

My feedback

  1. 304 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  SMA (K1000) » Managed Install  ·  Flag idea as inappropriate…  ·  Admin →
    Kent West commented  · 

    Make online scripting even more general:

    On the online script page, have radio buttons (or a pull-down), with the following options:

    * This is a batch script
    * This is a Powershell script
    * This is a bash script
    * This is a python script
    * This is a Ruby script
    * This is a VB script
    * Let the OS figure out the type of script, based on the file extension

    There can be a disclaimer that the appropriate interpreter/engine be on the target first. The radio-buttons might even have a field next to them to specify the path to the interpreter/engine on the target machine. Just having this field alone might eliminate the need for the radio buttons:

    Path to language engine/interpreter: %winapppath%\python\python3.7
    or
    Path to language engine/interpreter: {built-in batch interpreter}
    or
    Path to language engine/interpreter: %windir%\sysnative\ruby
    or
    Path to language engine/interpreter: {built-in VBS interpreter}
    etc

    In essence, the "Script Text" field would just become a mini-editor for all sorts of language engines, instead of just batch or shell as it essentially is now.

  2. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SMA (K1000) » Scripting  ·  Flag idea as inappropriate…  ·  Admin →
    Kent West shared this idea  · 
  3. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SMA (K1000) » Scripting  ·  Flag idea as inappropriate…  ·  Admin →
    Kent West supported this idea  · 

Feedback and Knowledge Base