git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seth Falcon <seth@userprimary.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Trouble with gitk and ActiveState tcltk on OS X
Date: Mon, 11 Feb 2008 07:51:35 -0800	[thread overview]
Message-ID: <m2zlu71ofs.fsf@userprimary.net> (raw)
In-Reply-To: 20080211044941.GX24004@spearce.org

"Shawn O. Pearce" <spearce@spearce.org> writes:
> For what its worth I use the native Tcl/Tk that ships with Mac OS X,
> /usr/bin/wish, which is really in /Library/Frameworks/Tk.framework.
> I've never used the ActiveState Tcl/Tk package on Mac OS X.
>
> git-gui builds against the Tk.framework I mentioned above when on
> Mac OS X.  In particular the git-gui Makefile seems to ignore the
> setting of TCLTK_PATH when it sees the above mentioned Tk.framework
> is available in your filesystem.
>
> The reason why you get nice icons for git-gui is because we use a
> feature of the Aqua port Tcl/Tk framework that allows us to create a
> full Mac OS X app by copying a tiny executable from the framework,
> and supplying our own resource bundle.  The bundle configures
> the icon.  Its the only way to get a custom icon on Mac OS X.
>
> Launching gitk from within git-gui (Repository -> Visualize History)
> uses the same app and bundle, so gitk inherits the icon too.
> I'd also bet gitk works this way, because it isn't launching through
> the ActiveState Tcl/Tk port.
>
> In short, why not just use the native Aqua Tcl/Tk that Apple ships?
> Why go through X11 and MacPorts?

Hmm.  I don't doubt that I've inadvertently made things harder than
they need to be, but...

I've just tried uninstalling the ActiveState stuff and removing the
MacPorts stuff.

Indeed git gui runs, but I no longer get the nice icon (instead a
default Tcl/Tk icon with a feather).  Launching gitk from the git gui
menu results in the same behavior for me: it launches and its menu
appears, but no window.  It is quite odd because I can open the
preference window for gitk via the menu and _that_ mini window does
appear.  Same thing if I launch gitk from the command line.

If I try to open the "Git Gui.app" I get:
ziti:git-gui seth$ open Git\ Gui.app/
LSOpenFromURLSpec() failed with error -10810 for the file /Users/seth/src/git-MASTER/git-gui/Git Gui.app.

I've recently upgraded my system to Leopard, so I wouldn't be
surprised if that is related to some of these issues.

Is there a big difference between how git gui uses Tcl/Tk and gitk?
It seems really odd to me that one works and the other not so much :-\

Any other things to try or suggestions of where to look for root
causes?

Thanks again,

+ seth


-- 
Seth Falcon | seth@userprimary.net | blog: http://userprimary.net/user/

  parent reply	other threads:[~2008-02-11 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10 21:15 Trouble with gitk and ActiveState tcltk on OS X Seth Falcon
2008-02-11  4:49 ` Shawn O. Pearce
2008-02-11  8:26   ` Kalle Olavi Niemitalo
2008-02-11 15:51   ` Seth Falcon [this message]
2008-02-11 17:59   ` Jay Soffian

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=m2zlu71ofs.fsf@userprimary.net \
    --to=seth@userprimary.net \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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.
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 NNTP newsgroup(s).