Code export wasn't our original plan, but we've been thinking about it more and more. It seems like Repaint is only a couple steps away from a pretty sweet "design tool for real code".
You're right about the exporting though. We're not sure exactly how to synchronize a code editor & Repaint editor for two way updates.
I'm confused - why can't this export as static HTML / CSS? Would make it useful for github pages. If you make it free for exported code as GPL or some super-restrictive license that only works for true free software, where nothing commercial can ever be used for what is exported, seems quite useful
I don't get it. If you can't export HTML and it can only be hosted on servers you control, why did you output HTML internally? Why not just stick to your own proprietary layout format and rendering engine?
Since almost all websites use HTML / CSS, its the output format we wanted to target. If you don't use HTML it breaks things like SEO, accessibility, etc.
What if the Repaint Project required me to link it to a git repo and make my repaint account have git access and my files live and read out of my git repo?
You're right about the exporting though. We're not sure exactly how to synchronize a code editor & Repaint editor for two way updates.