[GRASS5] XDRIVER popup bug

Markus Neteler neteler at geog.uni-hannover.de
Thu May 25 05:12:37 EDT 2000

On Wed, May 24, 2000 at 01:02:02AM -0400, Carl Anderson wrote:
> Markus Neteler wrote:
> > > its stuff.  I hope that moving from file/fifo's to sockets help that,
> > > so that nasty line can be dropped.
> > Did you find time to look for that? I am just interested
> > as the windows port (by John) requires such sockets.
> > Maybe he or someone else could assist?
> > 
> I finally got Cygwin and GCC2.95.2 up and running today.  I have some
> sample code but I want to try it out on Win32 before passing it on. Socket
> implementations have issues and sockets is a big change that needs
> thorough testing before acceptance.
Maybe John can test as well on his WIN-Port.

> Did you know that GTK has been ported to Win32 and can generate windows
> without needing X.  After getting sockets up and running someone could
> create a g[0-9] driver.  This may overcomplicate or uncomplicate GRASS
> monitors.
Wow, sounds very good. This might simplify the install procedure
on WIN systems.

> So if it and X were supported by GRASS It could help portability.
> I AM NOT SUGGESTING DROPPING X Support only adding a driver to allow 
> our Win32 friends to not have to add external software (X) to use GRASS.
I agree. As both drivers can co-exist it should not be a problem.

Concerning all:
The branching should be started. I fear I need some assistance to
avoid problems. As GRASS 5 is currently working pretty good (of
course bugs exist), I may start the next days. Or is branching
as trivial as tagging? Two version tags are already applied.
So I will read again the CVS book...

Best wishes


If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'

More information about the grass-dev mailing list