public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Rottmann <a.rottmann@gmx.at>
To: Steve Tell <tell@telltronics.org>
Cc: guile-gtk@sources.redhat.com
Subject: Re: (gnome gtk) et al
Date: Fri, 11 Apr 2003 10:00:00 -0000	[thread overview]
Message-ID: <871y09iclk.fsf@alice.rotty.yi.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0304110035290.3979-100000@ariel.lan.telltronics.org>

Steve Tell <tell@telltronics.org> writes:

> On Tue, 8 Apr 2003, David Pirotte wrote:
> 
> > > I really wonder why so few people seem interested in GTK+ 2.0
> > > bindings. I'd love to have Goops-based bindings for 2.0 (OO is really
> > > nice, if not necessary ;-) when dealing with widget sets IMO), and
> > > could lend a hand from time to time.
> > 
> > I really really would like to have goops-based any bindings, but Gtk+ 2.0
> > would be a must, I backup the idea
> 
> I'm interested in gtk+-2.0 (without requiring gnome) bindings also, and
> not only becaused I've been asked when some code of mine will build work
> with gtk+-2.0/2.2.
> 
> Not knowing much about goops yet, what would such bindings look like? I'd
> prefer to have somthing that is largely code-compatible with the current
> guile-gtk for gtk+-1.2.  Idealy I'd like a single guile+C codebase to be
> able to support both gtk+-1.2 and gtk+2.x for some transition period.
> It looks like this is reasonably straightforward for pure C uses of gtk+.
> 
Goops bindings would look quite different and would be much easier to
use because you won't have to specify the type of the widget in the
procedure name, eg. (gtk-widget-show w) will become (show w).

I think we should have a .def parser that can generate g-wrap modules
with an old-style interface and a goops-based interface (once g-wrap
supports goops, which I'd like to help at).

Andy
-- 
Andreas Rottmann         | Rotty@ICQ      | 118634484@ICQ | a.rottmann@gmx.at
http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

Make free software, not war!

  reply	other threads:[~2003-04-11 10:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030407144511.GA1489@lark>
2003-04-07 19:57 ` Ariel Rios
2003-04-07 20:15   ` Andreas Rottmann
2003-04-08 10:34     ` Marius Vollmer
2003-04-08 14:56   ` Stan Pinte
2003-04-08 20:03     ` Andreas Rottmann
2003-04-08 21:33       ` David Pirotte
2003-04-11  4:48         ` Steve Tell
2003-04-11 10:00           ` Andreas Rottmann [this message]
2003-04-09 15:24       ` Stan Pinte
2003-04-10 17:05         ` Andreas Rottmann
2003-04-10 17:10           ` David Pirotte
2003-05-06  6:52     ` Stan Pinte
2003-05-06 15:33       ` Marius Vollmer
2003-05-06 15:45         ` Stan Pinte
2003-05-07 13:07           ` Stan Pinte
2003-05-07 14:02             ` Stan Pinte
2003-05-07 14:10               ` Marius Vollmer
2003-05-07 14:38                 ` Stan Pinte
2003-05-07 15:17                   ` Stan Pinte
2003-05-07 18:16                     ` Marius Vollmer
2003-05-08 11:43                       ` Stan Pinte
2003-05-12 14:18                         ` Stan Pinte
     [not found]                           ` <1052750737.26632.4.camel@tosca.elektra.com.mx>
2003-05-12 16:48                             ` Stan Pinte
2003-05-14  9:17   ` Andy Wingo
2003-05-16 14:26     ` Andreas Rottmann
2003-05-20 20:08       ` Andreas Rottmann
2003-05-23 22:00         ` Kevin Ryde
2003-05-26 13:04           ` Andreas Rottmann
2003-06-23 14:14   ` Andy Wingo

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=871y09iclk.fsf@alice.rotty.yi.org \
    --to=a.rottmann@gmx.at \
    --cc=guile-gtk@sources.redhat.com \
    --cc=tell@telltronics.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 read-only IMAP folder(s) and NNTP newsgroup(s).