Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!strath-cs!sfleming
From: sfleming@cs.strath.ac.uk (Stewart T Fleming IE87)
Newsgroups: comp.sys.mac.hypercard
Subject: Assessment of Stack complexity
Message-ID: <3887@baird.cs.strath.ac.uk>
Date: 29 May 90 10:14:52 GMT
Sender: sfleming@cs.strath.ac.uk
Reply-To: sfleming@cs.strath.ac.uk (Stewart T Fleming IE87)
Organization: Comp. Sci. Dept., Strathclyde Univ., Scotland.
Lines: 31

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