Thanks to the @FEAnalyst who prepared the new PrePoMax documentation, it is now available online at:
2 Likes
Thanks Guys, as a newbie is there a what’s new somewhere? It is often nice to be able to home in new features.
1 Like
Sure, on this page: https://prepomax.fs.um.si/version-2-4-0/
Thanks, the “News” page had me fooled as the Black Bold header Titles are in fact hyperlinks to the what’s new. Feeling slight stupid as without a link that page would be strange so I should have done some clicking. It would be better if a Hyper link style was used or add a specific link tag in the Paragraph text.
Thank you @Matej and @FEAnalyst - great work as always 
! Would it be helpful to host the documentation in a GitLab/GitHub repo in a format that’s more friendly for edits (e.g., Markdown)? That could make it easier for others to contribute special cases and workarounds that come up in these threads but don’t always make it into the doc.… just a thought.
1 Like
The documentation is written in LaTeX and requires a special editor/compiler so indeed not very user-friendly for collaboration. Rewriting it to another format at this point is probably not worth it though. It’s a single document, not structured for a wiki (like the one used by FreeCAD).
For now, maybe we could collect somewhere suggestions for more sections. However, the idea was that it’s a rather concise document focusing on the PewPoMax interface usage while CalculiX-related stuff, pre- and postprocessing workflows, examples and other practical aspects are mostly provided as YouTube tutorials (also referenced in the documentation). Nowadays, this seems to be the most desired form by users. Written tutorials aren’t so welcome anymore, especially for user-friendly CAx software with modern interface.
With that said, of course, I don’t mind establishing a GitHub or GitLab repo where users could submit issues, discussions and PRs to contribute to the LaTeX-based documentation. In fact, it might be a good idea and I was thinking about it too (also in order to allow for more translated versions). Let’s just make sure the manual stays as a clear reference for users to quickly check some commands/options and let’s not dilute it too much with other information.
You are right…
Absolutely, I was thinking on the same. Whenever you want to go in that direction, I will try to support from my side.
A side note on LaTex, I’ve been trying to move away from it and found that markdown is doing a pretty good job handling most of my old latex files and trying to have them in a more convenient format. Most of my colleagues are moving also away from LaTex, or let’s say using it as a “intermediate” step to generate nice pdfs.
1 Like