[Pythoncard-users] Re: What Do We Call These Things?

[Dan S. <da...@da...>]

Good, lively discussion.

I'm inclined to agree with the other old 'Card fart here (back at ya, 
Danny!) when he says that HyperCard probably carries around a tad too 
much baggage to be useful in this situation. And Kevin's point that 
an app built on top of PythonCard (or whatever we end up deciding to 
call it) that provides the lightweight data storage automation that 
HyperCard users know and love is probably a better direction anyway.

I'm fine with calling these things we create applications rather than 
stacks. But the other terms for the components leave me cold and 
wondering if I'm working in Visual Basic again. (That's OK. It's a 
recurring nightmare.)

So after spending some time noodling about this, here's a concrete 
proposal that we can at least start shooting at.

A Monty application's visible interface consists of one or more 
Master Layouts which define sets of components that are common to all 
Windows that share a given Master Layout. Windows optionally have 
additional components that are not defined in their Master Layout. 
One type of component is a Pane, which is a container for other 
components. It is legal to nest Panes. The simplest case is a Window 
which is identical to its Master Layout in every respect.

Just a straw person. Let's beat it up!
-- 
Dan Shafer, Author-Consultant
http://www.danshafer.com
http://www.shafermedia.com