MobileRead Forums - View Single Post - Adding a limited Automate Feature To Sigil

KevinH · 08-13-2021, 10:54 AM

FYI, I started the process of making selected tools from the MainWindow return values so that they can be used in the automate lists:

Right now these include:

UpdateManifestProperties
Save
WellFormedCheckEpub
MendPrettifyHTML
MendHTML
ValidateStylesheetsWithW3C
RepoCommit (Checkpoint)
GenerateNCXGuideFromNav
RemoveNCXGuideFromEpub3
DeleteUnusedMedia
DeleteUnusedStyles
StandardizeEpub (Restructure Epub to Sigil Norm)
SplitOnSGFSectionMarkers
AddCover

This leads to a couple of questions:

1. How should we deal with intl Sigil user/devs in these automate lists if at all?
In other words should we be treating them like shell/bat commands which are all English based like most programming and scripting languages?

2. Should shorthand notations for automate commands instead of actual C++ routine names (as provided above) be used (think unix like short command line tools)

3. How to deal with non-modal dialogs like Search Editor / SpellCheck, Edit TOC, Reports, Edit Metadata, etc? Should we wait until these dialogs are closed by the user before proceeding to the next command in the automate list?

4. How to deal with running a specifically named saved searches with replace? Or do we punt on this and require a plugin to do those types of things in an automated setting.

Perhaps the best way to deal with this is to make a mac/Win builds available for testers to report back before going any further. If these features turn out not to be that usable for real power users/devs it will end up being a waste of time for little to no gain.

Any Thoughts?

08-13-2021, 10:54 AM	#29
KevinH Sigil Developer Posts: 8,816 Karma: 6000000 Join Date: Nov 2009 Device: many	FYI, I started the process of making selected tools from the MainWindow return values so that they can be used in the automate lists: Right now these include: UpdateManifestProperties Save WellFormedCheckEpub MendPrettifyHTML MendHTML ValidateStylesheetsWithW3C RepoCommit (Checkpoint) GenerateNCXGuideFromNav RemoveNCXGuideFromEpub3 DeleteUnusedMedia DeleteUnusedStyles StandardizeEpub (Restructure Epub to Sigil Norm) SplitOnSGFSectionMarkers AddCover This leads to a couple of questions: 1. How should we deal with intl Sigil user/devs in these automate lists if at all? In other words should we be treating them like shell/bat commands which are all English based like most programming and scripting languages? 2. Should shorthand notations for automate commands instead of actual C++ routine names (as provided above) be used (think unix like short command line tools) 3. How to deal with non-modal dialogs like Search Editor / SpellCheck, Edit TOC, Reports, Edit Metadata, etc? Should we wait until these dialogs are closed by the user before proceeding to the next command in the automate list? 4. How to deal with running a specifically named saved searches with replace? Or do we punt on this and require a plugin to do those types of things in an automated setting. Perhaps the best way to deal with this is to make a mac/Win builds available for testers to report back before going any further. If these features turn out not to be that usable for real power users/devs it will end up being a waste of time for little to no gain. Any Thoughts? Last edited by KevinH; 08-14-2021 at 12:06 PM.