71–80 of 125 posts
Do you have plans to open source the backend ? So devs over time can make it even smarter for all sorts of use cases ?
Open source and profitable are orthogonal things. You can still be profitable and build a solid product with a raving community.
Dunno how possible it is, but I would definitely pay for a vscode plugin to have a native app like experience.
Design -> Code is definitely a big problem. Creation time is one, but updating should be easy too.
Also I would love a reverse, code -> Design output as well, so it's a two way tweaking experience, where both design and code are always in sync. i.e React -> Sketch
You talk a lot about the compiler backend. Suppose we use a different UI library other than the big ones like React and Angular. How can I plug in my custom backend ? Do you have plans to open source the backend ? So devs over time can make it even smarter for all sorts of use cases ? Open source and profitable are orthogonal things. You can still be profitable and build a solid product with a raving community.
We're huge on backwards compatibility (and think everyone should be), which is why we don't want to expose something we haven't stabilized yet. We'll have a way to export our just-before-codegen internal representation (shame on me for forgetting the PL term) once it settles down a bit. It's very much like a DOM, so there's not too much craziness there.
We'll be launching a bunch more backends in the coming weeks, so there's a good chance we'll have first-party support for your favorite framework anyway :)
Really really like that you used VSCode's monaco editor. Dunno how possible it is, but I would definitely pay for a vscode plugin to have a native app like experience. Design -> Code is definitely a big problem. Creation time is one, but updating should be easy too. Also I would love a reverse, code -> Design output as well, so it's a two way tweaking experience, where both design and code are always in sync. i.e Rea…
Native VS Code integration is already here! The “3 screens” you see (design, code, preview) are just there for the demo— only the design editor on top is part of Pagedraw. You get to use your regular text editor (VS Code included), and localhost env if you use the full version and install the CLI https://documentation.pagedraw.io/cli/
> Design -> Code is definitely a big problem. Creation time is one, but updating should be easy too.
Updating is super easy if you do the updates in Pagedraw. Since everything is component based, you should never touch the generated code. All the code you write goes in adjacent components that import and are imported by Pagedrawn components. You never need to roundtrip, because you never need to edit the generated code
It would be helpful to know what those limitations are before spending too much time and only to find out it won't work for us.
I'm really curious how accurate the tool generates responsive designs. I feel like, it would have it's limits. It would be helpful to know what those limitations are before spending too much time and only to find out it won't work for us.
We give you controls to annotate your design with layout behaviors. The css we generate is 100% accurate to the constraints you specify, but our constraint system doesn't capture 100% of desired layouts (yet!)
We have 2 ways for you to control responsiveness: A flexbox-y constraint system, and media queries (Screen Size Groups). They're roughly the same controls html/css give you, though hopefully presented in a cleaner manner.
The tool has great potential, if u can address the UX market than the dev market. Devs have many many tools they wont give up, but we do not have any hybrid browser based tools which can take a Figma/Sketch and wire it with logic (maybe Ionic Creator)
Earlier quoted context omitted.
Then why is it a web app? What happened to open standards? Why not just make it a standalone application, following your logic?
You’re right, it’s not a web app. It is a stand-alone application built on top of Chrome the way that other apps are built on Qt or WPF.
As a UI/UX guy, ReactJS/JSX is a very high bar for us to cross. I have tonnes of Sketch/Figma files ready to be wired, as a JS newbie, JSX is too complicated for a Designer mind to understand :-) Any hopes for a beginner friendly language like VueJS or Webcomponents (AMP Pages/Polymer). The tool has great potential, if u can address the UX market than the dev market. Devs have many many tools they wont give up, but w…