From: Dmitry Antipov <dmantipov@yandex.ru>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: GTK scroll bar question
Date: Thu, 31 Jul 2014 19:13:53 +0400 [thread overview]
Message-ID: <53DA5D31.9000905@yandex.ru> (raw)
In-Reply-To: <258DF241-B761-4DD8-9CDD-278785FC4A39@swipnet.se>
On 07/31/2014 03:53 PM, Jan Djärv wrote:
> We want to get rid of those as they are a performance hit.
Less widgets is not necessary means more performance.
> The first Gtk+ version I made did not use handle_one_xevent, but it was
> decided that the code in handle_one_xevent should be reused. So it is
> a no-brainer to replace it, it is just a lot of work.
>
> The reason is that we have a lot of code in other places to handle timers
> and other things (the whole xg_select.c file for example) that only comes
> from not running the Gtk+ event loop.
It just confirms that Emacs is not a first-class Gtk+ citizen and will always
have OS- and so window system-specific code.
> It is true that Cairo don't use pixmaps
What do you mean about "don't use"?
* xlib: Uses the Xlib interface to the X Window System. This backend can target
Windows or Pixmaps. The Render extension is used if available, but is not required.
(http://cairographics.org/backends).
>> In particular, this will require
>> new redisplay interface to replace x_redisplay_interface
>
> No it will not.
Get your favorite function from x_redisplay_interface and try to redesign
it by using only Gtk+ and Cairo interfaces. Do not assume that Gtk+ is
backed by X, so no way to access underlying Display, Window, GC, etc.
I'm pretty sure you eventually finish with gtkterm.c :-).
> From what was contained in the Gtk+ port only, you now distribute to three files,
> and enlarge a struct for no good reason. That is not elegant IMHO.
Pointers to Gtk+ widgets are OK in x_output, which is actually a part of frame.
So I don't see why it's so bad for scroll bars, especially if it's going to
replace _larger_ data structure with non-zero maintenance cost.
>> With all possible respect, we can't direct each other to do or not to do
>> something. And we shouldn't, isn't it?
>
>
> So when you can checkin to the Emacs tree, you feel you are in your right to
> break code and generally change it so that the people that try to maintain
> it can't recognize anymore?
Please re-read above. I mean "do", which is not always the same as "checkin".
Dmitry
next prev parent reply other threads:[~2014-07-31 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 11:11 GTK scroll bar question Dmitry Antipov
2014-07-30 12:39 ` martin rudalics
2014-07-30 15:38 ` Dmitry Antipov
2014-07-30 18:30 ` Jan Djärv
2014-07-31 5:05 ` Dmitry Antipov
2014-07-31 6:52 ` Jan D.
2014-07-31 10:19 ` Dmitry Antipov
2014-07-31 11:53 ` Jan Djärv
2014-07-31 15:13 ` Dmitry Antipov [this message]
2014-07-31 15:27 ` Jan D.
2014-07-31 14:20 ` GTK scroll bar artifacts [Was: Re: GTK scroll bar question] Dmitry Antipov
2014-07-31 15:03 ` Jan D.
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=53DA5D31.9000905@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.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 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).