0.  structure definition roadmap.  First, the containment tree of things
that can be sent messages ("pure data").

m_pd.h	    t_pd    	    	    anything with a class
    	    	t_gobj	    	    "graphic object"
    	    	    t_text  	    text object
g_canvas.h  
    	    	    t_glist 	    list of graphic objects
g_canvas.c  	    	t_canvas    Pd "document"
g_graph.c  	    	t_graph     subdocument (no patching)

... and other structures:
g_canvas.h  t_selection -- linked list of gobjs
    	    t_editor -- editor state, allocated for visible glists
m_imp.h     t_methodentry -- method handler
    	    t_widgetbehavior -- class-dependent editing behavior for gobjs
    	    t_class -- method definitions, instance size, flags, etc.


1.  C coding style.  At this writing, the C code passes IRIX 5.3 -Wall, which
turns out not to be very stringent.  Several classes of errors aren't caught
which I think should be (e.g., variables used before set).  Some informalities
are intentional, for instance the loose use of function prototypes (see
below) and uncast conversions from longer to shorter numerical formats.

1.1.  Prefixes in structure elements.  The names of structure elements always
have a K&R-style prefix, as in ((t_atom)x)->a_type, where the "a_" prefix
indicates "atom."  This is intended to enhance readability (although the
convention arose from a limitation of early C compilers.)  Common prefixes are
"w_" (word), "a_" (atom), "s_" (symbol), "ob_" (object), "te_" (text object),
"g_" (graphical object), and "gl_" (glist, a list of graphical objects).  Also,
global symbols sometimes get prefixes, as in "s_float" (the symbol whose string
is "float).  Typedefs are prefixed by "t_".  Most _private_ structures, i.e.,
structures whose definitions appear in a ".c" file, are prefixed by "x_".

1.2.   Function arguments.  Many functions take as their first
argument a pointer named "x", which is a pointer to a structure suggested
by the function prefix; e.g., canvas_dirty(x, n) where "x" points to a canvas
(t_canvas *x).

1.3.  Function Prototypes.  Functions which are used in at least two different
files (besides where they originate) are prototyped in the appropriate include
file. Functions which are provided in one file and used in one other are
prototyped right where they are used.  This is just to keep the size of the
".h" files down for readability's sake.

1.4.  Whacko private terminology.  Some terms are lifted from other historically
relevant programs, notably "ugen" (which is just a tilde object; see d_ugen.c.)

2.  Max patch-level compatibility.  An "Import" function will later be provided
which aspires to strict compatibility with 0.26 patches (ISPW version).  Where
possible, features appearing on the Mac will also be provided; for instance,
the connect message on the Mac offers segmented patch cords; these will devolve
into straight lines in Pd.  Many, many UI objects in Opcode Max will not appear
in Pd, at least at first.

3.  Compatibility with Max 0.26 "externs", i.e., source-level compatibility. Pd
objects will follow the style of 0.26 objects as closely as possible, making
exceptions in cases where the 0.26 model is clearly deficient.  These are:

3.1.  Anything involving the MacIntosh "Handle" data type is changed to use
char * or void * instead.

3.2.  Pd passes true single-precision floating-point arguments to methods;
Max uses double.
Typedefs are provided:
    t_floatarg, t_intarg for arguments passed by the message system
    t_float, t_int for the "word" union (in atoms, for example.)

3.3.  Badly-named entities got name changes:

    w_long --> w_int (in the "union word" structure)

3.4.  Many library functions are renamed and have different arguments;
I hope to provide an include file to alias them when compiling Max externs.

4.  Function name prefixes.
Many function names have prefixes which indicate what package they belong
to.  The exceptions are:
    typedmess, vmess, getfn, gensym (m_class.c)
    getbytes, freebytes, resizebytes (m_memory.c)
    post, error, bug (s_print.c)
which are all frequently called and which don't fit into simple categories.
Important packages are:
(pd-gui:)   pdgui -- everything
(pd:)	    pd -- functions common to all "pd" objects
    	    obj -- fuctions common to all "patchable" objects ala Max
    	    sys -- "system" level functions
    	    binbuf -- functions manipulating binbufs
    	    class -- functions manipulating classes
    	    (other) -- functions common to the named Pd class

5. Source file prefixes. 
PD:
s    system interface
m    message system
g    graphics stuff
d    DSP objects
x    control objects
z    other

PD-GUI:
t    TK front end

------------------ done --------------------

tabosc4~
vcf~ help window fix
table couldn't be opened
writesf~ was always mono

------------------ dolist --------------------

SOON
dialog for audio and MIDI settings
Hammerfall fix error lights
Hammerfall adapt to ALSA
prepend help to help filenames and add help search path
ASIO or Direct X for NT
read/writesf~ for same
expr included as "internal object"
figure out about commas in exprs
pd to search harder (e.g. along $PATH) for binary
variable send and receive
number boxes to darken for typing and/or received messages
delayed updates
notice iconification and suspend updates
invisible toplevels
"lib" flag to search "extra" directory
new objects: clip, zerocross~, nexttick~
fastedit moves
make "pasting" data stop re-building the whole window
pique~ and fiddle~ unification (notice pique filtering is different!)
new message box look
try to find better fonts for Windows
dialog to change lib flag and path

data:
click on points of plot
typing at drawnumbers
fix templates to be loaded on demand and belong to a globally known patch
lists as elements of templates
sublists should display on parent if desired?
sublists seem not to handle canvas allocation right (get.pd->pointer.pd bug)
scalar hook to catch the mouse
protect against "plots" going away while you drag on them

LATER
+~ 0 faster than +~ -- detect scalar input; also, order forcing inputs
bonk~ file path handling
unify arrays and garrays
dialog to give values of $1, ... for the canvas
bang at end of line~, etc.
recording to part of a table
printout to main window
should sys_bail kill all "threads" on the way out?
check a_valid usage
allow backslashes (or else really disallow them)
HTML doc files: how can I get Pd to get the OS to open them?
icon & desktop integration
vreadsf~
benchmarking
flash menu when accelerator hits?
fix edit mode menu item
add button&slider?
"undo"
fancier text editing
tools (reassigns meaning of primary click)
get gui to notice early EOF
rewrite t_getbytes properly
obj_new should do a longjmp on out-of-memory
