ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Marco <netuse@lavabit.com>
Subject: Re: GUI for minimals WAS: Re: [t-rst] inclusion into Minimals, i. e. installation using `./first-setup.sh --extras='t-rst'`
Date: Mon, 09 May 2011 10:03:35 +0200	[thread overview]
Message-ID: <4DC79FD7.1020903@elvenkind.com> (raw)
In-Reply-To: <20110508220741.51fc0c36@glyph>

On 05/08/2011 10:07 PM, Marco wrote:
> On 2011-05-09 Pontus Lurcock<pont@talvi.net>  wrote:
>
>> On Sun 08 May 2011, Marco wrote:
>>
>>> If  we prefer  TK  over GTK  why not  use  the lua  Tk
>>> bindings?
>>
>> When I saw this discussion starting I googled the Lua Tk
>> bindings,  and it  turned out  [1] that  they apparently
>> haven't been updated since 1998.
>
> What about  ltcltk [1],  it's from  2010? However  I never
> used  it,  I just  did  some  simple  GUIs with  the  GTK+
> binding.

There is a real, serious problem with the predictability of GTK+
installations on macosx. It feels like each version of macosx in
either 32 or 64 bit needs a different version of the bundle, and
on top of that it hard to predict which one is needed.

Installation of any GTK+ bundle always appears to work, but if you
have the wrong one the runtime crashes.

Best wishes,
Taco

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2011-05-09  8:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-01 10:18 Paul Menzel
2011-05-01 11:18 ` Mojca Miklavec
2011-05-01 12:33   ` Peter Münster
2011-05-01 12:37     ` Mojca Miklavec
2011-05-01 14:14   ` Aditya Mahajan
2011-05-02  5:58     ` Mojca Miklavec
2011-05-04 17:00   ` Philipp Gesang
2011-05-04 22:02     ` Aditya Mahajan
2011-05-05  9:47       ` Philipp Gesang
2011-05-06 18:55     ` Mojca Miklavec
2011-05-06 19:04       ` Aditya Mahajan
2011-05-06 19:08       ` Marco
2011-05-07 15:36         ` Mojca Miklavec
2011-05-08 11:18           ` Taco Hoekwater
2011-05-08 14:17             ` Marco
2011-05-08 19:43               ` Pontus Lurcock
2011-05-08 20:07                 ` GUI for minimals WAS: " Marco
2011-05-09  8:03                   ` Taco Hoekwater [this message]
2011-05-08 14:56             ` Arthur Reutenauer
2011-05-08 17:36               ` Hans Hagen
2011-05-08 18:17                 ` Mojca Miklavec
2011-05-08 21:00                   ` Marco
2011-05-08 21:28                     ` Thomas A. Schmitz
2011-05-08 22:17                       ` Marco
2011-05-08 14:01           ` Marco
2011-05-07 10:19       ` Philipp Gesang
2011-05-07 11:23         ` Wolfgang Schuster
2011-05-07 12:08           ` Philipp Gesang
2011-05-07 15:45         ` Mojca Miklavec
2011-05-08 18:32           ` Philipp Gesang

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=4DC79FD7.1020903@elvenkind.com \
    --to=taco@elvenkind.com \
    --cc=netuse@lavabit.com \
    --cc=ntg-context@ntg.nl \
    /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).