Skip to content
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

CLI export option #309

Open
BotiKepi opened this issue Oct 7, 2024 · 1 comment
Open

CLI export option #309

BotiKepi opened this issue Oct 7, 2024 · 1 comment

Comments

@BotiKepi
Copy link

BotiKepi commented Oct 7, 2024

Hi,
I'm not an every day user of QElectrotech, but I do appreciate it (thanks for that !).
Yet, I'm used to version control my files (with git), even files such as .qet .

Having the ability to export pdf (or such graphic output) through CLI let the ability to graphically enlight differences when making a git diff, before committing for instance (the what-have-I-done-since-last-commit syndrom ;-) ).
This can be done using git attributes, which let us automate the process : exporting 2 versions of graphic rendering -- pdf, png, svg ...-- and diffing the graphics (in various ways).

I use that process with KiCad (PCB design) : it's not perfect, but quite convenient.

Hence, having a CLI export option (like for instance, --export-pdf) would be appreciated .

This is somewhat related to #162 , yet the need here is smaller : no need for a scripting language, "just" restricted actions such as export, through options (and without launching GUI).

Yeah, sorry for the "just" word, I don't know how big effort this would take, but I guess this is not a small piece of cake.

@pkess
Copy link
Contributor

pkess commented Feb 18, 2025

I agree with @BotiKepi . It would be very nice to have the possibility to export project contents like the full schematic as pdf. Another nice thing would be to export all connections as a list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants