public inbox for
 help / color / mirror / Atom feed
From: Alex Stark <>
To: Zach Frey <>,
Subject: Re: Common Gtk/GNOME language bindings?
Date: Fri, 21 Jan 2000 09:00:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

My 2c worth is that provision for very short documentation strings (ie
fewer than 60 chars) could be very useful.

As part of writing the tutorial examples, I found it pretty easy to
convert the defs files into human-friendly catalogues, and the really
neat thing with using guile-gtk is that it is simple to use
gtk-object-query-args to expand the information in the defs files.  One
could even validate features and procedures quite extensively.

IMHO, it is potentially of enormous benefit to be able to generate a
catalogue of features which is up-to-date.  (I have just wasted a lot of
time doing something trivial with RedHat rpms where the documentation is
confident but misleading, conflicting and obselete.)


  reply	other threads:[~2000-01-21  9:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-17  6:24 Miroslav Silovic
1999-12-17  6:52 ` Zach Frey
2000-01-21  9:00   ` Alex Stark [this message]
1999-12-17  8:11 ` James Henstridge

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).