You can look at the internals if there is a bug, if core features
don't do what you want and you need to extend them or if the
documentation isn't sufficient for you to understand how to properly
use the facilities provided by the framework.

However, this should be the exception and not the norm.

The reasons you use various lower-level solutions (Linux, Apache,
Python, this Framework) is because you do not want to re-invent the
wheel, but rather build on previous work to get more done.

Ideally, those solutions should work well enough out of the box that
you should rarely (if ever) feel inclined to look at their deep
internals.

At least, it needs to be so if those solutions to be viable in
commercial ventures (as opposed to strictly be viable for Academic
interest only).

Furthermore, backward compatibility demands that as a user, you should
avoid modifications to the deep internals of a Framework that is
essentially managed by someone else as those modifications are likely
to be overwritten or otherwise break future versions of the Framework
(again, if you consider the Framework a mere curiosity, propagating
those modifications to further versions might not be a problem, but if
you end goal is to build a complex app on the Framework, you want to
avoid the hassle of having to manage the internals of the Framework as
well, especially if you don't have total control over them).

With that said, I think this Framework is very good (both as a tool
and as a tutorial), but I needed to outline a difference in philosophy
here.

On Sep 28, 8:48 am, mdipierro <mdipie...@cs.depaul.edu> 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 <bvivek1...@gmail.com> 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 ..)- Hide quoted text -
>
> - Show quoted text -

Reply via email to