> > I see. Note, web2py.css is designed primarily to work with the "welcome" >> app. You don't have to use web2py.css or the "welcome" app at all, though. >> You can instead create the entire front end with pure Bootstrap, and that >> should work fine with web2py (if you're using the web2py grid, you might >> want to retain the grid-specific CSS from web2py.css). > > > Is this the case even if I just use the latest stable instead of trunk? If > I ditch web2py.css completely and don't base my front-end on the 'welcome' > app, and use purely Bootstrap (bootstrap.min.css), then there shouldn't be > any restriction imposed by web2py? >
Perhaps there is something I'm not thinking of, but I don't see why there should be any restrictions. web2py is primarily a server-side framework. It includes the "welcome" scaffolding application (which includes some client-side CSS and JS) to help jump start development (especially for prototyping), but you don't have to use it. > I see many people seem to prefer to work with web2py.css as a base, and > customize stuff as they go, I wonder if there is any specific advantage to > this approach (better supported by web2py? but I doubt so considering > web2py is supposed to be a generic enough framework). > Much of web2py.css is useful only if you're basing your design on the "welcome" app, though there are a few pieces you might keep (or keep with some modification) even with your own custom design (e.g., the grid CSS, maybe form errors). On the other hand, web2py.js is probably something you want to keep (for Ajax and components), but I don't think that should cause any conflicts (and again, it's easy enough to just edit if necessary). Anthony --
