Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!rutgers!njin!princeton!phoenix!englandr
From: englandr@phoenix.Princeton.EDU (Scott Englander)
Newsgroups: comp.sys.mac.hypercard
Subject: Wish list (Was Re: What to do about > 32K of data?)
Message-ID: <7526@phoenix.Princeton.EDU>
Date: 1 Apr 89 01:51:01 GMT
References: <938@Portia.Stanford.EDU> <10520023@hpfcdc.HP.COM>
Reply-To: englandr@phoenix.Princeton.EDU (Scott Englander)
Organization: Princeton University, NJ
Lines: 32

Spreadsheet-like fields!  I second that.  Just spent HOURS working on a
stack moving all those little identical fields around, and writing the
code to reference their names.  Perhaps a way to reference cells would
be like an array:

put field table[3,4]

You get the idea.  Other items:

Grouping of objects (fields, buttons).  I ALWAYS want to move lots of
stuff together when arranging a card.

Records (a la Pascal).  I suppose i could kluge it by assigning globals
to item numbers and then referring to "item [fieldname] of [recordname]"
but this gets cumbersome.

Search and replace while editing scripts.  Or at least the ability to
use McSink to do this without having to press OK first and then get
back into it after using McSink.

The ability to change a field's number from within the field info dialog
box.  Right now, you have to choose the field tool, select the field, 
choose "bring closer," double-click on the field to see what number it
changed to in the dialog box.  This is important, because field number
determines tabbing order, and to move one from 38 to 10 requires
executing the above sequence many times (it doesn't always move closer
or farther each time).

Many more, can't think of them now.
-- 

                                               - Scott