Jesse Leite

I'd suggest you use `open()` instead of `openHorizontal()` and use labels and form controls (see base form package) and bootstrap grid, to suit your own custom layout. It's more work...

You'd need to extend laravel's error bag to support namespacing, wouldn't you? That said, @adamwathan I had [that PR for form namespacing in the base form package](https://github.com/adamwathan/form/pull/109), which namespaces a...

@axyr I had `Form::open()->namespace()` in my first two commits, but we needed to store the namespace on the builder instance. Adam suggested it be implemented at the builder level, similar...

@adamwathan @axyr Updated implementation to accept `name()` before `open()` 👍 Example... ```php Form::name('profile')->open() Form::bind($bindProfileInputs) // Form inputs Form::close() ```

Rather than binding the actual model, you could bind an array of translated attributes. I'm not familiar with dimsav/laravel-translatable, but is something like this possible? ```BootForm::bind($catalog->translate($locale)->getAttributes())``` If not, you might...

@axyr Because my code is on `Element`, and because `FormOpen` extends `Element`, this is already possible: 

I know this was implemented in #99, but my case for magic method implementation here: https://github.com/adamwathan/form/pull/99#issuecomment-276850199 ...That said, if you want to close this PR, I won't be sad :)

:+1:

Oh very cool, thanks!

@geddski If you are still thinking of removing @locations, maybe you should do so before too many people marry themselves to it. Or at least remove it from the http://csstyle.io...