News for hackers. Stuff that matters.

A comment on Painting with Code: Introducing our new open source library React Sketch.app. Parent comment

Re:Painting with Code: Introducing our new open source libra... by pavlov on Tuesday April 25, 2017 @02:39PM (#14196689)
To go the other way -- generating React code from Sketch -- you can use React Studio:

https://reactstudio.com

It has a Sketch plugin that does a rather competent job of converting Sketch layers/groups into components. (For example, you can prefix a Sketch group with "c:", and React Studio will interpret it as a component.)

Here is a live video demonstrating the Sketch -> React Studio -> React code workflow: https://www.youtube.com/watch?v=Rfd7zmlFZw8 (It's in realtime with detailed explanations, so it runs about 40 minutes.)

Disclaimer: I wrote a pile of code for React Studio.

[ Parent | on HN ]
Re:Painting with Code: Introducing our new open source libra... by IOT_Apprentice on Tuesday April 25, 2017 @11:26PM (#14200209)
If reactstudio could support loading in react form, components, color themes etc al from the hundreds of react themes sold from places like envato, themeforest, etc. then a whole class of UI mock ups could be built. Example themes:

https://themeforest.net/item/material-design-reactjs-admin-w...

or

https://genesisui.com/demo/?theme=prime&version=react

[ Parent | on HN ]
Re:Painting with Code: Introducing our new open source libra... by perfmode on Tuesday April 25, 2017 @03:36PM (#14197204)
It seems like the logical conclusion is to create a two-way data binding in a live-coding environment.
[ Parent | on HN ]
Re:Painting with Code: Introducing our new open source libra... by sorenbs on Tuesday April 25, 2017 @06:03PM (#14198522)
The idea behind React Studio is awesome.

I think it would be super cool if React Studio could automatically create a GraphQL api based on the structure of the component data.

We are already doing small experiments in this direction at Graphcool (for example graphql-up https://www.graph.cool/graphql-up/)

Do you think anyone at Reract Studio would be interested in talking more about this? They can ping me at [email protected] :-)

[ Parent | on HN ]
Re:Painting with Code: Introducing our new open source libra... by pavlov on Tuesday April 25, 2017 @07:13PM (#14199075)
Sounds really great, I'll pass on your contact info!
[ Parent | on HN ]
Re:Painting with Code: Introducing our new open source libra... by salimmadjd on Tuesday April 25, 2017 @03:08PM (#14196980)
Interesting. But, the monthly Adobe-esque subscription fee is a turn off.
[ Parent | on HN ]
Re:Painting with Code: Introducing our new open source libra... by pavlov on Tuesday April 25, 2017 @03:11PM (#14197005)
That is of course something that can change. What kind of pricing would you prefer?
[ Parent | on HN ]
Re:Painting with Code: Introducing our new open source libra... by pknopf on Tuesday April 25, 2017 @03:33PM (#14197182)
Any kind of one-time pricing would be great.

Ideally, with a perpetual license with 1-year of free upgrades.

[ Parent | on HN ]
Re:Painting with Code: Introducing our new open source libra... by pavlov on Tuesday April 25, 2017 @03:58PM (#14197406)
That seems definitely possible. I think what the team was worried about is sticker shock -- $19/month might translate to something in the region of $200-250 for the scheme you propose. Does that sound bearable?
[ Parent | on HN ]
Re:Painting with Code: Introducing our new open source libra... by redindian75 on Friday April 28, 2017 @01:32PM (#14221368)
perpetual license is what scared me off as well. Ideally $199 with 1 year upgrades. As long as it keeps working after 1 year I am sold.
[ Parent | on HN ]
Re:Painting with Code: Introducing our new open source libra... by sorenbs on Wednesday April 26, 2017 @05:09AM (#14201574)
Thanks!
[ Parent | on HN ]
Re:Painting with Code: Introducing our new open source libra... by trakout on Wednesday April 26, 2017 @09:56AM (#14202950)
yes!
[ Parent | on HN ]