Closed kharazi closed 9 years ago
First of all let's wait for Bootstrap 3 final and few months after that until BS3 gets really stable. It's almost impossible to support both BS3 and BS2 versions, because it is not just css, HTML markup also changes a lot.
Anyways i think moving to BS3 is a good thing, but let's wait a bit. Font icons, new components, better markup too are worth of moving to v3. Just that first version of DjangoSuit with BS3 will not be backwards compatible.
Bootstrap 3 final is here... we are already using for the rest of one project and the sooner django-suit uses it the better.
i would also like a switch to bs3
+1
+1
+1
+1
It is not very hard to move.. I have moved all my applications... BS3 is much lighter and better.
2013/12/27 Juraj Bubniak notifications@github.com
+1
— Reply to this email directly or view it on GitHubhttps://github.com/darklow/django-suit/issues/134#issuecomment-31272029 .
+1
+1
+1
+1
+1
+1
+1
+1
+1
Any update on this. My opinion is that BS3 in 3.1.1 release is quite stable.
+1
+1
+1
I think i will need to make a statement before somebody will try to fork and make his own version of Django Suit with Bootstrap 3 (i saw few tries already).
Very soon i'll start working on migrating to BS3 and this is feature with priority Nr1, which means no need for +1 anymore :)
However i don't want just to change bs2 classes to new ones, that is the reason why this feature was on hold.
I am planning redesign Django Suit so that is supports few very important features like switching from left-vertical navigation to top-horizontal (both versions will be available). Top horizontal navigation would save us lot of horizontal space if needed and also allow to use Vertical tabs for forms instead of horizontal ones. There will be facelift on design terms too.
Also bootstrap3 has very nice responsive utilities, and i'll see what i can do about that, probably we can support some responsiveness too for at least iPad-like sizes.
This means i will rebuild theme from scratch and this needs time. I'll try to maintain backward compatibility as much as i can, but because Django release cycle is getting faster and Django 1.7 is really close, there is a chance that new version will be supported starting from Django 1.6 only. Probably i will split app into two branches 0.2.x branch for current version fixes (Django 1.4-1.6) and new 0.3.x for new version (Django 1.6+).
Also because Django CMS with v3 is starting to move away from default Django admin layout (they even have additional extended design theme), it get's harder and harder to maintain it. Therefore Django CMS support will probably will be dropped and some alternative CMS app (most likely FeinCMS) will be supported. See my more detailed comment about Django CMS 3 here: https://github.com/darklow/django-suit/issues/213#issuecomment-39294600
So any global layout ideas or comments on compatiblity are also welcome.
That is awesome! Thanks so much for addressing this in such a open and nice manner.
Any ETA on this?
I know this is priority #1. Any indication of a timeline will be very very helpful! A month? Six months?
This would be amazing. Would pay for it.
+1
+1
Main BS3 discussion is here: https://github.com/darklow/django-suit/issues/262#issuecomment-63809723 You can test and try it out already. Closing this one.
Sorry, but i still want to say:
+1
+1
You should move to Bootstrap 3 with care. It is changed.