> However, we're always interested in any way to make the documentation
> better, so if you can come up with a way to make this idea work, we
> can take a look at it.
That's the hard part and was hoping someone would have a bright
idea. :) The best idea I've had is to spell out the full path
On 9/10/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> Hi Devs,
>
> One of the things I'm always stuck with when reading the docs is
> knowing where to import the described methods or objects from. For
> example, just now I'm working on Q objects and just read the
> documentation but don't know
While not exactly what you're looking at, something I had considered
some time ago was putting together a set of wiki articles that are
geared toward more of a quick-reference documentation. I put together
articles for HttpRequest[1] and HttpRespone[2], but never got any
further than that.
As
Hi Devs,
One of the things I'm always stuck with when reading the docs is
knowing where to import the described methods or objects from. For
example, just now I'm working on Q objects and just read the
documentation but don't know where they live without having to jump
into the source of where
