Skip to content

Export clean SVGs with user-specified metadata #567

Open
0 of 1 issue completed
Open

Description

@psvoboda76

This is the following roadmap item:

capture

Activity

  1. added this to the Sprint 15 (upcoming) milestone on Mar 16, 2022
  2. Keavon commented on Mar 16, 2022

    @Keavon
    Member

    I've envisioned that this, along with other SVG metadata, could be included in a Properties panel section called "SVG Metadata" which includes a place to give it a custom ID, class, style, animation data, etc. I've never loved the automatic translation of layer name into a hyphenated ID that is used in other software since I usually have to go and manually strip that out when cleaning up the SVG syntax. But doing this in a custom properties section would make that optional and give the user more control. Does that seem like an improvement, or would it be disadvantageous over your proposal (@psvoboda76) in ways I haven't thought about?

  3. psvoboda76 commented on Mar 17, 2022

    @psvoboda76
    Author

    I fully agree, having a separate section "SVG Metadata" in the Properties panel is a better idea. It definitely is the right solution. Thank you.

    I've envisioned that this, along with other SVG metadata, could be included in a Properties panel section called "SVG Metadata" which includes a place to give it a custom ID, class, style, animation data, etc. I've never loved the automatic translation of layer name into a hyphenated ID that is used in other software since I usually have to go and manually strip that out when cleaning up the SVG syntax. But doing this in a custom properties section would make that optional and give the user more control. Does that seem like an improvement, or would it be disadvantageous over your proposal (@psvoboda76) in ways I haven't thought about?

  4. changed the title [-]SVG export - add id, export text as text element, specify dec. precision[/-] [+]SVG export with user-specified metadata[/+] on Apr 21, 2022
  5. changed the title [-]SVG export with user-specified metadata[/-] [+]Clean SVG export with user-specified metadata[/+] on Apr 21, 2022
  6. removed this from the Sprint 16 (upcoming) milestone on May 14, 2022
  7. psvoboda76 commented on Dec 19, 2022

    @psvoboda76
    Author

    Hi,

    Are there any time plans for implementing this option? I want to help. However, I am react js developer and never worked with vue before. Is there some design idea about the "SVG Metadata" pane? Eg. what it should contain aside of the id? Is someone working on it already I can contact and help?

  8. Keavon commented on Dec 19, 2022

    @Keavon
    Member

    Hi @psvoboda76, that will all be Rust code that works within our node system as part of a not-yet-built "Attributes" system that is used to send metadata alongside data through the node network (which is why I marked this as blocked until we have that). You'd be welcome to learn Rust and help us build that, but I might suggest the way you can help speed up the inclusion of this feature would be taking on some other tasks that generally improve the usability of the Graphite editor as a whole. If you're interested in doing that, let me know and I can suggest some options for tasks that would be beginner-friendly and predominantly focused around frontend code.

  9. changed the title [-]Clean SVG export with user-specified metadata[/-] [+]Export clean SVGs with user-specified metadata[/+] on Mar 4, 2023
  10. moved this to Blocked, Awaiting Full Node System in Task Boardon Mar 18, 2023
  11. moved this from Blocked, Awaiting Full Node System to Longer-Term in Task Boardon Apr 27, 2023
  12. moved this to Blocked in Task Boardon May 31, 2023
  13. moved this from Blocked to Medium-Term in Task Boardon Sep 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    • Status
      Medium-Term

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions