Re: [pygtk] Python 2.1 / Gtk+ 2.0

2001-03-14 Thread James Henstridge

On Wed, 14 Mar 2001, Peter Kese wrote:

 
 Hi!
 
 I am planning a project based on pygtk in which I am planning to use
 
   Python 2.1
   NumPy 18.0  - makes use of new Python 2.1 features
   PyGtk   - as I need to be portable to Unix and Windows
   GdkPixbuf
 
 As it is probably going to take me months to complete it, I thought it
 might be wise to start the project with Gtk 1.4 or 2.0.

First of all, there will never be a gtk 1.4 (they decided that about
a year ago).  Note that 2.0 is still under development at the moment, so
is not a great platform to target unless you are willing to track
development.  However, gtk 2.0 should be out soon.

 
 Therefore I am wondering:
 1) are there any PyGtk for Gtk 1.4 / 2.0 beta available, (when, how)

The HEAD branch of CVS is targeted at 2.0, but currently is not up to date
(will not compile with current HEAD glib/pango/gtk+).  There are some
snapshots I made available at:
  http://www.gnome.org/~james/

 2) does PyGtk 0.6.X compile with Python 2.1

No reason why it shouldn't.  I don't think the C API has really changed
much since 1.4 (or maybe earlier; 1.4 was the first release I started
writing extensions for).

James.


___
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk



Re: [pygtk] Python 2.1 / Gtk+ 2.0

2001-03-14 Thread Tom Cato Amundsen

On Wed, Mar 14, 2001 at 02:07:35PM -0600, Skip Montanaro wrote:
 
 Okay, I'm confused.  On the one hand, James says:
 
 James First of all, there will never be a gtk 1.4 (they decided that
 James about a year ago)...
 
 then later writes:
 
 James I don't think the C API has really changed much since 1.4 (or
 James maybe earlier; 1.4 was the first release I started writing
 James extensions for).
I think this version 1.4 is Python 1.4.

 
 Are these two different 1.4's you're referring to?  I'm particularly
 interested in this because I am gearing up to work on a project that will
 use 2.0.
 
 thx,
 
 -- 
 Skip Montanaro ([EMAIL PROTECTED])
 (847)971-7098
 
 ___
 pygtk mailing list   [EMAIL PROTECTED]
 http://www.daa.com.au/mailman/listinfo/pygtk
 

-- 
Tom Cato Amundsen [EMAIL PROTECTED]
GNU Solfege - free eartraining, http://www.gnu.org/software/solfege/

___
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk



Re: [pygtk] Python 2.1 / Gtk+ 2.0

2001-03-14 Thread James Henstridge

On Wed, 14 Mar 2001, Skip Montanaro wrote:

 
 Okay, I'm confused.  On the one hand, James says:
 
 James First of all, there will never be a gtk 1.4 (they decided that
 James about a year ago)...
 
 then later writes:
 
 James I don't think the C API has really changed much since 1.4 (or
 James maybe earlier; 1.4 was the first release I started writing
 James extensions for).
 
 Are these two different 1.4's you're referring to?  I'm particularly
 interested in this because I am gearing up to work on a project that will
 use 2.0.

You have taken my response out of context :)  The question was whether
pygtk worked with python 2.1, and I was saying that the C API (of
python) has not changed incompatibly for a long time.

BTW, gtk+ HEAD (what will be gtk+ 2.0) is already very good.  It has
replacement text and tree widgets; both with model/view split.  GTK+ now
also does flicker free drawing and exposure compression by default, so gtk
apps should look as smooth as Tk apps (while gtk+ is in fact faster than
Tk, many people seem to beleive otherwise, because gtk+ 1.2 
flickers).

Then there is pango.  This handles all the internationalised text issues
(multiple scripts, different text directions, etc).  Now all of the GTK+
functions that display text to the screen take UTF-8 character
strings.  By setting the python's default encoding to UTF-8, pygtk allows
you to pass in python unicode strings to these functions, and they will be
handled appropriately.  Pango also has an Xft backend, which allows for
anti aliased text rendering on the X11 target for servers with the RENDER
extension (ie. XFree86 4.0.x).

There are also more targets in 2.0 -- win32 and linux-fb have been
incorporated into the main sourcetree in addition to x11 (there was a
win32 port before, but was never integrated into the main tree).  You can
simply recompile pygtk with another target and it should work.  I am
considering changing the pygtk build process so that you can install pygtk
for more than one target, and "import gtk" decides which to use, allowing
your app to run both on x11 and framebuffer automatically.

James.


___
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk



Re: [pygtk] Python 2.1 / Gtk+ 2.0

2001-03-14 Thread Skip Montanaro


James You have taken my response out of context :) The question was
James whether pygtk worked with python 2.1, and I was saying that the C
James API (of python) has not changed incompatibly for a long time.

Thanks for the clarification.  It hadn't occurred to me that the second 1.4
referred to Python 1.4.  That's pretty damn ancient in Internet years... ;-)

James BTW, gtk+ HEAD (what will be gtk+ 2.0) is already very good.  

How soon before we get a peek at PyGTK for gtk+ 2.0?

Skip


___
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk