[GRASS-dev] [GRASS GIS] #1719: GRASS 7 Monitor command line support
GRASS GIS
trac at osgeo.org
Fri Mar 28 14:50:11 PDT 2014
#1719: GRASS 7 Monitor command line support
--------------------------+-------------------------------------------------
Reporter: annalisapg | Owner: grass-dev@…
Type: enhancement | Status: reopened
Priority: normal | Milestone: 7.0.0
Component: wxGUI | Version: svn-trunk
Resolution: | Keywords: d.mon, display, d.* commands, rendering
Platform: Unspecified | Cpu: Unspecified
--------------------------+-------------------------------------------------
Comment(by glynn):
Replying to [comment:30 wenzeslaus]:
> It would be great if you would elaborate more on this idea now or in the
future. (I'm not sure if I can extend it and consider all the issues.) For
example, how switching between different `wx*` monitors and other
applications (ximgview, g.gui) would be solved?
By changing the GRASS_RENDER_COMMAND variable, or by changing settings
which are used by that program. If we want to provide the equivalent of
"d.mon", any variables should probably be GRASS variables so that they can
be changed by a module (environment variables can only be changed via the
parent shell).
> > The main reason for delegating to an external command is that it
avoids enforcing a specific communication protocol, or embedding the
details into lib/display, which would be an issue for high-level protocols
such as Windows' DDE or Python's pickle format.
>
> But still, wouldn't be Windows' DDE or Python's pickle even more fragile
(in any sense) than the current file-based approach?
I don't think so. Using files for inter-program communication is a bit of
a hack (e.g. there's no way to tell if the "reader" has died).
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1719#comment:31>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list