It was a choice between using a wrapper so that existing implementations could remain untouched, or modify every existing resource handle to process the extension point.
Both ways have their benefits. Its unfortunate we didn't take the same direction, this makes the gap between the geotools catalog and udig catalog even larger. -Justin Jody Garnett wrote: > Well I sent this to the wrong list; but some of the stuff on > IGeoResource is of interest; although it sounds like > Justin took a different track in terms of using wrappers. >> Started page the programmers guide reference section ... >> - >> http://udig.refractions.net/confluence/display/DEV/Upgrade+from+1.0+to+1.1 >> >> >> Assume this can be updated as backwards incompatibilities are pointed >> out. If you know >> of any I missed please update the page :-) >> >> Jody >> > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > > !DSPAM:1004,45661e3c146636309890654! > -- Justin Deoliveira [EMAIL PROTECTED] The Open Planning Project http://topp.openplans.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
