Changes between Version 20 and Version 21 of GSoC/2015

Timestamp:

03/09/15 12:36:14 (10 years ago)

Author:

wenzeslaus

Comment:

--

GSoC/2015

@@ -99 +99 @@
 === Complete basic cartography suite in GRASS GIS wxGUI Map Display ===
 
- * With few additions the wxGUI Map Display could cover large number of cartography needs so that users wouldn't be forced to switch to [http://grasswiki.osgeo.org/wiki/WxGUI_Cartographic_Composer WxGUI Cartographic Composer] or different software (Inkscape, QGIS) to create fully-featured map usable, e.g. for scientific publications. The development can happen in phases so that the easy-to-implement things, which gives greatest gain, are done first.
+ * With few additions the wxGUI Map Display could cover large number of cartography needs so that users wouldn't be forced to switch to [http://grasswiki.osgeo.org/wiki/WxGUI_Cartographic_Composer WxGUI Cartographic Composer] or different software (Inkscape, QGIS) to create fully-featured map usable, e.g. for scientific publications. The development can happen in phases so that the easy-to-implement things, which gives greatest gain, are done first in case it is not possible to implement everything during summer.
  * first phase:
   * store legend, scale bar, north arrow and text (and others if added) in workspace (#2369)
   * add units to legend (optionally also title) as parameter
   * possibility to add any image (as in animation tool), use cases: logo/watermark, workaround for overview maps
-  * disable rendering when loading workspace
-  * determine map window size without the need to change map display size manually
+  * disable rendering when adding multiple layers into layer manager using ''Add multiple...'' (disabled rendering when loading workspace already implemeted in r63319)
+  * determine map window size without the need to change map display size manually when loading workspace (currently there is a bug, when loading workspace, map display has correct size but map window is smaller and one must resize the window to get the right size of map window)
  * second phase:
   * support map units in scale bar, not only meters
   * allow user to set the length of scale bar (in map units)
-  * manual breaks for legend
-  * legend background
+  * manual breaks/ticks for legend (it is possible to set number of breaks/ticks but the values are not rounded), additional feature would be an option for automatic breaks/ticks every ten, hundred, ...
+  * legend background (currently the legend has transparent background), additional features include rounded corners, border and opacity settings
   * general shapes
    * can be implemented using `d.*` commands (e.g. `d.graph`) or wxPython or both (wxPython might be easier for interactivity, `d.*` commands for scripting)
-   * use cases: workaround missing backgroud of legend or text, manual marking special points 
+   * use cases: workaround missing backgroud of legend or text, manual marking of special points
   * include map-display-like object
+   * useful for overview maps (insets) or histograms
    * would be represented as image but the image would be dynamically generated
-   * useful for overview maps (insets) or histograms
+   * controlled using someting like nested map display
    * might be implemented as a standard Map Display whose saved image would be inserted as an image, perhaps image from other Map Display can be used
    * the important feature is the user does not have to create an intermediate file
+   * Simple Layer Manager classes can be used to manage layers in the additional/nested map display
  * third phase:
   * implement vector legend:
@@ -129 +131 @@
    * this can be also implemented as a script generator (rather than workspace renderer)
    * it should work as a simple automatic map ("atlas") generator and should accept also time series as the input
+  * general system and (GUI) manager for additional object on map display
+   * should support multiple legends and scale bars
+   * should include general shapes
+   * should work with any `d.*` commands, e.g. `d.histogram`
  * It would be great to make as much things as possible to work also in 3D Views (wxNVIZ).
- * Thorough (manual) testing on different platforms is needed (by student or mentors).
+ * Thorough (manual) testing on different platforms and version of wxPython is needed (by student or mentors).
  * See also:
   * [wiki:GSoC/2014#GRASSGISMapdisplaydecorationsenhancements map decorations idea from last year]
@@ -139 +145 @@
   * [wiki:GSoC/2014#ColortablemanagementGRASSGISwxGUI slightly related color tables idea from last year]
   * #2080 (changing properties of barscale or legend)
- * Language requirements: Python, wxPython, (perhaps a little bit of C and OpenGL)
+ * Language requirements: Python, wxPython, (C and OpenGL will be needed for some parts)
  * Co-mentors: Anna Petrasova, Helena Mitasova, Martin Landa