From: Eli Zaretskii <eliz@gnu.org>
To: joakim@verona.se
Cc: emacs-devel@gnu.org
Subject: Re: Initial documentation for xwidgets
Date: Fri, 12 Feb 2016 23:25:39 +0200 [thread overview]
Message-ID: <838u2p7h9o.fsf@gnu.org> (raw)
In-Reply-To: <m3ziv5d4cs.fsf@exodia.verona.se> (joakim@verona.se)
> From: joakim@verona.se
> Cc: emacs-devel@gnu.org
> Date: Fri, 12 Feb 2016 22:08:03 +0100
>
> I finally read the documentation you wrote for xwidgets, and it was really good thanks!
Are you sure? I cannot imagine I was that lucky. There are some
functions I didn't document, some of them in xwidget.c, others in
xwidget.el -- did I decide correctly which ones should be documented
and which shouldn't?
> I have just two things.
>
> - This fixme, I dont really have a good answer.
> @c FIXME: What else can a URI specify in this context?
> The uri is just any ury webkit accepts, which isnt a very helpful
> explanation of course.
Examples could help. Can you provide examples of URIs that are
neither URLs nor file names?
> - When I read the documentation I noticed the term 'webkit-osr'. -osr
> stands for 'off screen rendering'.
>
> There used to be different types of widgets, that weren't rendered
> off-screen. I don't think I will re-introduce those widgets because they
> were unreliable.
>
> So, there will likely only ever be osr widgets, which makes the osr suffix
> redundant.
>
> I guess people might have started tinkering with xwidget-osr.
>
> What do you think, should I change this, or does it not matter?
We can still change it, it's not too late.
Thanks.
next prev parent reply other threads:[~2016-02-12 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 8:13 Initial documentation for xwidgets Eli Zaretskii
2016-02-12 21:08 ` joakim
2016-02-12 21:20 ` Paul Eggert
2016-02-12 21:25 ` Eli Zaretskii [this message]
2016-02-12 21:35 ` joakim
2016-02-12 21:40 ` joakim
2016-02-12 21:55 ` Paul Eggert
2016-02-13 9:09 ` Eli Zaretskii
2016-02-13 9:09 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838u2p7h9o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.