Let's use the java type system
Tries to improve the progress monitor.
Addresses #324. I try to manage my two sub-process as good as I can. The
progress bar will go twice from 0 to 100 while the number on the right
of the window will jump from 0 to 50 (end of the first task) to 100 (end
of the second task).
Change viewport dimensions and scroll increments.

Make the viewport view 6 rows. On one scroll click, go down one
row. On one mouse wheel turn, go down 3 rows.
Remove double imageChanged() calls.

This method is already called by setSymbol(Symbolizer) This could
be slowing down scrolling because we repaint twice.
Set the scroll mode. Seems to be a little faster.
Merge branch 'master' into enhancement/some-scroll-improvements
Merge pull request #383 from agouge/enhancement/some-scroll-improvements

Enhancement: some scroll improvements regarding #323
fix map manager serialisation
Merge pull request #382 from agueganno/improvement/progress-bar-legend

Improvement : progress bar in the simple legend editor
fix map editor and manager persistence
Merge pull request #391 from nicolas-f/fix/mapeditor-persistence

Fix/mapeditor persistence
fix toolbar hiding on updating toolbars
Fix for the WMS driver so that we retrieve a BoundingBox even if it is not explicitly given by the getCapabilities
Removes the dependency to the gvSIG WMS client.
Adds classes from openjump instead. I've cleant them a bit and included
them in our driver and in the UI parts used to add WMS sources.
Removed WMSLegend, as it was not used anymore.
Bounding box management must be improved.
We must be able to cover all the cases for all the WMS versions.
Starts to implement 1.3.0 support.
Not that easy : this version of WMS manages bounding boxes in a cleaner
way, I must adapt the code to that.
Migrating the wms client to a dedicated project.
Enables back the re-projection of bounding boxes.
We do that when we find a CRS that does not have an associated bounding
box.
Adds transparency and fix 1.3.0 management.
Adds transparency