Vincent Spallek

My feedback

  1. 268 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    45 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Vincent Spallek supported this idea  · 
  2. 34 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Vincent Spallek supported this idea  · 
  3. 136 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Vincent Spallek commented  · 

    CSS options should be supported.

    Vincent Spallek supported this idea  · 
  4. 66 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Vincent Spallek commented  · 

    Another aspect to consider is the philosophy of OOCSS:

    1. Create design tokens (color, font specs)
    2. Utilizing these tokens, create CSS classes as defined by OOCSS. Example: protective-margin for a margin around clickable elements; clickable-area for a minimum width and height and mouse cursor; button-background for the colors for the different states. Then we can create another class button-background--emph for an emphasized button without having to repeat all the other specifications that won't change
    3. Combine those classes to build-up the elements. With this approach, they will become much more consistent with little effort <button class="protective-margin clickable-area button-background">Normal button</button>, <button class="protective-margin clickable-area button-background--emph">Important button</button>
    4. Use those elements to build-up the screens and flow

    It would be great if something like this would be supported by XD. Other Adobe tools like InDesign allow it to assign one style (e.g. paragraph style) to each element, but not several. Even in Dreamweaver, I can only pick one CSS class when using the design view.

    Related: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/13245423-import-html-from-url-as-editable-static-content

    Vincent Spallek supported this idea  · 
    An error occurred while saving the comment
    Vincent Spallek commented  · 

    One example for a design system: https://vueds.com/

  5. 181 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    39 comments  ·  Adobe XD: Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →

    Kenneth, would you mind breaking out SWF import as a separate feature request? That way people can gauge whether people want both or which one is higher priority. I’ll remove SWF from the title here so it’s focused specifically on HTML import.

    An error occurred while saving the comment
    Vincent Spallek commented  · 

    It definitely is related. If importing HTML, JS and CSS, three aspects might be important:
    - Support build automation: being able to hand over a list of components that consistently gets (re‑)imported, instead of having to select them manually in the UI
    - Retaining the component hierarchy (component A is composed of component B and C)
    - Understanding properties: A button's label can be edited or its icon or width, but not its colors or height

    An error occurred while saving the comment An error occurred while saving the comment
    Vincent Spallek commented  · 

    I want to be able to automatically (re-)generate an XD UI kit from my existing Web UI component library so that the components the designers use are always in sync with what the developers use to implement the solution.
    This includes the possibility to update existing symbols in my XD files if they have changed in my web component library.
    There are numerous solutions that generate a documentation from existing UI components, couldn't this approach be extended to also generate XD symbols?

    Vincent Spallek supported this idea  · 
  6. 781 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Vincent Spallek supported this idea  · 

Feedback and Knowledge Base