Fix critical bug

[davidpomerenke]

Fix critical bug Can't locate scigen.pm in @inc [...] at ./make-latex.pl line 21. & similar bugs at running ./make-latex.pl (as described on the homepage) by including current directory as library.

[ariccio]

Heh, did you just casually port this to nodejs? And here I was wondering if it would be worth figuring out perl and deploying it to heroku with minimal changes. Excellent work!

[davidpomerenke]

Yes! Thank you for your nice words :)

It is possible to run the main part in the browser, without any server involved. There is some more explanation and a demo at scigen.js.

The bottleneck of the browser-only approach is the creation of the PDF from the Latex code that is produced by scigen.js. While the Latex core is ported to Javascript, Bibtex (for the bibliography) and Postscript Ghostscript (for the figures) are not. I managed to circumvene Bibtex but did not yet find the time and motivation to circumvene Ghostscript. Therefore, in the latest commit, I have disabled the generation of new figures (instead linking some random pre-made figures that are not tailored towards the topic of the paper, which is suboptimal).

As long as there is no workaround for Ghostscript, it may still make sense to run scigen.js on a server that also runs Latex (including Ghostscript!) -- I don't know if this is possible on Heroku?

For this, you could use the scigen.js version on NPM, where, I believe, the generation of new figures is still enabled. Perl would not be needed, then.

Edit: It's about Ghostscript, not about Postscript.