-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor out Nodejs related code so it can run in browser #38
Comments
but will it be able to generate PDFs ? |
I guess iFrame will work. iframe.focus();
iframe.contentWindow.print(); https://plungjan.name/SO/testprintiframe.html This requires the user to click |
Another way:
|
Maybe one day, author of a paper only need to send a link to his editor. |
Do you know overleaf ? Its basically that, but for latex |
It will be different if we are using web technology.
|
Definitely something I want to explore, but it would be quite a different project, and at the moment I dont like that the user would need to go through the print-page interface, possibly redefining paper size etc. everytime. It would also be some work to let users manage file and assets in their browser. Other drawbacks would be that you couldnt edit an image file in gimp/inkscape, and see real-time changes in your PDF. But I agree that it would be orders of magnitude more accessible than the current solution. |
I think it should be still standalone and available as Node.js solution with headless Chrome (puppeteer) in the background. Personally I see not much sense in migrating the codebase and let this run in all browsers. |
One good aspect would be user conversion, since you could get started on an example in seconds, nothing to install. You could also make a custom UI with relaxed-specific features. But yeah, huge project. |
Could be easily done with React which can run Node.js code in the background and consume Node.js modules. So basically we have a feature request for a different implementation (which needs proper planning and evaulation of possible solutions). |
...with the problem that the main feature (automatic PDF generation with custom margins, footers, headers, etc.) is certainly not doable from a browser. |
Let me close this till there are out-of-box solutions to manage folders of assets in service worker(like stackblitz-core), html-to-pdf generator (maybe pdfjs but doc said it's deprecated) and assert editors (for images). |
See https://stackblitz.com/, it's possible to run a dev server and an editor in the browser's service worker.
I think it's possible to build an online ReLaXed editor if all nodejs related code is refactored out.
The text was updated successfully, but these errors were encountered: