Hi,
I am trying to use the 'xganim' function (in WinGRASS) to animate a series of vectors (converted from shapefiles) but has encountered the following attached errors. Any advice is much appreciated.
Many thanks
Best Regards
Casey
_________________________________________________________________
MSN Hotmail is evolving – check out the new Windows Live Mail http://ideas.live.com
Xganim_CouldNotFind.log (449 Bytes)
On 06/02/07 14:18, yuri bay wrote:
Hi,
I am trying to use the 'xganim' function (in WinGRASS) to animate a series of vectors (converted from shapefiles) but has encountered the following attached errors. Any advice is much appreciated.
AFAIK, this module is not available in WinGRASS at the moment.
Moritz
yuri bay wrote:
I am trying to use the 'xganim' function (in WinGRASS) to animate a series
of vectors (converted from shapefiles) but has encountered the following
attached errors. Any advice is much appreciated.
couldn't execute "xganim": no such file or directory
Clearly, this component isn't included in the WinGRASS binary
packages. xganim requires Motif (it's currently the only module which
does);
Cygwin provides a package for LessTif (which should work), so there
isn't any fundamental reason why xganim can't be provided on Cygwin;
it just requires whoever builds the Cygwin packages to install LessTif
and use --with-motif when configuring GRASS.
OTOH, it isn't really an option for the native Windows (MSys) version;
the only native Motif libraries for Windows cost money.
--
Glynn Clements <glynn@gclements.plus.com>
yuri bay wrote:
> I am trying to use the 'xganim' function (in WinGRASS) to animate a series
> of vectors (converted from shapefiles) but has encountered the following
> attached errors.
Another (Cywgin required) solution:
d.slide.show -v across=1 down=1
Glynn:
Clearly, this component isn't included in the WinGRASS binary
packages. xganim requires Motif (it's currently the only module which
does);Cygwin provides a package for LessTif (which should work), so there
isn't any fundamental reason why xganim can't be provided on Cygwin;
it just requires whoever builds the Cygwin packages to install LessTif
and use --with-motif when configuring GRASS.
(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?
Hamish
Hi,
Hamish, thanks for the reply. If I need to use the solution you have suggested, does that mean I need to uninstall the native binary winGRASS so that I can install the Cygwin binary one?? I have tried to use d.slide.show but there is no response nor errors.
Thanks
Regards
Casey
From: Hamish <hamish_nospam@yahoo.com>
To: Glynn Clements <glynn@gclements.plus.com>
CC: ksh_wong@msn.com, grassuser@grass.itc.it, wingrass@grass.itc.it
Subject: Re: [GRASS-user] Re: Xganim errors in WinGRASS
Date: Wed, 7 Feb 2007 12:25:26 +1300> yuri bay wrote:
> > I am trying to use the 'xganim' function (in WinGRASS) to animate a series
> > of vectors (converted from shapefiles) but has encountered the following
> > attached errors.Another (Cywgin required) solution:
d.slide.show -v across=1 down=1Glynn:
> Clearly, this component isn't included in the WinGRASS binary
> packages. xganim requires Motif (it's currently the only module which
> does);
>
> Cygwin provides a package for LessTif (which should work), so there
> isn't any fundamental reason why xganim can't be provided on Cygwin;
> it just requires whoever builds the Cygwin packages to install LessTif
> and use --with-motif when configuring GRASS.(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?Hamish
_________________________________________________________________
Get Hotmail, News, Sport and Entertainment from MSN on your mobile. http://www.msn.txt4content.com/
On 07/02/07 00:25, Hamish 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.
Moritz
yuri bay wrote:
If I need to use the solution you have suggested, does that mean I
need to uninstall the native binary winGRASS so that I can install
the Cygwin binary one?? I have tried to use d.slide.show but there is
no response nor errors.
Sorry, I don't know much about installing GRASS on Windows. Hopefully
someone else can answer?
d.slide.show will need an X-monitor to run, and that is only available
with X-Windows from the Cygwin.
Hamish
Moritz Lennert wrote:
Hamish 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.
In the mean time there is not a 100% functional version, or for that
matter any Stable version, available for Windows users- and who knows
how long it will take for the MSys port to be ready? A month? 6? Is it
really much more work to prepare than just a simple compile & .zip using
a clean Cygwin install? It would be nice to release 6.2.1 for Cygwin
regardless of 6.3 native success. Also it helps to isolate bugs by
having two ports to test with, using different methods.
Hamish
I second this. Of course, I don't know how to do this and so can't offer
much help.
Michael
On 2/7/07 3:59 PM, "Hamish" <hamish_nospam@yahoo.com> wrote:
In the mean time there is not a 100% functional version, or for that
matter any Stable version, available for Windows users- and who knows
how long it will take for the MSys port to be ready? A month? 6? Is it
really much more work to prepare than just a simple compile & .zip using
a clean Cygwin install? It would be nice to release 6.2.1 for Cygwin
regardless of 6.3 native success. Also it helps to isolate bugs by
having two ports to test with, using different methods.
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University
phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
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@gclements.plus.com>
On 08/02/07 11:37, Glynn Clements wrote:
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.
I agree and I know I have been absent on this for a while, but hope to find more time now. Although, I have to admit that I am in the position Glynn describes, not using Windows regularly.
But as we are discussing the possibility of moving GIS teaching and research in our department to GRASS I am motivated to get this up and running since forcing everyone to use Linux will have to come in a later stage 
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.
I now have a working windows machine at my disposition and hope, therefore, to find more time to test.
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.
I personally think that we should aim for the first solution as in the general gui work we are trying to become as independent from the monitors as possible and v.edit already seems more or less ready for this, or ?
Moritz
On 08/02/07 11:37, Glynn Clements wrote:
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.
Just to add to this: I think it is time that we publish a more recent version of WinGRASS. The one which people get to now from the downloads page is way out of date and any current version would be better than that. In addition, this would allow us to have more alpha-testers.
Paul, as you are the one working most closely on WinGRASS do you want to do this ?
If not, I am willing to try to publish a regular binary snapshot of current CVS. I don't know if I can promise weekly, but I could try.
Moritz
On Fri, 9 Feb 2007, Moritz Lennert wrote:
On 08/02/07 11:37, Glynn Clements wrote:
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.Just to add to this: I think it is time that we publish a more recent version of WinGRASS. The one which people get to now from the downloads page is way out of date and any current version would be better than that. In addition, this would allow us to have more alpha-testers.
Yes, Huidae's version is more Msys-GRASS than Windows-GRASS. It depends on having Msys installed, also depends on various Msys-related modifications to the source code which have been removed now.
Paul, as you are the one working most closely on WinGRASS do you want to do this ?
I don't like the idea of putting out a version that has the vector-DB connectivity completely broken. I think it would give a bad impression.
Apart from that it would not be too hard to do. You could include the Mingw Tcl/Tk within the distribution too, and the required libraries (GDAL, PNG etc.) It could just be a big zip file that could be unzipped anywhere, with only the path in grass63.bat needing to be changed to suit it. grass63.bat could be saved anywhere and then a desktop shortcut created to start it up.
Paul