I usually end up in that way too. But I don't find it convenient. There's lots of class relations and going back and forth is clumsy. Also in most cases Im just after the specification of a class or where it's defined and it takes longer time if you have to scroll down the source code as well. Have a look at the API doc of a 3D library called Ogre3d http://www.ogre3d.org/docs/api/html/annotated.html
Do you see what I mean? Fast, simple, clean and online! Very convenient! On Jan 10, 10:53 pm, Sam Walters <mr.sam...@gmail.com> wrote: > Hi, > My approach with regard to: > > > frameworks I'm used to have at least a well structed API documention listing > > all methods and members of classes with some comment attached to them. They > > also show the class heirachy, quick and simple. > > I just look at the source itself for this. > > cheers > > sam_w -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
