unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Adrian Robert <adrian.b.robert@gmail.com>
To: "emacs-devel@gnu.org Development" <emacs-devel@gnu.org>
Subject: State of NS port
Date: Thu, 10 Jan 2013 11:27:27 -0500	[thread overview]
Message-ID: <69E12347-B799-48E4-AE1A-115365CEA4C8@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]

Hi,

I built the NS port of emacs under Mac OS X 10.8 today from trunk.  I realize a tremendous amount of work over the years has been done to clean up various glitches in menus, rendering, event handling, etc., many caused by my own poor work, but I was really disappointed to see some big steps backwards in basics.  Here is a screenshot of the HELLO file from today on left, and a version from 3 years ago on the right.

I've stepped back my direct involvement in the port to find more time to focus on other things, and I appreciate the work of others who have taken up the slack.  But glaring issues like extra blank space in the window, nonconformance to the system standard edge-rounding, and poor text rendering in the prevailing Carbon port (at the time) were part of what led me originally to resurrect the NS port to begin with back in 2004.

I don't know if the current steps backwards are due to the lack of maintenance in keeping up with internal core changes, or due to inadvertent and/or accepted losses in the course of making port enhancements.  But I would request that when people make changes, they keep an eye out for regressions introduced by them, and refrain from committing improvements that introduce new (or old) problems.

All I can do is make this request humbly, and apologize for my own lack of involvement, which while it has surely led to improvement of the codebase overall, seems to have caused some penalty as well.

respectfully,
Adrian


[-- Attachment #2.1: Type: text/html, Size: 2011 bytes --]

[-- Attachment #2.2: Screen-Shot-2013-01-10-at-11.08s.png --]
[-- Type: image/png, Size: 215457 bytes --]

             reply	other threads:[~2013-01-10 16:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 16:27 Adrian Robert [this message]
2013-01-10 18:53 ` State of NS port chad
2013-01-10 19:28 ` Stefan Monnier
2013-01-12  3:49 ` Chris Zheng
2013-01-12 10:09   ` Jan Djärv
2013-01-14  2:44     ` Chris Zheng
2013-01-14  9:35       ` Jan Djärv
2013-01-12 14:58   ` Harald Hanche-Olsen
2013-01-12 16:41     ` Jan Djärv
2013-01-15 17:57       ` Adrian Robert
2013-01-15 20:47         ` Jan Djärv
2013-01-16 13:46           ` Adrian Robert
2013-01-13  8:14   ` YAMAMOTO Mitsuharu
2013-01-13 12:23     ` Jan Djärv
2013-01-13 14:09     ` Jan Djärv
2013-01-14  3:07       ` YAMAMOTO Mitsuharu
  -- strict thread matches above, loose matches on Subject: below --
2013-01-11  1:38 David Kanter
2013-01-11 16:13 ` Jan Djärv

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=69E12347-B799-48E4-AE1A-115365CEA4C8@gmail.com \
    --to=adrian.b.robert@gmail.com \
    --cc=emacs-devel@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).