Ticket #3824 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

Update the "Cartographic Symbol Construction with MapServer" document to version 6

Reported by: havatv Owned by: havatv
Priority: normal Milestone: 6.0 release
Component: Documentation - MapServer Version: 6.0
Severity: normal Keywords: symbol construction, examples, style, mapfile
Cc: havatv, tbonfort, dmorissette

Description

The "Cartographic Symbol Construction with MapServer" document has to be updated to describe Mapserver version 6 functionality.

Change History

Changed 2 years ago by tbonfort

  • cc tbonfort added

Changed 2 years ago by dmorissette

  • cc dmorissette added

See also

  • #3798: CARTOLINE removed
  • #3793, GAP, PATTERN, LINECAP/JOIN and POSITION removed from symbolObj

Changed 2 years ago by dmorissette

Correction:

  • #3798: CARTOLINE removed
  • #3797, GAP, PATTERN, LINECAP/JOIN and POSITION removed from symbolObj

Changed 2 years ago by havatv

  • status changed from new to closed
  • resolution set to fixed

The first version of the revised document (with some new illustrations) has now been uploaded. I have changed the structure of the document a bit, and provided some other examples. There will be further work on this, but I close this ticket as fixed now.

Changed 2 years ago by tbonfort

Great work Havard, many thanks for having taken this task.

Changed 2 years ago by havatv

The document is very crude, and has not been properly proof read. I know that there are many errors and omissions. I felt that I had to commit something to get things out for the version 6 release.

I will have to fix a lot of things. It would be good to correct the worst mistakes as soon as possible. Is it possible to update the documentation that is on mapserver.org independent of releases (before 6.0.1)?

Changed 2 years ago by dmorissette

Yes, the live website version is taken from SVN branch-6-0, and fixes or 6.0-specific additions are welcome in that branch.

The SVN trunk version has now become 6.1-dev (future 6.2), so this means that all fixes to the 6.0 branch should also be applied to trunk to make sure they make it in 6.2.

Things should remain this way until the 6.2 release, i.e. there should be no more tagging or branching of the docs until the 6.2 release.

Note: See TracTickets for help on using tickets.