[This collection of former "things to do" is all to do with "Old" Pandora.
 "New" Pandora is something on Windows, which mercifully is just installed
 on an as-is basis by CSG, without any attempt by either CSG or the TAs
 to maintain it or understand its innards.
 Thus, this file is now really just a souvenir.
]


Pandora (+ proof "auto-checking")
---------------------------------
 * both the lab cshrc section and the Pandora directory layout / maintenance
	file (makeall, installinlab) structure still make the old
	bin-directory layout assumption (arch- but not os-specific).
	(In fact the lab cshrc section doesn't even conform to the *old*
	assumption any more! - Ian Moor thought Pandora didn't have any
	binaries, but they just weren't installed when he looked.)
	So: get all this to conform to the new "os-and-arch" regime.



 * file-permissions are a bit of a mess! I *almost* did this change:

>> well! amn't I brave! ---a change entirely on my own intiative:
>>  removed restrictive file-permission choice for freshly-written file,  
>>  letting it default to the user's umask-specified file-permissions.
>>  (This is what every normal editor does. People can then choose for themselves
>>   [via umask] what file-permissions they like best.)
>> Plus:
>>  removed arrangement where it saves it in ~/.pandora if it can't save it
>>  there and then. ---users will get very confused if the save apparently
>>  succeeds, and yet it's not sitting there visibly ready to load!
>>  (Also, philosophically, as with any normal editor, it's the user's
>>   responsibility to be working in a place they can write to.
>>   And of course, with the new file-permissions, writing to ~/.pandora 
>>   with no warning or consent could "expose" something they thought was
>>   being written to an unexposed (or less exposed) directory!)
>>  (Not to mention that this double-barrelled saving stuff is not documented
>>   in the comments. So let's scrap it and be done with it!)

	...but then I reversed it, 'cos there's more to it than that.
	(The saving procedures are shared by the "writing to /tmp stuff",
	"writing to user-visible files", and "writing to ~/.pandora"
	parts of the system: there should really be different file-permission
	regimes for these different purposes.)

	Also I think the /tmp scratch directory (as opposed to the /tmp
	shared Pandora fonts directory) should itself have fully restricted
	permissions (drwx------). [surely *it* isn't "shared"!]



 * modify apr_pan / xpan so that the "ill-advised tabs/newlines" remark
	is removed, and instead we have the rule that a title *without*
	tabs/newlines is centered as far as possible,
	whereas a title *with* tabs/newlines is accepted verbatim
	(and therefore comes out left-justified).

	This would allow hardcopy to be upgraded to give any Pandora printouts
	it's dealing with titles like:

		--------------------------------------------------
		Student:	Derek Egbert Fred Gilbert (defg)
		PMT:		Maria Lin (slm)
		Exercise:	jmc1 proof 2
		Filename:	dragons.pan
		--------------------------------------------------

	...which will please Angela when she's putting them in the trays!



 * can the fonts migrate to CSG-installed?