[GRASS-dev] [GRASS GIS] #1719: GRASS 7 Monitor command line support

[GRASS GIS]

#1719: GRASS 7 Monitor command line support
-------------------------+--------------------------------------------------
 Reporter:  annalisapg   |       Owner:  grass-dev@…              
     Type:  enhancement  |      Status:  new                      
 Priority:  normal       |   Milestone:  7.0.0                    
Component:  wxGUI        |     Version:  svn-trunk                
 Keywords:  d.mon        |    Platform:  Unspecified              
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------

Comment(by glynn):

 Replying to [comment:11 wenzeslaus]:
 > So let's start brainstorming about rendering.
 >
 > Currently used options:
 >  * wxGUI renders to uncompressed PPM and uses g.pnmcomp
 >   * Glynn suggested that composition should be done by wxGUI
 ([http://lists.osgeo.org/pipermail/grass-dev/2012-August/059188.html
 link])
 >   * can PIL be used? (currently only Cartographic Composer preview
 depends on it)

 Note that the cairo driver can render to an X Pixmap. These can then be
 composited via g.cairocomp. Rendering and compositing may be hardware-
 accelerated, and the resulting raster data will never leave video memory.

 However:
  1. Requires X. I don't think that there's any equivalent on Windows. It
 relies upon the fact that an X client can create resources (e.g. Pixmaps)
 on the server which are retained after the program terminates.
  2. Requires that cairo was built with XRender support (although that's
 almost certain on X; cairo was created largely to facilitate the use of
 XRender).
  3. Can wxWidgets use an X Pixmap directly (i.e. without copying the
 contents to client memory and back again)?
  4. Leaving "stale" images in the X server's memory is even worse than
 leaving stale PPM files in the temp directory. Even keeping all of the
 "live" images in the X server's memory may be an issue on some systems.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1719#comment:12>
GRASS GIS <http://grass.osgeo.org>