Hello Vixus, If you want to use bootstrap, than it comes with it. If not, then deleted everything but web2py.css, jquery.js, and web2py.js for components and grids you need those but they are small and un-intrusive.
massimo On Sunday, 23 September 2012 10:05:46 UTC-5, Vixus wrote: > > So I'm reasonably experienced with python and grew up web developing with > PHP. I wanted to move all my web development over to python and web2py > seemed like the ideal way to get started. There's one thing I really don't > like however and is giving me a lot of trouble actually learning the > framework and that's all the default cruft that gets put in place when I > start a new application. Also a lot of things are hidden behind the IDE > (where is default.py getting all its module info from?) -- there doesn't > seem to be any technical explanation of what's going on behind the scenes. > > For instance, yes, it's very nice that a user system is put in place for > me but all the other stuff like the bootstrap UI elements just gets in the > way of me developing my website because I spend more time sifting through > the huge CSS files trying to fix things. Basically, I'm used to building my > sites from the very ground up, because then I know how everything fits > together and works. With web2py I've found this really confusing. Yes, I'll > read through the entire book but I'd find it a lot easier to get the > examples if I had a really blank project to work with. > > So what does everyone think? Do I just delete all the files and start from > scratch (I'm scared something will break or I won't have the right initial > setup) or continue trying to muddle through with the prefab setup? > > web2py feels amazingly powerful, and I want to add it to my arsenal, so > any help is appreciated. Thanks! > --
