Changes between Version 2 and Version 3 of GSoC_SVG_Symbols_SECOND_DRAFT_OF_THE_MS_RFC

Timestamp:

Aug 10, 2009, 10:47:16 AM (15 years ago)

Author:

kiranvarma

Comment:

--

GSoC_SVG_Symbols_SECOND_DRAFT_OF_THE_MS_RFC

@@ -11 +11 @@
 
 The SVG parsing and rendering will be triggered by the following syntax:
+
+{{{
 SYMBOL
 TYPE SVG
 SVGPATH / p a t h / t o / f i l e . svg
 END
+}}}
+
 The choice for using a SYMBOL for the task is to allow for the reuse of the SVG symbol easily within classes.
 
@@ -38 +42 @@
 1. Implement an SVG parser. For this, we directly make use of the SVG Viewer example provided along with the AGG
 sources.
+
 2. Modify the MapServer lexical analyzer and parser to recognize the new keywords (SVG and SVGPATH).
+
 3. Modify the symbolObj structure to store information about the SVG symbol requested (eg. File path).
+
 4. Write a single function to render a parsed SVG file to a pixmap. The pixmap will be an intermediate form that can then
 be rendered. The pixmap will be stored in cache memory to prevent having to constantly be rasterized it every time a
 symbol is drawn.
+
 5. Create a createBrushFromSVG() function that creates a GD image pixmap. Also modify the basic rendering functions
 to support the new symbol type by using the createBrushFromSVG function.
+
 6. Render the pixmap into the final image file. This will be done using a mixture of the AGG and GD libraries.
 
@@ -52 +61 @@
 4.1 AGG/SVG Parser.
 The SVG parsing and pixmap generation functions will be stored in source files stored at
+
+{{{
 / maps e rve r / r e n d e r e r s / agg / svg /
+}}}
+
 The files within the above directory include the files for:
 a. SVG Parsing