Event-driven GUIs, PythonWorks, Boa, wxWindows; future directions of event-driven Python?

[Cameron Laird]

In article <mailman.992871506.18037.python-list at python.org>,
Roman Suzi  <rnd at onego.ru> wrote:
			.
			.
			.
>I still remember HyperCard with warm feelings.  It had very comfortable
>look&feel both from developer's and user's perspective. Every object had
>it's own script, which contained event handlers. Events were forwarded
>automatically from contained objects to containers and if not handled,
>Hypercard was the last who intercepted them. (Much like exceptions).
>
>Very nice scheme, which allowed to concentrate on the GUI and application
>logic, and not on the message propagation details.
>
>What I wanted to say, is that GUI programming is really easy when tools
>are like HyperCard: conceptually simple and powerful. Because all that
>complication comes from not hiding unnecessary details. Tk is like
>Assembly of GUI, while higher level is needed.
>
>After HyperCard (and SuperCard, HyperStudio to some extent) I have not
>seen anything near the quality and simplicity, unfortunately... Well,
>probably Squeak (sp?) is near, but it is thing in itself.
			.
			.
			.
Do you realize a modernized HyperCard is still commercially
supported <URL: http://www.metacard.com/ >?
-- 

Cameron Laird <claird at NeoSoft.com>
Business:  http://www.Phaseit.net
Personal:  http://starbase.neosoft.com/~claird/home.html