Cool. Just make sure you sell some premium features or enable donations to make it sustainable.
I am ready to pledge some Early Bird Eur49 for premium features immediately. )
BTW, there used to be active community of visual Javascript tool WaKanda.Org You may be interested to have a look at them. Eventually, they sold their souls to Angular hoping for venture capital to buy them. And even deleted forum after community opposed that. No true developments since then.
Thank you @Volodymyr !
Actually, donations are enabled https://www.meteorkitchen.com/contribute Thanks to everyone who donate, got total ~500 USD in two years - enough to pay hosting expenses, but that doesn’t power the project.
Paid premium features - I plan that, but I think kitchen is not ready/good enough yet, so… powered by enthusiasm (and coffee - a lot of 
).
Good luck! I look forward to seeing more of it.
Is there going to be a way to validate form controls within Visual Meteor?
This is amazing guys … fabulous job
keep it up …
Sure. Simple validation would be
If RadioControl1 === ‘Yes’
Then FieldInputControl text/value is “Required” (in this case the form will throw on submit attempt)
Else FieldInputControl is not required (in this case the form can be save without any text/value on this control).
Basically I’m talking about client side dependencies and relationships between form controls. We can do this today with Blaze and SimpleSchema for example.
Really cool project! Can’t wait to check it out further.
Random question. What have you used for the drag and drop front end to build the source code? I want to develop something similar for an in-house application I have to use at work. Currently we build our views in raw XML
Ah, ok, I understand. There is multiple ways:
Meteor Kitchen can generate SimpleSchema automatically
There is built-in getFormData function which reads the form and performs validation
There is built-in form component similar to autoform (instead assembling form manually as shown in the video, you can drop “form” component, choose collection and form will be rendered and validated according to collection fields definition)
you can add other package into app and perforn validation with it.
Update on progress got more features implemented and improved UI designer. I’m close to deploy first “alpha” release - maybe in next 7-10 days.
Stay tuned!
@ashhimself I’m using “gasoline-turbo”: https://www.npmjs.com/package/gasoline-turbo
My mini project that generates Blaze and React source code from json. It is independent from meteor-kitchen btw.
I wish to implement Angular too, but I am noob for Angular, so contributions are highly welcome.
Drag and Drop part (visual UI for gasoline-turbo) is less or more trivial, there is example app, but I didn’t uploaded the source code - I will tonight when I reach my computer.
New preview video: playing with code like with LEGO blocks: https://youtu.be/JQOkLFA28eU
Added Import from Blaze. Still not deployed, moving slowly but moving forward…
That is damn cool. Kudos!
Wow! Long live Meteor! Kudos man!
Freakin’ sweet, keep up the amazing work! also digging the soundtrack on preview #2 
Tried to create mini example for Meteor Kitchen but and the end I almost made something better than Meteor Kitchen itself 
It’s minimalistic CMS, see video here: https://youtu.be/BVWTSGizo7I
Enjoy!
Moving forward:
Meteor Kitchen now generates directory structure inspired by Meteor guide, plus from Meteor Chef’s Pup and slightly modified by our own experience and routine. (React apps only - Blaze remains unchanged).
Next step: we will replace Flow Router with React Router.
Stay tuned!
Ah… and just to repeat again:
Meteor Kitchen can help you to find a job. Just login, go to your profile and set “I am available for hire”.
Meteor Kitchen can help you to find developers. See list of developers and at the top of the page activate “Available for hire” filter.
Good luck!
perak if you replace flow router with react router do we have start over because the changes made in 9.38 that awsome btw futher a good step to follow alomost pup directory structure
best regards Eric
No need to start over. Once we replace flow router with react router, next time you build the app it will work the same as before. (except if you are tweaking something, e.g. using custom files replacing generated router.js or similar)
last question did you replace flow router with react router in 9.38 or is it plan to come in the next release
That is the plan for next release. In 9.83 only directory structure is changed.