I've been playing around with builder, it seems amazing but it seems to stop just short of completing all the "rote" code by not performing the steps to set up a component, am I missing something?

Couldn't it run php artisan create:component to build set up a component? It would be nice to be able to stay out of the command line if builder is doing most of that heavy lifting.

Lots of views, but no responses.

Is this something that no one wants? Am I missing something wanting it?

I'm still looking at this idea. A components option could create new components and update the description field and edit the default.htm file (like you can do in the CMS view)

I notice that the plug-in info can not be updated either.

Right now there is probably no other way than use artisan's create:component or prepare it by hand.

Maybe open new issue on Builder's support page?

I believe this is an important feature for the builder. With this feature you could prototype your plugin and make it work on both back-end and front-end without writing any line of code.

I thinks the best way to implement this feature is to do what Rainlab.Pages plugin does with snippets.

So may be we can reuse the code of Rainlab.Pages to get this. Then we add a new generator to the builder that convert a partial/snippet to a component :

• In the plugin config file fill the registerComponents function
• Create the component registration file
• fill the property definition with the snippets properties
• Create the component partial from the existing partial
• (add a code section for creating a dynamic component) - its may be not necessary. I can use my favorite text editor for that, it is the most interesting part.