Changes between Version 53 and Version 54 of wxGUIDevelopment/GUIForPs.map


Ignore:
Timestamp:
Sep 16, 2011, 8:15:55 AM (13 years ago)
Author:
annakrat
Comment:

update and add new features to be implemented

Legend:

Unmodified
Added
Removed
Modified

  • wxGUIDevelopment/GUIForPs.map

    v53 v54  
    1616WxGUI Cartographic Composer (formerly called Hardcopy Map Output Utility) is available in '''GRASS 6.4.2+'''.
    1717
    18 === Prototype 1 ===
     18=== Prototype 1 (ready) ===
    1919
    2020 * Configuration dialog (paper format, map scale)
    … …  
    2828 * Generate ps.map configuration text file
    2929 * Read configuration files
     30
    3031==== Known Issues ====
     32 * map scale for ll projections (map window)
    3133
    32  * run ps.map in thread (error)
    33  * mapinfo (position, color)
    34  * add 'Apply' to dialogs, track open dialogs
    35  * map scale for ll projections (map window)
    36  * icons: page setup, mapinfo
    37 === Prototype 2 ===
    38 
    39  * Implement other instructions (vlegend, barscale, ...)
    40  * If the `ps2pdf` program is installed offer a PDF output option
     34=== To be implemented ===
     35 * Implement other instructions (`grid`, `geogrid`, `eps`, `rectangle`, `line`, `point`, `rgb`, `region`, ...)
     36 * Add north arrow (`eps` instruction)
     37 * wxGUI integration (load maps from current map display - problem is that ps.map supports only 1 raster map)
     38 * GUI preferences
    4139 * If `pstoimg` program is installed offer a PNG output option (latex2html linux package; uses ghostscript. Imagemagick's `convert` does not do as nice a job AFAICT. Alt to try: Inkscape can do non-interactive conversions from the commandline.)
    4240 * Snap to grid
    43 === Prototype 3 ===
    44 
    45  * wxGUI integration
    46  * GUI preferences
     41 * Alignment of map elements (expected problem: inaccurate size of map elements)
     42 * latex support (`ps2eps`, it would add more possibilities for text customizing and solve the encoding problem)
    4743 * As a parallel task, nice features from ps.output should be ported to ps.map. (contact HB)
    4844
    … …  
    5349== Ps.map bugs and inconsistencies ==
    5450
     51 * ps.map file must be in Latin 1 encoding (missing certain accented characters - #1349)
     52 * mapinfo position (it aligns to the left side of map frame - #1333) and color (background color is not visible outside the map frame)
    5553 * color should support RGB for all instructions (e.g. #192)
    5654 * common usage of ref points and units (absolute, relative)