I'm author of Structor. Now I'm working on documentation. If you have any questions you want to know, please put the issue on GitHub (https://github.com/ipselon/structor) or write directly to support. Thanks.
Looks promesing, but it looks like the person is still working on it to get it ready.
I don't understand this line:
"This project was developed for real-life site on http://helmetrex.com"
But the url is the site that you are already on, and it is called StuctorMarket, but Stuctor is something else here:
https://github.com/ipselon/structor
Wow, so many negative comments in here. First of all, thanks to the author for this project! Not that I directly benefit from it, but I appreciate the effort that has gone into taking the pains to make a project of this complexity, setup a website for this and most importantly, open source it! Still requires a bit more polishing, but this project being open source, I see no reason why it wouldn't, pretty soon.
Divshot was aquired by Google and probably we will see built-in support for Polymer and Angular in a not so distant release. I guess Helmetrex will face the same destiny under Facebook.
Yup. I ended up ditching front end frameworks and just using Atom to build a desktop application. Atom has so many packages already it makes it just a matter of figuring out how to put everythung together,
No, there is no demo for builder. Structor runs as server on localhost and reads files from local filesystem. So, if there was a demo for each on-line demo session we would have to start new docker container or something like it.
I've really wanted a way to have prototype GUIs be cross platform deployable. Probably there would be demand given the popularity of prototyping tools like zeplin.io, www.invisionapp.com, https://www.flinto.com/, http://framerjs.com, http://giveabrief.com/ and others.
The code generation is tailored for each platform, so there's no common framework or other library dependencies in the generated project files. Instead the generated code uses the native stuff directly. On iOS that means you get UIViewControllers, UINavigationControllers, UIPageControls etc. Likewise on Android the native equivalents.
Looks good. But problem with all this kind of builders is customisation. Since HTML/JS/CSS is so powerful for customisation, one day as a developer you will realise, this is not helping me in that.
It was said in the sample project on market site: "this project is fully customisable and hackable". You may create and bring in the project any React (and not even React) component you wish.
When team of Material UI components will make stable their library for react 0.14.0 I will publish project with Material UI components on market.
Would it be enough to say that this is customisable ?