[GRASS-dev] [GRASS GIS] #1719: GRASS 7 Monitor command line support
GRASS GIS
trac at osgeo.org
Mon Sep 10 08:31:04 PDT 2012
#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 cmbarton):
Replying to [comment:17 wenzeslaus]:
> Replying to [comment:16 glynn]:
> >
> > In theory, the fastest solution should be to use the cairo driver with
output to X Pixmaps. The d.* modules generate output in video memory, and
may be hardware accelerated. Compositing occurs entirely in video memory,
and may be hardware accelerated. The main unknowns are how hard wxWidgets
makes this, and whether something similar can be achieved on other
platforms.
>
> In wxWidgets there is wxBitmap ([http://wxpython.org/docs/api/wx.Bitmap-
class.html wxPython], [http://docs.wxwidgets.org/2.8/wx_wxbitmap.html
wxWidgets]).
> {{{
> This class encapsulates the concept of a platform-dependent bitmap,
either monochrome or colour or colour with alpha channel support.
> }}}
>
> This wxBitmap can be directly drawn on some wx widget/window. This
operation is fast.
>
> Can be wxBitmap used for what you are talking about? It is the same as X
Pixmap on linux?
>
> But how would be this bitmap/pixmap transfered from d.* module to wxGUI
application?
We already use wx.Bitmap
The PNM file generated by g.pnmcomp is read by wx.Image. A wx.Bitmap is
created from the wx.Image object and is rendered to the DC canvas. This
part is fast.
AFAICT, the slowest part of the process is the d.* rendering.
For any changes to the rendering, keep in mind that other modules use this
rendering engine to. So any fix needs to work in all modules that go from
d.* modules to screen.
Michael
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1719#comment:19>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list