And note, this issue is not specific to the web2py scaffolding app -- it applies to any site you want to migrate from Bootstrap 2 to Bootstrap 3 (or 4) or to Semantic UI, etc.
On Monday, November 16, 2015 at 6:29:26 PM UTC-5, Anthony wrote: > > On Monday, November 16, 2015 at 5:09:57 PM UTC-5, lillian wrote: >> >> Anthony, >> >> The app mostly uses the default styling which is why I was surprised so >> much of it seemed broken when I tried to migrate, >> > > Yes, but it is the default styling for Bootstrap 2. The CSS rules for > frameworks like Bootstrap are not based on HTML elements alone. Rather, the > framework itself prescribes both a particular HTML structure and a set of > specific CSS classes. Therefore, when switching from one framework to > another (including from one major version of Bootstrap to another), it is > not simply a matter of swapping out the CSS rules -- you also have to > change all the HTML markup and CSS class names so they are consistent with > the requirements of the new framework. > > If you stick Bootstrap 3 CSS rules in an app whose markup is written for > Bootstrap 2, it's not going to work. Whether or not you have stuck to the > default styling in the original Bootstrap 2 markup is irrelevant. > > >> It seems like it might be easier to start a new app and just move the >> controllers/views/models over from the old app and go from there. >> > > Yes, that was my point. You are migrating to a new front-end framework, > which has its own unique requirements for markup and class names. > > Anthony > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
