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

[David L. <wh...@oz...>]

On a more serious note...

Two or three (or four) questions spring to mind:

1. What baggage does using the Hypercard metaphor bring along?

2. Just exactly _who_ is the intended audience and application domain?

3. Having just reviewed the PyCard website, I don't recall seeing any
mention of what the scripting language for PyCard is to be - if it's going
to be Python itself, that sets the bar at a certain level from the outset
(answers part of the who in question 2 for example).

4. Is there a spec?

Ok, enoug seriousness - I like PyCard; mascot: Jean Luc PyCard of course :>

And, if you didn't like 3 Card Monty, how about the Full Monty? And for the
older members of our television audience, how about Monty Hall? Monty
Cristo, Count of?

And now for something completely different...

Dave LeBlanc

> -----Original Message-----
> From: pyt...@li...
> [mailto:pyt...@li...]On Behalf Of Dan
> Shafer
> Sent: Monday, January 07, 2002 18:55
> To: pyt...@li...
> Subject: [Pythoncard-users] Re: What Do We Call These Things?
>
>
> 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
>
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythoncard-users
>