Quote:
Originally Posted by KevinH
...
1. each target script gets its own directory
2. all the targets python code is stored there along with a script info.xml file
3. each scriptinfo.xml file could have the following info in it
- Script Type (edit, input, output)
- Name
- Version
- Description
- Programming Language/Interpreter
- Programming Language/Interpreter version needed
- List of dependencies (We won't check the list but it's informational
so a user knows what they need installed).
- Name of target module to invoke file to run from launcher
...
|
Have you actually tried to run DGSM? All those things are already there - well, not the red ones, the green one I've added now.
Manifest Id error was my mistake. I do test outside of Sigil but grabbed the files from it - and did it too early in this case.
I tried to groak your wrapper but alas: not enough python between my ears. Which brings me to one of my second thoughts. I was able, using guesses and stackoverflow, to write some things in python which did something I set out to do. I'm not able to do it with your wrapper in between. It is probably for the best - one should really learn the language first and than write scripts.
But what remains is:
1. your wrapper needs proper documentation.
2. the call to execute script will depend on interpreter (or on: do we have wrapper for this interpreter?).
Before writing proper documentation could you implement New UUID/Smarten it just for me to have something to lean on?