Reading Web has a hard requirement to support a PDF Table of contents with page numbers for any new PDF generation service that will replace OCG in the collection extension.
wkhtmltopdf has support for the ToC feature required by product, while Electron does not. One aspect that has not been quantified is how difficult it would be to implement the PDF ToC feature into Electron. ToC requirements here: https://www.mediawiki.org/wiki/Reading/Web/PDF_Functionality#Books
As Electron is already available in an extension, it would be good to quantify this effort before selecting a different solution.
Some questions to answer:
- What is the time estimate involved in adding these features to Electron by wrapping the service?
- In addition to evaluating the effort of adding these features by wrapping electron, it also important to evaluate extending Electron itself. The reason being is that we may have an issue with needing to generate 2 PDFs.
- Do we really need to render twice to get the PDF?
- If so, is generating 2 PDFs that much of an issue? Performance wise, complexity wise?