Grey Li

> I've made the interface a lot more flexible, but and if you think its needed yet, I can make it backward compatible. Does this PR break something?

IMO, it's a good idea to make it backward compatible.

I prefer to make a new file.

Can we just keep the old keyword arguments (i.e. `action`, `method`, `extra_classes` etc)? Both in the code and the docs. These arguments were commonly used when people rendering a form.

@madsmtm We need to let user transfer easily from Flask—Bootstrap to this project, so I want to keep all of them.

OK, you are right, just update the docs will be enough.

Hi, please make sure you have already installed this extension (instead of `flask-bootstrap`): ``` $ pip install bootstrap-flask ``` Besides, this extension can't use with Flask-Bootstrap at the same time,...

TODO: Create a FAQ section in docs and add this issue.

It will bring too much complexity, I think this should be supported with an external library.

Not yet. I'm happy to review a PR.