sfleming@cs.strath.ac.uk (Stewart T Fleming IE87) (05/29/90)
Are there any defined guidelines for assessing the size and complexity of a stack ? I'm thinking along the lines of techniques used to estimate the size of software projects. What attributes of Hypercard affect the time it takes to develop a stack ? - overall stack size ? How big is the stack database ? Are there a lot of different backgrounds ? - script requirement ? Are there lengthy scripts ? Does the stack use scripts from other stacks ? - script complexity ? Do scripts add extra complex features to Hypertalk ? eg duel scrolling fields etc - user modification ? Does the user have options to create cards, backgrounds etc ? Do these have to be incorporated into the original stack ? - navigation requirements ? How does the user control the stack ? Are the methods consistent ? Is there some sort of overview ? Is there *really* a need for Hypercard debugger tools ? As I see it, if the new version is capable of producing stacks which are indistinguishable from applications, then there will be an increase in the number and complexity of stacks produced. I would appreciate all comments about the above (email preferred). Stewart Fleming