13 results found
Thanks for your clarification! I’ll leave this open with your comments.
An error occurred while saving the commentAnonymous commented
First, this VSCode extension seems to be a lot more complicated than it needs to be. We just need to add 2 textboxes for the components, 1 for links, and 1 for description.
To give a more specific example, we use VueJS along with Quasar Framework. Then, I design a component based on the component inside the Quasar Framework. For example, this stepper component: https://quasar.dev/vue-components/stepper
So there's 2 things that can happen after the dev handoff.
1. The dev already knows what component to use and the implementation went smoothly.
2. The dev doesn't know that this is already a component in quasar, and so the designer would need to let the devs know which component is the design based on, and what properties would be needed to set in order to achieve the desired design. As the project gets bigger, this process will be unproductive and repetitive.
To solve this, the designer should be able to give a link to the component's documentation, give notes, descriptions, or any instruction that will point the devs to the right direction. This way, the designer would only need to specify the documentation in the components library or the master file of the components, then everytime the designer uses that component, it will have the documentation already attached.
So for the stepper example
1. I would like to give the component a link which is: "https://quasar.dev/vue-components/stepper"
2. I used the stepper's vertical layout, dark mode, and flat properties, so to help the devs, I want to give instructions saying something like: "vertical=true, dark=true, flat=true"
Also, not every developer uses VSCode. In my case, most of them use IntelliJ.
Last, this should be a very simple addition to components that will have a bigger impact for the development handoff, compared to the VSCode plugin, which relies mostly on VSCode and the developer's understanding of design system packages. Adding 2 textboxes for a link and a description would cover more cases where different teams of developers are using different frontend frameworks, while using the IDE of their choice.Anonymous shared this idea ·
2,872 votesfeature-under-review · 148 comments · Adobe XD: Feature Requests (Read-Only) » 02 : Prototype mode · Admin →
3,558 votesfeature-under-review · 316 comments · Adobe XD: Feature Requests (Read-Only) » 02 : Prototype mode · Admin →
Reopening the feature request, based on feedback.
Note: there’s a limited version of this feature already available. If you select an existing piece of text and then leave it selected while you use the Text tool to create new text, its style will match the piece of text you had selected.
3,888 votesfeature-in-the-backlog · 516 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →
1,111 votesfeature-under-review · 49 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →
1,774 votesfeature-under-review · 81 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →
We’ve started working on multiple fills and borders, with plans to extend to this multiple shadows in the future.