There is a chance; do you have a good suggestion? I choose "Map" in response to a discussion with Michael with respect it being hard to start with the library when people simply want to draw a map.
Jody On 08/06/2010, at 2:37 PM, Ben Caradoc-Davies wrote: > +1. Changes look sensible. > > One suggestion: any chance of calling the "Map" class something else? It will > cause confusion both in code and in discussion. > > Kind regards, > Ben. > > > On 08/06/10 08:15, Jody Garnett wrote: >> Proposal is established enough to be voted on; I will be working on this >> over several evenings this week with this weekend targeted for the first >> commit. >> - http://docs.codehaus.org/display/GEOTOOLS/MapContext+Refactor >> - http://jira.codehaus.org/browse/GEOT-3136 (Initial patch showing the api; >> used to produce diagrams above) >> >> Summary: >> >> MapContext and MapLayer have really grown over time - and in some cases have >> diverged from their actual use. >> >> Summary: >> • MapContext use replaced by the class Map (for stability and so we >> don't have two java files) >> • MapContext itself will gain a toMap() method which can be used by the >> renderer to handle code during the transition >> • Map uses layers() method to provide direct access to the layer list; >> removing 50% of the methods from MapContext >> • Map has improved "viewport" methods (MapContext viewport model >> methods are not currently used in the codebase - in part because they are so >> confusing) >> • MapLayer replaced by Layer class >> • Specific Layer subclasses for different kinds of content; this is an >> open ended set allowing additional kinds of layers to be added over time for >> TileServers, Google Maps and so forth >> • DefaultMapLayer re-factored to use an internal Layer delegate (so >> existing code will not be broken; and importantly will not be duplicated) >> • DefaultMapLayer toLayer() method used by the renderer during the >> transition >> >> This proposal does not break any existing API; it provides a safe migration >> path forward (and like the Query proposal) makes use of classes directly for >> a simplified experience. >> ------------------------------------------------------------------------------ >> ThinkGeek and WIRED's GeekDad team up for the Ultimate >> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >> lucky parental unit. See the prize list and enter to win: >> http://p.sf.net/sfu/thinkgeek-promo >> _______________________________________________ >> Geotools-devel mailing list >> Geotools-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geotools-devel >> > > > -- > Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> > Software Engineering Team Leader > CSIRO Earth Science and Resource Engineering > Australian Resources Research Centre ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
