Yes Anthony, this was my understanding, but I am glad that you confirm. I appreciate very much the time you spent to explain. And, Yes, it was debunked and there is even a scaffolding version with Bootstrap 3, confirming the point. Still, I also appreciate the response of Massimo, pointing out that there is a general difficulty in the integration of arbitrary CSS + HTML approaches into any framework. Custom layout could easily be created with bootstrap 3 and yet there was still a difficulty in the integration process. I do believe that the difficulty is inherent to the complexity of layouts + styles, which prevent the creation of an abstraction layer over templates similar to what we have in the case of database structures.
On Saturday, 18 June 2016 13:29:54 UTC-4, Anthony wrote: > > On Saturday, June 18, 2016 at 8:47:42 AM UTC-4, Dominic Mayers wrote: >> >> I am just starting to learn web2py and I want to better understand the >> issue. Is the issue simply that Bootstrap 3 is not backward compatible >> with v2.x and therefore we cannot use Bootstrap3 with the templates in >> web2py that have been created with Bootstrap 2 ? >> > > Yes, though this is not really an issue because even if you want a custom > Bootstrap 2 theme, you still cannot simply use the existing front-end > scaffolding app without making significant modifications. The front-end > scaffolding application is just intended as a quick and easy starting > point. If you want a custom layout, you need to implement that, and > implementing a custom layout is equally easy/difficult regardless of which > CSS framework you are using. > > >> The issue seems to be bigger than that because we would need to modify >> "all parts of web2py that are tightly bound to bootstrap", but what does >> this mean? >> > > You should read back through this thread, as that statement has been > debunked. No parts of web2py are tightly bound to Bootstrap, as web2py > itself predates Bootstrap. The front-end scaffolding application is based > on Bootstrap 2, and web2py forms and the grid include some convenience > formatting options for Bootstrap 2 and 3, but you can use all of these > elements without Bootstrap at all, as they always had been used prior to > Bootstrap's existence. > > >> Of course, we expect a coupling between the view and the remainder of >> the code. The code has to provide data as expected in the view. There is no >> way this can be avoided, even in a loosely coupled framework. So, is this >> the only issue? I would like to know if there was a fundamental flaw in the >> design of web2py? >> > > Keep in mind that most server-side web frameworks don't provide a > front-end scaffolding application nor built-in formatting options for any > CSS frameworks. web2py happens to provide a bit more than other frameworks > in this regard. Some of what it provides happens to be based on Bootstrap, > but you can simply ignore all of that and use whatever CSS framework you > want -- and at that point, you are no worse off than you would be with one > of the many other server-side frameworks. > > 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.
