[GRASS-windows] Re: [GRASS-user] Xming as X server for winGRASS?

[Isaac Ullah]

>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 07 Mar 2008 17:47:46 +0100
> From: Luigi Ponti <lponti at infinito.it>
> Subject: [GRASS-windows] Re: [GRASS-user] Xming as X server for
>        winGRASS?
> To: Paul Kelly <paul-grass at stjohnspoint.co.uk>
> Cc: grass-user at lists.osgeo.org, grass-windows at lists.osgeo.org
> Message-ID: <47D171B2.9070603 at infinito.it>
> Content-Type: text/plain; charset=ISO-8859-3; format=flowed
>
> Dear Paul,
> thanks for your prompt reply.
>
> Paul Kelly wrote:
> > On Fri, 7 Mar 2008, Luigi Ponti wrote:
> >
> > A better course of action might be to try to revive the w11 driver
> > (--enable-w11 configure option) which is similar but uses Windows
> > functions instead of sockets. I don't know how near being finished it
> > is; might be worth looking at.
> The most recent thread I have found on the topic suggests that this is
> still not a viable option.
> http://www.nabble.com/GRASS-.-configure-options-td15482716.html#a15489963
> >
> > There's some discussion if you search the mailing lists for keywords
> > like w11 and pngdriver. It isn't necessary to have the XDRIVER working
> > for batch display functionality - you can use the PNG driver (in fact
> > that is probably easier) and direct rendering on Windows--or on any
> > other platform. See the list of PNG driver-related environment
> > variables in
> > http://grass.ibiblio.org/gdp/html_grass63/variables.html#png for some
> > ideas on how to control it.
> If anybody has a pointer to a working example that would be great. While
> the concept is clear, the practicalities are not as evident by reading
> recent posts on the topic:
>
> http://www.nabble.com/why-d.vect.thematic-won%27t-run-on-WinGRASS---d.mon-problem-td15054987.html#a15054987
>
> Particularly, how do you tell the PNG driver where to start/stop direct
> rendering to png file without d.mon?
> > Paul
> >
> Thanks and regards,
>
> Luigi
>



Luigi,

    The current TCL GUI uses the PPM driver to create all of it's displays
... It writes all the displays to a single .ppm graphics file and then
displays this in the TCL map canvas. This all runs natively in Windows, and
could probably be easily changed to use any other sort of display driver you
would wish. You should look at the code in  "grass63RC4\grass-
6.3.0RC4\etc\d.rast.edit.tcl" to see exactly how it works.
   Also, just to add my 2 cents, the TCL map display is so much better than
the old X11 monitors that I wouldn't think there was any advantage to trying
to code anything remotely "X-like" for WinGRASS. Eventually, in the next
version of GRASS, the python-based interface and map display tools will be
miles beyond even what's available in the current TCL one. I know that none
of the d.mon commands will work in winGrass, but you can do everything from
the GUI anyway, so I am not sure anyone really needs to re-do all of the old
X11 stuff to get the (IMHO) out-dated d.mon commands to work in Windows...
It certainly does not seem to be a cost effective thing to do in terms of
coding time...
    If you are trying to create GRASS scripts that have their own displays,
it will pay to move beyond BASH/*NIX style scripting with X11 monitors for
the displays, and move on to scripting languages like (WX) Python that have
better ways to display things.

Cheers,

Isaac


-- 

Isaac I Ullah, M.A.

Archaeology PhD Student,
ASU School of Evolution and Social Change

Research Assistant,
Mediterranean Landscape Dynamics Project
***************************************************
isaac.ullah at asu.edu
ullah at archaeologist.com

http://www.public.asu.edu/~iullah
***************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-windows/attachments/20080307/34d5b3c1/attachment.html