kwok@uhccux.uhcc.hawaii.edu (Kwok Bor Cheung) (02/28/90)
I am a novice hypercard 'programmer' and would like to improve my skill in developing hypercard stacks. I have created a few stacks for myself and I am running out of ideas what (stack) to make next. If someone out there has any idea (whether it is old or new) on what to develop, please email the idea to me. Your response will be appreciated. Thanks.
nvi@mace.cc.purdue.edu (Charles C. Allen) (12/18/90)
Ideas? Did I hear a call for ideas on how to improve Hypercard?
Button, field, card, and background variables.
Menus as objects. Popup menus.
Standard highlighting behavior of buttons.
Named parts of variables ("firstName of thisPerson", or something like
that). Ability to display these in fields easily.
Charles Allen Internet: cca@physics.purdue.edu
Department of Physics nvi@mace.cc.purdue.edu
Purdue University HEPnet: purdnu::allen, fnal::cca
West Lafayette, IN 47907 talknet: 317/494-9776bayes@hplvec.LVLD.HP.COM (Scott Bayes) (12/20/90)
> Ideas? Did I hear a call for ideas on how to improve Hypercard? > > Button, field, card, and background variables. Yes. Has anyone noticed how many places the 2.0 Power Tools stack has a comment to the effect "keep this function at the start of this script" in a button or field script? The function invariably returns data needed by the handlers. What better way to do this than with an object variable? > > Menus as objects. Popup menus. > > Standard highlighting behavior of buttons. Wht do you mean? > > Named parts of variables ("firstName of thisPerson", or something like > that). Ability to display these in fields easily. It would be nice to have these, kind of a struct or record capability. > > Charles Allen Internet: cca@physics.purdue.edu > Department of Physics nvi@mace.cc.purdue.edu > Purdue University HEPnet: purdnu::allen, fnal::cca > West Lafayette, IN 47907 talknet: 317/494-9776 Scott Bayes
nvi@mace.cc.purdue.edu (Charles C. Allen) (12/20/90)
> > Standard highlighting behavior of buttons. > > Wht do you mean? Several people have asked this in mail, so I'll explain here. Go into any application that uses the standard CDEF for radio buttons or checkboxes. Click on one of them and hold the button down. The outline of the button becomes two pixels rather than one, while the actual state indicator is not changed. The "you're changing me" indication is orthogonal to the "what's my state" indication. Now do the same thing in Hypercard and cringe at the use of the same mechanism for both. I personally find Hypercards treatment of radio buttons and checkboxes to be very disconcerting. Charles Allen Internet: cca@physics.purdue.edu Department of Physics nvi@mace.cc.purdue.edu Purdue University HEPnet: purdnu::allen, fnal::cca West Lafayette, IN 47907 talknet: 317/494-9776