Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'batch builder'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Staff and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.5 Beta New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 1 result

  1. Hello, it would be really awesome if AD could add a simple, generic Batch Builder that can export coordinates for Artboards and Slices and basic information for exported object layers to either JSON or XML: Any slice Coordinates Slices created from objects Stroke: Thickness, Color & Alignment Fill: Color Slices created from text frames (assuming a constant style for the entire frame) Family Weight Size Alignment Bonus points for any additional properties (everything in the contextual context toolbar and the effects panel may be of interest) That would dramatically increase the usefulness for UI design in collaboration with development teams! We're currently trying to use the Spine JSON-Export to automatically create design specs for our dev team, but the proprietary structure (origin in bottom left, anchor at center of any object, no text support) makes it kind of finicky. It's awesome that it's there, but a few more attributes would make it much more useful for us. If it's too time intensive to make a pretty JSON/XML-file, I'd also settle for Batch Builder that prints a parsable ToString()-Dump of the document tree .
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.