tag:blogger.com,1999:blog-8454280407750835604.post5664812028355655975..comments2010-08-31T13:36:21.240-07:00Dan Shoutisnoreply@blogger.comBlogger5125tag:blogger.com,1999:blog-8454280407750835604.post-4416358653001428102008-09-17T09:08:00.000-07:002008-09-17T09:08:00.000-07:00Guys,<BR/><BR/>Dan is right about how creating a GP tool is a mess, given these numerous data types that seem to point to the same type. <BR/><BR/>However, if any of you are Java developers/managers, then there's some good news for you. ESRI will be releasing support for creating GP tools in Java shortly. This support will include Eclipse IDE wizards that will generate boiler plate code for you, based on what you tell the wizard to generate (what type of parameters, values, licensing, etc).<BR/><BR/>The data types still haven't changed in the first release of this Java support, but in future releases we are planning to ask more questions in "English" in the wizard and generate code so that users don't have to worry about the data type and "ability to work in a model" mess.<BR/><BR/>Thanks!<BR/>ADAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8454280407750835604.post-73586909464632778562008-09-17T06:34:00.000-07:002008-09-17T06:34:00.000-07:00Hi Dan -<BR/>A big drawback of maptopologies is that they are tied to arcmap's Topology Extension. If you come up with something equivalent to maptopology (without an arcmap dependency) it would be very useful. In addition to packaging for use in modelbuilder, consider making it available to arcengine.Kirkhttp://ambergis.wordpress.comnoreply@blogger.comtag:blogger.com,1999:blog-8454280407750835604.post-6121935706875353412008-09-16T19:28:00.000-07:002008-09-16T19:28:00.000-07:00Dan,<BR/><BR/>Great post, very amusing (if that's the right word for it). How about this illuminating entry in the developer help:<BR/><BR/>"FindBeginningRing Method: Returns the beginning ring of the ring group containing the specified following ring."<BR/><BR/>Well that's just clear as crystal.Steve Lhttp://www.flickr.com/photos/passenger57noreply@blogger.comtag:blogger.com,1999:blog-8454280407750835604.post-74106402858854560322008-09-16T08:46:00.000-07:002008-09-16T08:46:00.000-07:00Hi Kirk,<BR/><BR/>I didn't put two and two together at first and thought your link was to to a GIS or programming reference that might have some technical solution.... <BR/><BR/>A fantastic lecture; I should check out the book. Rather telling that the best response to ArcObjects issues is a healthy dose of life philosophy. ;)<BR/><BR/>I think you'll find Boundary Maker Redux interesting, once it's out. I'm barely touching ArcObjects except to build a GP tool wrapper. The rest is straight-up computational geometry, a rather different (but much more flexible) approach.Dan Shoutishttp://www.blogger.com/profile/12551374378737211543noreply@blogger.comtag:blogger.com,1999:blog-8454280407750835604.post-15838297028909749822008-09-16T07:34:00.000-07:002008-09-16T07:34:00.000-07:00Hi Dan -<BR/><BR/>For boundary manipulations, I find maptopologies to be useful. I&#39;m not familiar with ways of doing this with OOTB modelbuilder, so I think it would be great to see more custom gpTools being developed. Here&#39;s some quick &amp; dirty VBA code I wrote a while back for doing something similar: http://arcscripts.esri.com/details.asp?dbid=12863<BR/><BR/>When dealing with ArcObjects I find it helpful to remember Randy Pausch&#39;s comments about walls from his Last Lecture.<BR/>http://www.amazon.com/Last-Lecture-Randy-Pausch/dp/1401323251Kirkhttp://ambergis.wordpress.comnoreply@blogger.com