bbyer at apple.com
Sat Dec 15 02:36:05 PST 2007
AFAIK, one of the big limiting factors here is that Xquartz has to
either live inside a .app bundle, or pretend to do so with exec/argv/
etc, in order to have a dock icon at all.
On Dec 14, 2007, at 12:04 PM, Jeremy Huddleston wrote:
> Well the one that "represents the X applications" *is* the X
> server. With the way things are in git, it's behaving like it was
> before 2.1.1. putting the app in the dock and clicking it launches
> a new xterm and a new icon represents the server. I'm actually fine
> with that, but I don't know how others will react.
> As it is, though, I believe disabling launchd support will still
> cause the 10.4 behavior.
> I know vmware does some weird hackery with .apps that cause it to
> "just work" as expected. I think we should just try putting as much
> of x11-exec and server_main() functionality into xinit and actually
> use that to start Xquartz (which loads its resources rather than
> grabbing them from X11.app with some weird argv and fork()ing
> What are peoples' thoughts?
> On Dec 14, 2007, at 04:45, Derek Fawcus wrote:
>> On Thu, Dec 13, 2007 at 11:43:33PM -0800, Jeremy Huddleston wrote:
>>> That way, people running Xquartz directly will see it with menus and
>>> the right icon. Also, I think this is a bit stronger from a
>>> engineering standpoint. The only problem with that is that we'll
>>> have a new two-icon icon issue when people put /A/U/X11.app in the
>>> dock... hrm...
>> So can we accept that but make them different?
>> i.e. have one icon for the Xserver, and one that sort of represents
>> the X applications? but I'm not sure what one would want to do wrt
>> to menus if / when switching between the two.
>> Xquartz-dev mailing list
>> Xquartz-dev at lists.macosforge.org
> Xquartz-dev mailing list
> Xquartz-dev at lists.macosforge.org
CoreOS / BSD Technology Group, XDarwin maintainer
More information about the Xquartz-dev