From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Nic Ferrier Newsgroups: gmane.emacs.devel Subject: Emacs and Javascript/XSLT (was Re: A new online publishing tool for Texinfo documents.) Date: 25 Nov 2003 10:37:12 +0000 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87u14sbup3.fsf_-_@kanga.tapsellferrier.co.uk> References: <200311222118.hAMLI3v07843@f7.net> <87r800dr09.fsf@kanga.tapsellferrier.co.uk> <87znemp5a0.fsf@mail.jurta.org> <878ym6dtbh.fsf@kanga.tapsellferrier.co.uk> <87smkc7ulq.fsf@mail.jurta.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1069759887 32210 80.91.224.253 (25 Nov 2003 11:31:27 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 25 Nov 2003 11:31:27 +0000 (UTC) Cc: Juri Linkov , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue Nov 25 12:31:23 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AObPe-0001iE-00 for ; Tue, 25 Nov 2003 12:31:22 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AObPe-0008Jp-00 for ; Tue, 25 Nov 2003 12:31:22 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AObyt-0007Ca-TY for emacs-devel@quimby.gnus.org; Tue, 25 Nov 2003 07:07:47 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AObdg-0004Va-6I for emacs-devel@gnu.org; Tue, 25 Nov 2003 06:45:52 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AObaS-0003cc-V8 for emacs-devel@gnu.org; Tue, 25 Nov 2003 06:43:04 -0500 Original-Received: from [217.34.135.17] (helo=tf1.tapsellferrier.co.uk) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AObY7-0003CW-86 for emacs-devel@gnu.org; Tue, 25 Nov 2003 06:40:07 -0500 Original-Received: from [194.74.202.254] (helo=kanga.tapsellferrier.co.uk) by tf1.tapsellferrier.co.uk with esmtp (Exim 3.35 #1 (Debian)) id 1AOaZn-0003Wv-00; Tue, 25 Nov 2003 10:37:47 +0000 Original-Received: from localhost ([127.0.0.1] helo=kanga.tapsellferrier.co.uk ident=nferrier) by kanga.tapsellferrier.co.uk with esmtp (Exim 3.35 #1 (Debian)) id 1AOaZF-0006Oi-00; Tue, 25 Nov 2003 10:37:13 +0000 Original-To: storm@cua.dk (Kim F. Storm) In-Reply-To: Original-Lines: 61 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:18104 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18104 storm@cua.dk (Kim F. Storm) writes: > Juri Linkov writes: > > > I still think that there is no need to add Javascript and XSLT engines > > to Emacs. The solution you propose will be useful for web browsers > > because they have no other extensibility mechanisms. But Emacs could > > handle pages received from server by using local Emacs Lisp programs. > > The received pages could contain some indication about their type so > > that Emacs will decide what functions to call to handle them. And > > this is much safer than to embed Emacs Lisp code on the web pages. > > I totally agree. > > Just put something like > > > > into every page and let emacs info reader -- or stand-alone info > reader -- deal with that; should be damn trivial compared to XSLT or > javascript or whatever. > > But by all means, add whatever javascript and XML etc to make it > useful in a standard browser as well. This is not about altering the emacs info reader. This is about writing a new HTML publishing system for Texinfo. The arguments about adding Javascript and XSLT functionality to Emacs are about the functionality of Emacs/W3, _not_ about Emacs info mode. Whether the new publishing system relies on Javascript/XSLT or not is aside from the question of whether Javascript/XSLT functionality should be added to Emacs/W3. Clearly, Emacs/W3 is never going to be a competitive browser without those features. IMHO it's really not defensible to suggest that Emacs shouldn't have access to XSLT (the question is _how_). I can understand reservations about adding Javascript to emacs. Unfortunately, I can't see anyway of doing it other than linking the Javascript engine into emacs and rms has said he won't support that. If the new publishing system uses Javascript then Emacs/W3 won't be able to display the pages with all the functionality. If people here feel that a client side code system supporting emacs lisp would be useful then I think I could probably add that to W3 and support the 2 sets of code used for the publishing tool (Elisp and Javascript). Tagging might also be possible but this would require patching W3 to support this new info publishing system. That doesn't seem the right way round to me. Nic