Thanks very much! I'll make sure to read the book through as well. On Wednesday, September 26, 2012 5:13:28 PM UTC+1, Massimo Di Pierro wrote: > > You can delete all of web2py files in an app and make your own. > > The controllers (in your case default.py) is executed in the same > environment as the models, therefore it see all the variables defined in > the models (in web2py that is what models are for: they build the > environment for the controller). > > The only files that you may want to retain are appadmin.py and > appadmin.html because they implement database administration and > jquery.js/web2py.js/calendar.js because they implement useful stuff for > forms and web2py_components. > > Massimo > > > > On Tuesday, 25 September 2012 18:47:48 UTC-5, Vixus wrote: >> >> Hi, thanks for your reply! >> >> What about the rest of the files? Can I make my own layout.html and >> default.py from scratch? I was struggling to find all the details on the >> auth object in the documentation and also what the gluon module is and how >> to use it. default.py doesn't seem to have any imports or anything, are >> these put in automatically by web2py? >> >> vix >> >> On Monday, September 24, 2012 10:24:45 PM UTC+1, Massimo Di Pierro wrote: >>> >>> 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! >>>> >>>
--
