Open begna112 opened 3 years ago
Nothing have changed for Windows users since VS Preview has been uploaded to GitHub, but that aside.
VSP is quite raw in this regard. Those are minimal steps to get it working:
pip install -r requirements.txt
seems the most convenient way.python run.py
, supplying path to .vpy
script.Further steps depends on your workflow:
a) to make VSP available in any terminal, you can create a script named vspreview
that forwards all the arguments to run.py
wherever you placed it, and put this script into some directory added to PATH
b) (my personal favorite) for VS Code, you can create a launch task, that opens file from active editor in VSP. It'd be along the lines of:
{
"name": "Current File",
"type": "python",
"request": "launch",
"console": "integratedTerminal",
"program": "C:\Users\Admin\Downloads\vapoursynth-preview\run.py",
"args": [
"${file}"
],
"showReturnValue": true
}
See below how to improve this approach.
Going through your items:
git clone
and pip install -r requirements.txt
.vpy
with the script you create, but I'd say there's much more sense in associating it with VS Code
Can you create a step-by-step walkthrough for how to install this?
Been trying to figure it out with someone who has an older version installed and it doesn't seem to work the same.
As this isn't a normal extension (or doesn't appear to be), it's not exactly self-evident how this should be setup without instructions.
Items that would be good to know:
Items which might be complicating this for me: