There is also a "glass pane" which allows you to work directly with SWT (specially used for animation feedbacks for tracking; but I imagine you could do full screen animations if needed).
I do not think there is much difference between the glass pane and a draw command from a performance point of view. I found a documentation page on the geotools utility class I mentioned in a previous post: - http://docs.geotools.org/latest/userguide/library/main/shape.html -- Jody Garnett On Tuesday, 6 September 2011 at 10:56 PM, Jesse Eichar wrote: > A draw command can be a full rendering if that is what you wish. The draw > command solution is certainly the most difficult with regards to effort and > should probably be used as a last resort but if it is performance you need > then that is the solution. > > Another thing to consider is the animation class. They are essentially > DrawCommands but provides support for stepping through frames and some > primitive timing that should become more sophisticated over time. > > Jesse > > On Tue, Sep 6, 2011 at 2:50 PM, Matthias Lendholt > <[email protected] (mailto:[email protected])> > wrote: > > Am 06.09.2011 12:58, schrieb Jesse Eichar: > > > > > Jody hit most of the most important points. One thing to remember is > > > that normal layers are slowest to render, mapgraphics are next (about > > > 1-2 refreshes per second) and DrawCommands are the fastest (12+ > > > refreshes per second). > > > > Ok, good to know! But I in this case I would have to perform DrawCommands > > for ~4000 Features and I'm not sure whether this would perform better than > > the layer rendering. Or? > > > > Until the user doesn't perform any map action (zoom, pan, ...) the > > MapGraphic would be the fastest solution. I'll think about implementing it. > > > > Matthias > > > > > > > > Jesse > > > > > > On Tue, Sep 6, 2011 at 12:30 PM, Matthias Lendholt > > > <[email protected] > > > (mailto:[email protected]) > > > <mailto:[email protected]>> wrote: > > > > > > Hi all > > > > > > > > > In our tsunami early warning system > > > (http://udig.refractions.net/__gallery/dews/ > > > <http://udig.refractions.net/gallery/dews/>) we are using wave > > > propagation models. See attached image: A shapefile is providing the > > > isochrones. A dynamically generated sld provides the color gradient > > > which is based on an attribute containing the arrival time. The > > > thick red isochrone is updated in real-time showing the current > > > position. Depending on our models the update interval is between > > > 12seconds and 2 minutes and rendering was not an issue. > > > > > > As a new feature we would like to provide play back / fast forward > > > functionality to visualize the wave propagation. This means the > > > highlighted iso chrone will move quite fast, and the map has to be > > > updated every second. I tried it with the existing code but the > > > rendering gets stalled. > > > > > > Currently on each update the sld is updated: > > > > > > layer.getStyleBlackboard().__put(SLDContent.ID, style); > > > layer.refresh(null); > > > > > > I'm not sure whether this is the best way to update the styling. > > > > > > The shapefile contains about 4300 Linestring features. Maybe this is > > > to heavy for animation-like map updates? > > > > > > Many thanks in advance for any hints or suggestions. > > > > > > Matthias > > > > > _______________________________________________ > > User-friendly Desktop Internet GIS (uDig) > > http://udig.refractions.net > > http://lists.refractions.net/mailman/listinfo/udig-devel > > _______________________________________________ > User-friendly Desktop Internet GIS (uDig) > http://udig.refractions.net > http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
