In HTML specification, I saw TCL to client-side script language.
I know that Netscape negivator can be interpreter the javascript,
and that Explorer can be interpreter the Jscript and the VBscript.
What is web browser that can interperter the TCL?
<URL:http://www.scriptics.com/software/plugin.html>
--
Cameron Laird http://starbase.neosoft.com/~claird/home.html
cla...@NeoSoft.com +1 713 996 8546 FAX
> <URL:http://www.scriptics.com/software/plugin.html>
Should I take this to mean any web browser with these plugins will allow
tcl as an embedded client-side html scripting language?
The Tcl plugin is a way to have "tclets" like there
are java applets.
I think the language list in the specs is theoritical
and the only one actually deployed are JavaScript and
to a lesser extent (M$ only) VB.
In article <01bdc09c$7ac05c60$2294...@opus.ngdc.noaa.gov>,
--
http://www.demailly.com/~dl/
-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum
No, not quite. The Tcl Plugin allows "Tclets" to be embedded in a page,
ala Java applets. It does not allow Tcl to replace JavaScript for scripting
pages themselves. However, the Tcl Plugin does provide a mechanism for
sending JavaScript to the browser.
There is an opportunity now to add Tcl as a page scripting language to Mozilla.
I posted an article to this newsgroup a long time ago seeking volunteers, but
I never got a reply :-(
There's also Plume, which uses Tcl for everything, including page scripting.
Unfortunately it's been a while since I've had a chance to work on it :-(
HTHs,
Steve Ball
> There is an opportunity now to add Tcl as a page scripting language to Mozilla.
> I posted an article to this newsgroup a long time ago seeking volunteers, but
> I never got a reply :-(
Well, I'm sure my (non-)answer then is the same as now -- it sounds useful,
and a lot of fun to do, but I have hardly any free time to do it in, and
I can't think of a good excuse to make it a real work item.
Is there anybody who's gotten familiar enough with the Mozilla source to
have some pointers for where this would need to be put in? I wouldn't mind
helping a little with such a project, but I don't want to have to learn the
entire Mozilla source tree.
(I assume we're talking about the HTML construct <SCRIPT LANGUAGE=Tcl> ? )
Zach
--
Zach Frey, Engineering Staff | Voice: (313) 975-7361
Open Networks Engineering, Inc. (ONE) | Fax: (313) 975-6940
2725 S. Industrial Highway, Suite 100 | Email: z...@one.com
Ann Arbor, MI 48104 | Web: http://www.one.com/
> Steve Ball wrote:
> > There is an opportunity now to add Tcl as a page scripting
> > language to Mozilla. I posted an article to this newsgroup a long
> > time ago seeking volunteers, but I never got a reply :-(
> Well, I'm sure my (non-)answer then is the same as now -- it sounds useful,
> and a lot of fun to do, but I have hardly any free time to do it in, and
> I can't think of a good excuse to make it a real work item.
I'm in the same boat. I'd love it if this were there, but it isn't
something I have to time to work on right now :-(
> Is there anybody who's gotten familiar enough with the Mozilla source to
> have some pointers for where this would need to be put in? I wouldn't mind
> helping a little with such a project, but I don't want to have to learn the
> entire Mozilla source tree.
>
> (I assume we're talking about the HTML construct <SCRIPT LANGUAGE=Tcl> ? )
I too am curious about the details of what peopel have in mind.
> Zach
--
Michael Tiller
Ford Motor Company
Steve Ball wrote:
> There is an opportunity now to add Tcl as a page scripting language to Mozilla.
> I posted an article to this newsgroup a long time ago seeking volunteers, but
> I never got a reply :-(
Prior to that we should define Tcl bindings to the DOM (Document Object
Model) so that people can write HTML-embedded scripts whatever the
platform. If we can avoid the same "compatibility" hell that exists with
JavaScript/JScript, that would be great.
The big question is what OO formalism/syntax to use? Rather than chosing
a specific OO extension (like [incr Tcl]), we can try to define a simple
generic syntax that could be recreated in any environment. Also remember
that JavaScript (the de facto standard, and the DOM originator) uses a
prototype-based OO paradigm, whereas most OO environments (including
[incr Tcl]) use class-based paradigms with several variants (C++, Java,
SmallTalk...). I suggest a syntax close to Tk widget commands because
it's well known and easy to recreate. That way, linking this generic
syntax to specific OO extensions would only need a bunch of Tcl scripts
(the same way many Tcl extensions provide their own Tk-like megawidgets
packages).
See you, Fred
--
Frédéric BONNET frederi...@mim.lu
---------------------------------------------------------------
"Theory may inform, but Practice convinces"
George Bain