From: Bastien Guerry <bzg@gnu.org>
To: "Elias Mårtenson" <lokedhs@gmail.com>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Condition to link to javascript code?
Date: Mon, 19 Dec 2016 17:32:19 +0100 [thread overview]
Message-ID: <878trb517w.fsf@bzg.fr> (raw)
In-Reply-To: <CADtN0WKmqOC3kBOJgt4hJF8mRNwRjcCdRjGk3YdAr6hp2mY61A@mail.gmail.com> ("Elias Mårtenson"'s message of "Mon, 19 Dec 2016 16:46:57 +0800")
Hi Elias,
Elias Mårtenson <lokedhs@gmail.com> writes:
> But if you solve the problem for people on airplanes, then it's be
> solved for everybody else since there will be no need to download
> anything from a Google server, or did I completely misunderstand what
> this tool does?
If everybody uses the resulting HTML on its own computer, then the
problem is solved: the HTML refers to a local klipse.js libarary that
the user can freely use.
But I expect most people want to put the resulting HTML somewhere on
a web server. In this case, they might find useful to use klipse.js
by linking to the location of that library.
I'm not opposed to the "host-everything-you-can" solution but I need
to understand what are the conditions for linking to an external
javascript library, provided that this library is GLPv3, passes the
librejs tests successfully, and is hosted on Google's server.
--
Bastien
next prev parent reply other threads:[~2016-12-19 16:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 3:01 Condition to link to javascript code? Bastien
2016-12-15 3:41 ` Clément Pit--Claudel
2016-12-15 12:12 ` Bastien
2016-12-17 15:47 ` Richard Stallman
2016-12-18 17:47 ` Bastien Guerry
2016-12-19 7:20 ` Elias Mårtenson
2016-12-19 8:06 ` Bastien Guerry
2016-12-19 8:46 ` Elias Mårtenson
2016-12-19 16:32 ` Bastien Guerry [this message]
2016-12-19 16:52 ` Clément Pit--Claudel
2016-12-20 18:15 ` Richard Stallman
2016-12-20 19:10 ` Davis Herring
2016-12-21 17:14 ` Richard Stallman
2016-12-21 11:28 ` Rasmus
2016-12-21 17:18 ` Richard Stallman
2016-12-22 10:24 ` Rasmus
2016-12-22 19:56 ` Richard Stallman
2016-12-23 13:40 ` Achim Gratz
2016-12-23 16:18 ` Richard Stallman
2016-12-24 11:41 ` Achim Gratz
2016-12-24 18:55 ` Richard Stallman
2016-12-25 10:04 ` Achim Gratz
2016-12-25 20:43 ` Richard Stallman
2016-12-22 3:13 ` Christopher Allan Webber
2016-12-22 19:54 ` Richard Stallman
2016-12-23 13:33 ` Achim Gratz
2016-12-23 16:18 ` Richard Stallman
2016-12-19 13:44 ` Stefan Monnier
2016-12-19 13:07 ` Richard Stallman
2016-12-19 17:01 ` Bastien Guerry
2016-12-20 18:16 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878trb517w.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lokedhs@gmail.com \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).