[winGRASS] Re: [GRASS-user] Re: Xganim errors in WinGRASS

[yuri bay]

Glynn,

I am currently actively using winGRASS for my work because I could not 
afford the ridiculously expensive suit like the ArcGIS Desktop.  I have 
tried ArcGIS demo and with GRASS and winGRASS current ability has already 
surpassed ArcGIS Desktop in some areas.  I would also like to find out 'How 
To' and 'How Easy' we can extend winGRASS, in terms of adding 
functionalities, whether it is the interface/menu functions, or algorithms 
used to solve let say, network analysis problem.

>1. use the native version on a day-to-day basis, in spite of its
>current "alpha" quality, and
>2. take responsibility for getting any issues resolved.
>
>Point #2 doesn't necessarily mean that they need to fix any and all
>bugs themselves, but they will need to provide meaningful bug reports,
>apply and test any proposed fixes, etc.
>

I am more than happy to be part of the group to continuously providing bugs 
but as for testing fixes I am afraid with my humble (none!) knowledge on C 
and linux and software building and compiling, I could not help much.  
Having said that, I would be happy to help if members are willing to provide 
explanation on the detail steps involves in testing fixes in window terms, 
i.e. they do not really need to explain everything on the fixes / codes, 
just the steps on what/where/how to compile and test.

Thanks

Best Regards
Casey

>From: Glynn Clements <glynn at gclements.plus.com>
>To: Moritz Lennert <mlennert at club.worldonline.be>
>CC: grassuser at grass.itc.it, Hamish <hamish_nospam at yahoo.com>,        
>wingrass at grass.itc.it
>Subject: Re: [winGRASS] Re: [GRASS-user] Re: Xganim errors in WinGRASS
>Date: Thu, 8 Feb 2007 10:37:57 +0000
>
>
>Moritz Lennert wrote:
>
> > > (general call for packagers)
> > > It would sure be nice if someone produced a GRASS 6.2.1 Cygwin binary.
> > > Currently the most up-to-date binary available for the Cygwin version
> > > is 6.1-cvs April 17, 2006. i.e. there is still no stable GRASS 6.2
> > > available for Windows users -- what's the problem? shared libs?
> >
> > I think this is mainly due to the fact that we are not very far from a
> > real native windows version. I think dev efforts should rather be put
> > into that.
>
>Actually, I'd say that we're still quite a long way from having a
>*usable* native Windows version.
>
>Most of the people who have contributed to the native version don't
>normally use Windows[1]. Thus, they aren't likely to be as motivated
>to solve issues as would someone who actually has a *need* for a
>native Windows version.
>
>[1] At least, not for GRASS; I use it for playing games, watching
>videos, and running an X server so that I can do "work" on my Linux
>box without needing a second monitor/keyboard.
>
>A *usable* native Windows version is going to require one or more
>people who are willing to:
>
>1. use the native version on a day-to-day basis, in spite of its
>current "alpha" quality, and
>2. take responsibility for getting any issues resolved.
>
>Point #2 doesn't necessarily mean that they need to fix any and all
>bugs themselves, but they will need to provide meaningful bug reports,
>apply and test any proposed fixes, etc.
>
>Oh, we also need either a version of v.digit which doesn't require an
>interactive monitor (XDRIVER), or a port of the driver code (and the
>corresponding part of libraster) to Windows. Regarding the latter,
>it's the startup code from lib/driver/main.c which is the main issue;
>the X-specific stuff is already adequately handled by libW11.
>
>--
>Glynn Clements <glynn at gclements.plus.com>
>
>_______________________________________________
>winGRASS mailing list
>winGRASS at grass.itc.it
>http://grass.itc.it/mailman/listinfo/wingrass

_________________________________________________________________
MSN Hotmail is evolving – check out the new Windows Live Mail 
http://ideas.live.com