Re: why not load the index first?

On Thu, 2009-01-22 at 19:46 +0530, Kenneth Gonsalves wrote: > On Thursday 22 Jan 2009 7:31:07 pm Malcolm Tredinnick wrote: > > But please do understand that this isn't a > > change that is necessarily universally better for everybody. It does > > harm the content presentation, for example. > >

Re: why not load the index first?

On Thursday 22 Jan 2009 7:31:07 pm Malcolm Tredinnick wrote: > But please do understand that this isn't a > change that is necessarily universally better for everybody. It does > harm the content presentation, for example. ok - I wont raise this again - but please check out the comments on the

Re: why not load the index first?

On Thu, 2009-01-22 at 19:17 +0530, Kenneth Gonsalves wrote: > On Thursday 22 Jan 2009 6:48:11 pm Malcolm Tredinnick wrote: > > I think you have not described whatever problem it is that you're trying > > to solve particularly well. "Index" has at least three different > > meanings for the

Re: why not load the index first?

On Thursday 22 Jan 2009 6:48:11 pm Malcolm Tredinnick wrote: > I think you have not described whatever problem it is that you're trying > to solve particularly well. "Index" has at least three different > meanings for the documentation. I'm assuming you mean the content index > (/dev/genindex/),

Re: why not load the index first?

On Thu, 2009-01-22 at 18:31 +0530, Kenneth Gonsalves wrote: > hi, > > wrt django documentation, why not load the index first - on the left? Do you mean the thing labelled as "general index"? It would use up valuable horizontal screen real-estate without adding a lot of val

why not load the index first?

hi, wrt django documentation, why not load the index first - on the left? Also it would be helpful if the following links are at the top of the index: Search * Latest * 1.0 * 0.96 * All Browse * Prev: django.contrib.webdesign * Next: django-admin.py and manage.py