[GRASS-dev] WxPython front-end to ps.map

[Moritz Lennert]

On 08/02/07 10:11, Jáchym Čepický wrote:
> hi,
> 
> 2007/2/8, Hamish <hamish_nospam at yahoo.com>:
>> Hamish:
>> > > ps.map now has an optional 'border' instruction to control the
>> > > existence, color, and width of the box around the map area.
>>
>> Paul:
>> > That's great! Will be a godsend to someone somewhere I'm sure.
>>
>> The next step is to write a wxPython GUI cartographic composer frontend
>> which will create a ps.map instructions file and run that to create a
>> PostScript file. ps.map can make very professional hardcopy maps, but it
>> needs a user friendly front-end.
>>
>> see
>>   http://grass.gdf-hannover.de/wiki/GRASS_GUI#Components
>>
>> There was a TclTk start for this in d.m, gui/tcltk/d.m/print.tcl.
>>
>> This is not meant replace a Print button for the current display
>> monitor, it's a stand alone hardcopy plot generator. That print button
>> could write to a ps.map file, but maybe it is very easy to write
>> directly to PostScript from the map canvas, like Michael has done for
>> gis.m?

Yes, but currently what is written from the map canvas is the rasterized 
PNG image, not the original vector information, which makes working on 
the resulting ps file in a vector graphics program impossible...

> 
> As soon as new map display class will be defined in wxPython, I would
> like to build georectifing, ps.map and digitizing tool on top of it.
> 

Is there any possibility of changing the display system so that vector 
data is displayed as such in the display or at least the content of the 
display could be directly exported to ps or pdf as vector ?

Just naive questions, but this might determine whether it is better to 
concentrate on a ps.map frontend or on direct vector export of the display.

Moritz