Doesn't work on Firefox
Also doesn't work on Safari. The "error" message tells you to use Chrome instead (or ask for an app download).
Launch HN: Pagedraw (YC W18) – Compile UI Mockups to React Code
11–20 of 125 posts
Re: Launch HN: Pagedraw (YC W18) – Compile UI Mockups to React Code
#12Why don't you support Firefox? > You can import the mockups from Sketch or Figma How do I import Figma designs? I tried the Sketch import, doesn't work through that. Excited to use this. Congrats on your launch.
We haven't launched the Figma integration yet, (it's behind a config flag,) but it's coming soon! Sketch should be working today. Could you email us at team@pagedraw.io if it's not?
Re: Launch HN: Pagedraw (YC W18) – Compile UI Mockups to React Code
#13I created a text field, deleted it, and added another ending up with a slightly mis-defined UI element. The name in the UI is Text 4, the prop is text3 and the css class is text_4. That said, I’m totally in love. Can I just ask for Typescript generation, please? (UPDATE: My god it’s already there in the full version - Thank you!)
We're working on simplifying the common case usage for props, but they are complicated right now because we're going for giving you the full flexibility of React. What that means for us is that props have 2 parts: their definition and their usage. Go into the CODE tab of the sidebar and you'll see the prop definitions on top and the usages below. When you create a new binding by clicking "make dynamic", we automatically create both a definition and a usage for you. We don't do a great job of keeping the names in sync because we expect you'll rename the prop (and update the usage).
Re: Launch HN: Pagedraw (YC W18) – Compile UI Mockups to React Code
#14I created a text field, deleted it, and added another ending up with a slightly mis-defined UI element. The name in the UI is Text 4, the prop is text3 and the css class is text_4. That said, I’m totally in love. Can I just ask for Typescript generation, please? (UPDATE: My god it’s already there in the full version - Thank you!)
I’ve installed the pagedraw-cli app but am getting crashes because my project is on the D:/ drive and it’s inheriting the drive specifier and looking for my C:/users folder under D:/users. Super excited to go deeper with this.
Re: Launch HN: Pagedraw (YC W18) – Compile UI Mockups to React Code
#15Is Vue support planned?
Re: Launch HN: Pagedraw (YC W18) – Compile UI Mockups to React Code
#16React-Native-Web plz :D
Re: Launch HN: Pagedraw (YC W18) – Compile UI Mockups to React Code
#17Congrats on the launch guys! Really excited to play around with this.
Re: Launch HN: Pagedraw (YC W18) – Compile UI Mockups to React Code
#18React-Native-Web plz :D
coming soon! :D
Re: Launch HN: Pagedraw (YC W18) – Compile UI Mockups to React Code
#19Is Vue support planned?
yes, depending on demand. Get your friends / coworkers to message us if they need it too
Re: Launch HN: Pagedraw (YC W18) – Compile UI Mockups to React Code
#20Have you fully consider the Designer's side of this? I feel that to be successful and bridge the gaps between those two mental models you also need to onboard the designers so they can help with generating the right type of mockup (or at least the kind that will help a developer using Pagedraw get the closest to a 1 to 1 code export).
The reason why I ask is that I tried importing several semi-complex but not uncommon (structure wise) files and I got an error saying that I should make sure that the file is correctly formed.
That right away is bad UX. If the designers need to reformat or change the behavior of their files, then they need to be part of the user journey. Right now there's nothing of that as far as I can tell.