|
Hi varlog,
user_none added a few good ideas
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
If we did that, it may make the registration process gui part easier as the user provides a zip for each "script" that is stored in the official scripts home that either Sigil or the launcher could search.
All of this can be implemented later in stages, I would like to focus on getting what we have merged together and working properly and then add the bells and whistles.
When I get free time I will focus on adding a few support routines to Resources, FolderKeeper and MainWindow (I think that is where tab flushing is done), to make flushing to disk, and integrating results easier.
Take care,
Kevin
|