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

SVGPCB integration improvements #349

Open
ducky64 opened this issue Apr 30, 2024 · 0 comments
Open

SVGPCB integration improvements #349

ducky64 opened this issue Apr 30, 2024 · 0 comments

Comments

@ducky64
Copy link
Collaborator

ducky64 commented Apr 30, 2024

From building several layout templates, improvements could be made to make the whole process easier:

  • Consistent naming API, that matches the pathname of the HDL component. Two parts:
    • Hierarchical naming - the returned object should be a scope and automatically handle adding the container's pathname prefix as needed - the function code should not deal with this.
    • Character remapping - e.g., replace , with _, must match the behavior in the netlist compilers.
  • Generate consistent KiCad tstamps, to allow proper netlist updates in KiCad layout. Either tstamp generation could be part of a compiler pass and be part of the IR (unclear how this would work with the current structure - maybe passes can introduce new parameters?) or add a tstamp generation helper to SVGPCB.
    • Probably not possible to generate tstamps as part of the SVGPCB layout template generation pass, since it would need to name each individual element.
  • Some graphical library to avoid needing to add primitives like vector-add in each layout template
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

1 participant