public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Alex Stark <jas@eng.cam.ac.uk>
To: Marius Vollmer <mvo@zagadka.ping.de>, guile-gtk@sourceware.cygnus.com
Subject: Re: Gtk tutorial examples
Date: Fri, 21 Jan 2000 03:51:00 -0000	[thread overview]
Message-ID: <3888485C.B47A0DB9@eng.cam.ac.uk> (raw)
In-Reply-To: <87k8l4b9m5.fsf@zagadka.ping.de>

Marius Vollmer wrote:
> 
...
> I think it would be a good thing for us to use this PROGRESS file as
> kind of guidance what to do next.  SO if anyone wants to contribute...
> 
> > I had major problems with selections and pixmaps,
> 
> I don't know about selections but pixmaps should be doable without
> much dirty work.  We can just use GdkWindow wherever Gdk uses
> GdkPixmap or GdkBitmap.
> 
> > and the almost total lack of documentation was a big pain. [:-)]
> 
> What did you miss specifically?  I'm curious with what people have
> problems.


I've expanded the explanatory files a bit.  (And I'll leave these alone
for now.)  If you want me to send the PROGRESS file to this list, send
an email to my address.

The files TRANSLATION and PROGRESS include notes on issues and problems
I encountered when translating the examples.  The TRANSLATION file has a
few notes on how and how not to do callbacks.  If these are wrong, tell
me.  I'd be happy to add explanatory notes anyone supplies.

PROGRESS contains three things: a list of specific problems encountered
with each example; a list of general issues; and a progress indicator
for each example.  In many cases there are very small outstanding
problems preventing the completion of an example.  It would be very
helpful if, when something in guile-gtk is fixed, a fix to the example
could also be passed on.

The list of general issues also serves as a list of things I found hard
to understand from the documentation.  To be honest, we really need a
central place for notes and tips.  The current documentation is cryptic
and limited.  If it weren't for the fact that 90% of the translation is
very easy, I wouldn't have got anywhere.  (In fact, the tar file
contains some sed filtering that does 60%. :-) )

None of these files (README, TRANSLATION, PROGRESS) should be taken as
at all definitive, but rather initial sketches.

Alex.

  reply	other threads:[~2000-01-21  3:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-18  7:09 gtk tutorial: missing? Alex Stark
2000-01-18 13:40 ` Gtk tutorial examples Alex Stark
2000-01-20 21:03   ` Marius Vollmer
2000-01-21  3:51     ` Alex Stark [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-12-09 11:57 Gtk Tutorial examples Alex Stark
1999-12-09 13:43 ` ariel
1999-12-09 14:43   ` Alex Stark
1999-12-09 17:53     ` ariel

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=3888485C.B47A0DB9@eng.cam.ac.uk \
    --to=jas@eng.cam.ac.uk \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=mvo@zagadka.ping.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).