VASL Templates
==============

I'm trying to get VASL Templates to run on my laptop so that I can
create nice setups for Advanced Squad Leader. As it turns out, I have
to use pipx because that automatically creates virtual environments
for me, as far as I understand.

    cd src
    git clone https://code.pacman-ghost.com/public/vasl-templates.git
    cd vasl-templates
    pipx install .

As it turns out, this is not enough:

    Traceback (most recent call last):
      File "/home/alex/.local/bin/vasl-templates", line 5, in <module>
        from vasl_templates.main import main
      File "/home/alex/.local/pipx/venvs/vasl-templates/lib/python3.11/site-packages/vasl_templates/main.py", line 19, in <module>
        import PyQt5.QtWebEngineWidgets
    ModuleNotFoundError: No module named 'PyQt5'

So now you need to install PyQt5 into the virtual environment used by
vasl-templates:

    pipx inject vasl-templates PyQt5

Next error:

    Traceback (most recent call last):
      File "/home/alex/.local/bin/vasl-templates", line 5, in <module>
        from vasl_templates.main import main
      File "/home/alex/.local/pipx/venvs/vasl-templates/lib/python3.11/site-packages/vasl_templates/main.py", line 19, in <module>
        import PyQt5.QtWebEngineWidgets
    ModuleNotFoundError: No module named 'PyQt5.QtWebEngineWidgets'

Fix:

    pipx inject vasl-templates PyQtWebEngine

And now it works at last! 😅

​#Advanced_Squad_Leader

@Sandra@idiomdrottning.org recommends fpm, i.e. building a Debian
package and installing that, instead.

> The awesomest part is that they don’t go in their own venvs or
> dockers or chroots or their own li’l boring & redundant worlds.
> Instead it’s all according to traditional Debian philosophy, all
> part of the same file system with no redundancy.