XD already allows users to paste appearance only, and I used to think it'd be nice if those styes could be defined as an abstract component and reused when creating variations of a component The procedure would be something like this.
1. define a set of styles as a style-only-component (or whatever you call it).
2. apply it to a master component in order to create :
a) a sub-master component (like implementing an interface to a class in Java), or
b) a state of the component (like layer effect in Photoshop)
In this way, it might be easier to maintain consistency of hover state across buttons for example.
I agree too! There are popular scenarios that require to expand the bounds of a component without scaling. Actually I'd expect adding a new element to outside of an existing component's bounds automatically expands the bounds just like groups (or symbols).
1 voteAnonymous shared this idea ·
We’re working on a visual versioning system for XD documents. You could see a preview here: https://youtu.be/pf35qphKOWE?t=1h7m51s
(as my request "Git friendly linked symbols" has been merged with this)
I was not asking version control. My request was about flexibility of workflow with linked symbols. For example, Photoshop looks for four locations to find a source file and keeping relative path is enough to keep objects to be linked.
Could you undo the merge as I believe my request had got some votes.
I really liked the linked symbols as an MVP! As one of the next steps, what I'd like to see is a better support for a Git based workflow such as,
- manage all xd documents with Git including a single source of truth
- when checked out, all linked symbols are automatically linked to their originals
When I tried links were broken and had to be fixed manually. My feeling is using Git (or other version control system) is not rare among XD users, and many people will benefit from this enhancement.Anonymous supported this idea ·