Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why limit to forms? #3

Closed
dyve opened this issue Sep 14, 2011 · 3 comments
Closed

Why limit to forms? #3

dyve opened this issue Sep 14, 2011 · 3 comments

Comments

@dyve
Copy link

dyve commented Sep 14, 2011

Great idea to keep bootstrap to tags in Django. Might be better than making real BootstrapForm, BootstrapModelForm, etc.

But why limit it to forms only? You could have tags to include Bootstrap CSS, additional JavaScript (required to make topbar etc work).

@tzangms
Copy link
Owner

tzangms commented Sep 14, 2011

Hi dyve,

Coz, all the twitter-bootstrap things is all about html and css, only forms can simplified by template tags.

There is BootstrapForm version, check this out

https://github.com/earle/django-bootstrap

@chengyin
Copy link

The biggest problem I have for the class version is inheritance, it's hard to apply it to the django forms such as UserCreationForm.

I like the filter version. Do you have any known limitation?

@dyve
Copy link
Author

dyve commented Oct 26, 2011

I rolled my own version that does a little more than basic conversion (https://github.com/dyve/django-bootstrap), because tazangms didn't want it in this implementation. Learned a lot from this source though.

@dyve dyve closed this as completed Oct 26, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants