>(And BTW, if you've ever written a parser you know that >adding support for this is trivial, and it will have zero impact on >runtime performance.) Then why not support JavaScript as an additional syntax to XTalk, at least that way it will be consistant. It's not all that difficult either http://www.mozilla.org/js/spidermonkey/
OSA supports multiple languages, so does .NET, and HyperCard used to support Applescript. It is the framework, the easy way that you can write an app in a few minutes with a familier easy to use visual object model that matters like Doug said. These languages are just tools and some people find some tools easier than others. Personally I would rather support JavaScript and call it JavaScript then impact the readability of the XTalk language for others. AFAIK Macromedia didn't scrap lingo but added support for Javascript. There are many things that can be added to improve the transcript language and I'm all for it but prefer to discuss on the improve-list or a list set up like the old XTalk list. Tuviah _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution