Re: Réf . : Re: [Bug-gnubg] Python in Win32 GUI build ?

[Joern Thyssen]

On Wed, Oct 08, 2003 at 01:48:12PM +0200, address@hidden wrote
> 
> >On Wed, Oct 08, 2003 at 12:53:08PM +0200, address@hidden
> wrote
> >>
> >>
> >> What's the status in having Python support for Win32 builds ?
> >> It seems it is only available in the command-line one.
> >> Any hope ot have it in the GUI one(s) soon ?
> >
> >There is one big problem with python support in the GUI: I've not yet
> >managed to find out how to update the GUI while python is running. So as
> >soon as you go into python the GUI is "frozen", e.g., if you execute
> >gnubg.command("new match 7") you'll *not* see any updates in the GUI.
> 
> Hmm, nasty probelm. Maybe a Python command "update_gui" to execute each time
> we want the GUI updated. It's manual but maybe it can be added at the end of
> all the GNUbg-specific pythn commands (I'm totally new to Python, I'm just
> rambling).

Unfortunately, that will only partly cure the problem. Counter example:
(a) minimise gnubg (b) maximise gnubg. This requires repainting the
gnubg window, but this won't happen as the gui is "frozen", so you'll
see a grey/black/whatever frame.

> 
> >Apart from that it should be trivial to add python to the GUI build.
> >
> >Also note that you have to download and install python yourself in order
> >to get all the standard python libraries, e.g, "sys" or "os".
> >
> >Jørn
> 
> Hmmm, I've downloaded the libpython dll and the no-GUI builds works fine.
> 
> I've installed Python 2.2.3 but in the GUI build (old and panel/3D)
> the "Python shell (IDLE)" menu is always disabled. Maybe it is built
> without Python support (Nardy ?).

Yes, the GUI build is without python support. I think the reason is
partly that very few users want python support and partly due to the
frozen GUI problem. Besides, I guess that the typical user who wants
python support wouldn't mind using the no gui build.

> Assuming that's the problem, what should I do to build with Python
> support ? Just set USE_PYTHON to 1 (I guess it's somewhere in the
> makefiles or directly in the source) ?

If you roll you own builds you should #define USE_PYTHON 1 in config.h.
I assume the makefiles should be modified as well.

Jørn

pgpFeXM_m5LQJ.pgp
Description: PGP signature