these are independent from everything else so you may want to start looking at them first
gluon/html.py gluon/template.py gluon/highlight.py this is also independent but complex (the dal) gluon/sql.py these are the main ones gluon/widget.py gluon/main.py gluon/globals.py gluon/compileapp.py wsgibase in main.py is the most important function. You could say that defines web2py. build_environment in compileapp.py builds the environment as see by your apps. On Sep 28, 9:19 am, b vivek <[email protected]> wrote: > I know it is too much to ask, but could somebody suggest where do I start > digging in. I really want to know the internals properly. Well Massimo, if > you have to suggest a student, where would you ask him to begin... > > On Tue, Sep 28, 2010 at 6:18 PM, mdipierro <[email protected]> wrote: > > Not sure I understand. The code is there. You are encouraged to look > > at it. I do that with my students. > > > On Sep 28, 6:44 am, b vivek <[email protected]> wrote: > > > I have spent the last few weeks with web2py and found it to be really > > good. > > > In the process I have also built a small application for a client with > > it, > > > which is supposed to be deployed sometime next week.Now I am planning to > > > build something bigger, larger using web2py. > > > > Would it be good dig through the inner codes of web2py, its working etc. > > Or > > > can I just start off and whatever I need apart from this , I can add up > > as > > > modules and work on it!.. (the question looks vague but hope someone > > > understands ..) > >
