Annotation of /branches/WIP-pyshapelib-bramz/Extensions/svgexport/TODO

TODO file for Thuban svgexport Extension

For 1.0.2:

* Add raster file export.

  Spec REC-SVG11-20030114 includes no indication about embedding raster images.
  Thus we probably have to write extra files.
        
        Substeps:
                a) write shown raster file as .png, no matter which
                   filename.
                b) add filename construction based on used svg file.
                   Difficulty: There can be several raster layers.
                c) add <image> tag to .svg file

        Considerations:
                q1) What resolution to use for the PNG file? 

                    As high as possible to avoid losing information.
                    Will probably not be easy to decide if there are 
                    complicated projections.

                q2) Should be there one PNG file or is tiling better?

                    One PNG per tile that Thuban is using seems to be
                    a good approach.

                q3) Image processing is happening in UI/renderer.py with
                    the help of gdalwarp and and wx image function. 
                    Shall we use wx as well? This would make this extension
                    depend on wx and a GUI, but if we use something else like
                    PIL (python-imaging) the results might be significantly
                    different to what the user sees on screen. On the other 
                    hand, this will already depend on the screen resolution.
                    Or refactor renderer.py to use PIL as well? Probably not
                    because of speed reasons.

For 1.0.x, x>2:

* find out why the memory shapes in class Testobjectexport
  return points with negative values with projected_points

Better support for variable Point sizes:
* a real test for variable point sizes
* save point size in an svg attribute value
* Create a better legend for variable point symbols

* add a progress bar or something so that the user is informed 
  during exports of huge files. A simple interator return of 
  draw_shape_layer_incrementally() might not be enough, because the user
  might stop this operation when doing something.

For later:

* use styles for the geographic objects in one class in each layer
  after making sure that Skencil can do this, too.

* add a method to trigger the application down the pipe that new
  files have just been written. First idea: Add a "save as" variant
  which also asks for a command line to run after each "save".
  The command line can be used to run something like 
  "skencil-remote --updated-thubanmapsvgfile %s"

* Think about adding preferences or options , e.g.: ignore the line Width.
1	bernhard	2490	TODO file for Thuban svgexport Extension
2	bernhard	2481
3	bernhard	2726	For 1.0.2:
4	bernhard	2481
5	bernhard	2732	* Add raster file export.
6	bernhard	2490
7	bernhard	2732	Spec REC-SVG11-20030114 includes no indication about embedding raster images.
8			Thus we probably have to write extra files.
9
10			Substeps:
11			a) write shown raster file as .png, no matter which
12			filename.
13			b) add filename construction based on used svg file.
14			Difficulty: There can be several raster layers.
15			c) add <image> tag to .svg file
16
17			Considerations:
18			q1) What resolution to use for the PNG file?
19
20			As high as possible to avoid losing information.
21			Will probably not be easy to decide if there are
22			complicated projections.
23
24			q2) Should be there one PNG file or is tiling better?
25
26			One PNG per tile that Thuban is using seems to be
27			a good approach.
28
29			q3) Image processing is happening in UI/renderer.py with
30			the help of gdalwarp and and wx image function.
31			Shall we use wx as well? This would make this extension
32			depend on wx and a GUI, but if we use something else like
33			PIL (python-imaging) the results might be significantly
34			different to what the user sees on screen. On the other
35			hand, this will already depend on the screen resolution.
36			Or refactor renderer.py to use PIL as well? Probably not
37			because of speed reasons.
38
39	bernhard	2726	For 1.0.x, x>2:
40	bernhard	2490
41	bernhard	2482	* find out why the memory shapes in class Testobjectexport
42			return points with negative values with projected_points
43	bernhard	2481
44			Better support for variable Point sizes:
45			* a real test for variable point sizes
46			* save point size in an svg attribute value
47			* Create a better legend for variable point symbols
48
49			* add a progress bar or something so that the user is informed
50			during exports of huge files. A simple interator return of
51			draw_shape_layer_incrementally() might not be enough, because the user
52			might stop this operation when doing something.
53
54			For later:
55
56			* use styles for the geographic objects in one class in each layer
57			after making sure that Skencil can do this, too.
58
59	bernhard	2489	* add a method to trigger the application down the pipe that new
60			files have just been written. First idea: Add a "save as" variant
61			which also asks for a command line to run after each "save".
62			The command line can be used to run something like
63			"skencil-remote --updated-thubanmapsvgfile %s"
64	bernhard	2513
65			* Think about adding preferences or options , e.g.: ignore the line Width.
Name	Value
svn:eol-style	native
svn:keywords	Author Date Id Revision