No,
for all 3 script types, Sigil passes in real ebook path, path to temp directory Sigil owns, script type, and path to target script. the real ebook path is only ever read from. All writes go to temp directory which Sigil uses to validate from and update it's own files upon return of launcher.
when Sigil only wants to pass in selected resources and not full book, it creates a temp directory to act as ebook root and fills it with just the selected resource and then passes that as ebook root.
Sigil must own and create/destroy output temp directory so it exists after the launcher process ends.
The launcher copies on write to output directory and has all the iterators to access any class of resource easily, so no need to send long lists of text XHTML files.
Hope this explains things .
KevinH
Last edited by KevinH; 08-08-2014 at 10:38 AM.
|