Until some time ago web2py mantained the "burden" of it's own template, it's own css, it's own javascript functions based on jquery. I think I started using web2py when it contained only ez.css's classes. Having to be a CSS/JS coder better than all peoples around the world can be hard ;-)
Then superfish was added, css3 buttons were included, skeleton was adopted, grids can be serialized in a friendly jquery-ui style, etc. etc. etc. Let's be real: css frameworks and ui js are included in every application someone is starting coding out there. You're not forced to be an HTML guru to be a web programmer, and still have some nice user interface. >From where I am standing, both as a simple and a long time web2py user, I'm happy to "infiltrate" in all code that web2py generates and explore practically every flexibility it has to offer, but "sane defaults" are provided right now and maybe are ok for ultra-small apps. Now, I'm not saying to follow every css and js library out there, but bootstrap is 160K of css (counting images and some nice js), largely adopted and very well supported, probably not going "under" within the year, mobile-friendly and in general easily understandable and to work with. web2py should leave defaults as always, but it's nice to see it "ready" to integrate with the major players out there. I think that a "style" argument can be added to every bit of code will need to change in the code regarding serialization without much problems. web2py 2.0 will be bootstrap-menu ready, if users want to start with welcome and edit that, it'll be ready. Maybe 2.1 will be bootstrap-forms ready, and so on....... Backward compatibility is not broken, old behaviour is maintained. If someone wants bootstrap's form he'll set a style parameter and voila. Il giorno sabato 26 maggio 2012 16:37:05 UTC+2, Massimo Di Pierro ha scritto: > > For now this is in trunk. Your implementation looks good. > > For me the problem whether we want to do this or not. Most of the > conventions implemented in web2py core are web2py own conventions or > standard protocol. Bootstrap is a css library. very popular today but will > disappear tomorrow as a better one comes out. Now everybody will use it. Is > it a good idea to include code which is designed exclusively for bootstap > conventions and specifically refers to bootstrap css classes? Or is it > better to handle it from the layout only using js? > > So we need to think about this some more. I cannot promise this will stay > in web2py 2.0 in this form. > > Massimo > > >>> >
