[I7] Table of Contents

[Emily Short]

Coming to this somewhat belatedly after a busy week:

First, I think this is a great improvement overall. It gives me a  
sense of the structure of the code in a way that no previous gadget  
quite did, and it feels very smooth and elegant how the contents panel  
slides in and out.

> Of course one option would be to display
> the name of what's above and what's below
> in small type, or italic, or both, above the
> tear -
>
>     Section 2 - Whatever
>  /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
>
> Hmm. Does anyone like this idea? I'm not
> sure.

I think it wouldn't hurt, in that it would give the user some idea of  
what to expect when clicking there.

>> Something else that should probably be done is to hook this into  
>> the undo system, so that pressing undo after changing the source  
>> view will change it back again.
>
> We also need to think about the effect of
> Find (this probably needs to open the source
> to the entirety?)

It would be nice to have the option of doing a find and replace just  
in the segment we currently have open.

I am also wondering whether, once we have this working to our  
satisfaction, we shouldn't revise the Contents Index, for two reasons.  
One, I think it will confuse people when talking about the IDE if  
there are two separate kinds of tabs both called "Contents" which lead  
to similar but different kinds of information. And two, I think this  
does most of the work of the Contents index, only much better. (There  
are some things in there that would still be worth having, like the  
list of global variables, but it has always seemed slightly arbitrary  
that those appear at the foot of a table of contents, so possibly it  
would be appropriate to revisit what we're doing here.)

The chief objection I can think of to removing or seriously revising  
the Contents Index page is that it currently does list all the objects  
generated in each section. The problem is, though, that on a game of  
any size this list is so big and unruly as to be essentially useless,  
and I might as well just search the main source for the object I'm  
looking for.

Anyway, I think this is definitely a step in the right direction, and  
also that it does make it easier for me to think of a given piece of  
the code as a discrete entity.

-- Emily