ArcGIS Engine Developer Guide

More documents

Recommendations

Info

BUILDING APPLICATIONS WITH C++ AND CONTROL WIDGETS Each Motif ArcGIS control widget has a corresponding GTK ArcGIS control widget. A buddy control is a control that is designed to work in conjunction with another control. For example, the Table of Contents, or TOC, Control is a buddy of the MapControl. Although the GUI design will be different for GTK developers, the majority of the rest of the application code will be the same. Throughout the scenario, sidebars will highlight areas where GTK programmers will take different steps. The ArcGIS Engine C++ API provides reusable Motif widget components corresponding to each ArcGIS Engine control. This developer scenario will show how these components can be embedded in a Motif form to build a map viewer application. Motif itself is a specification for how graphical user interfaces should look and feel. The Open Software Foundation (OSF) Motif Toolkit, used with the ArcGIS Engine C++ API in this scenario, uses X as the window system and X Toolkit Intrinsics as the API platform. The Motif widgets discussed here are one part of the Motif toolkit. Each widget is a reusable and configurable component of the user interface. The Motif toolkit provides widgets for common tasks, such as the toggle button used in this scenario. Each built-in Motif widget knows how to draw itself as well as some generic behavior; for example, the toggle button knows to call a function when it is clicked. However, it is up to the programmer to implement the callback function, giving the widget its specific behavior. In addition to providing widgets the Motif toolkit does other work for the developer, including handling many user interactions, managing window layout, and redrawing. The Motif widget ArcGIS controls are custom widgets made available through the C++ API of the ArcGIS Engine Developer Kit. Placed in a top-level application widget, the controls have events, properties, and methods that the developer can access, and like the built-in Motif toolkit widgets, each ESRI control widget knows how to draw itself. The objects and functionality within each control can be combined with other ESRI ArcObjects as well as with custom controls to easily create customized end user applications. This scenario was written in C++ using the Motif toolkit from the Open Software Foundation. It was chosen to create an application that would run on a Solaris or Linux platform. The same application could also be written in Java. Whichever API you use, your future success with the ArcGIS controls depends on your skill in both the language and ArcObjects. DESIGN This scenario has been designed to highlight how the ArcGIS controls interact with each other and to expose a part of each ArcGIS control’s object model to the developer. The scenario starts with building a GUI using Motif to place and manage the controls. The controls are then connected to each other through the SetBuddy methods. At this stage, the application is ready to function as a simple map viewer. The GUI functionality is then extended through a custom tool and event handling. To achieve this, the scenario further explores the API of the visual Motif widgets, as well as the other nonvisual ArcGIS Engine components. REQUIREMENTS To successfully follow this scenario you need the following (the requirements for deployment are covered later in the ‘Deployment’ section): • An installation of the ESRI ArcGIS Engine Developer Kit with an authorization file enabling it for development use. 358 • ArcGIS Engine Developer Guide
BUILDING APPLICATIONS WITH C++ AND CONTROL WIDGETS The ArcGIS developer samples are not included in the typical installation of the ArcGIS Engine Developer Kit. If you do not have them installed, rerun the Developer Kit Install wizard, click Custom or Modify, and click the samples feature under Software Developer Kit. The GTK implementation can be found in the same directory in Building_an_ArcGIS_controls_Map_Viewer_ ApplicationGTK_cpp.zip. In GTK C++ you would include ArcSDK.h and Ao/AoGTKControls.h. You would use libarcsdk.so, libgtkctl.so, and libaoctl.so. GTK developers will also need to link against some GTK libraries and include some GTK-specific directories. It is recommended that pkg-config be used for this. These steps are shown in the provided Makefile.SolarisGTK.Template and Makefile.LinuxGTK.Template. • Your favorite text editor. • A supported C++ compiler. o Solaris: Sun WorkShop (Forte) 6 update 2 o Linux: GCC version 3.2 • A configured C++ environment (for example, your compiler configured and your path set). To test this, see ‘Pre-ArcObjects C++ configuration steps’ in Chapter 4, ‘Development environments’. • A configured ArcObjects environment. To get your machine ready for ArcObjects development, you must source the file / init_engine.sh (or .csh, depending on your shell of choice). If you prefer, that can be done in your shell’s RC file. Otherwise, you must source that file for each shell. • Familiarity with your operating system and a basic foundation in both C++ and Motif programming. Although this scenario uses the Motif toolkit, it is not intended to teach the basics of Motif programming. For Motif-specific details, see the Motif Programming Manual resource listed at the end of this example. • While no experience with other ESRI software is required, previous experience with ArcObjects and a basic understanding of ArcGIS applications, such as ArcMap and ArcCatalog, are advantageous. • Access to the sample data, code, and makefiles that come with this scenario. Code and makefiles are located at /developerkit/ Building_an_ArcGIS_Controls_Map_Viewer_ApplicationMotif_Cpp.zip. The sample data is located at /developerkit/samples/data/ arcgis_engine_developer_guide. The controls and ArcGIS libraries used in this scenario are as follows: • MapControl • PageLayoutControl • TOCControl • ToolbarControl • Carto Object Library • System Object Library • Display Object Library • SystemUI Object Library • Geometry Object Library In Motif C++, you must include the following files to use those controls and object libraries: • ArcSDK.h • Ao/AoMotifControls.h Chapter 6 • Developer scenarios • 359
Page 1 and 2:
ArcGIS ® Engine Developer Guide Ar
Page 3 and 4:
Contents CHAPTER 1: INTRODUCING ARC
Page 5 and 6:
1 Introducing ArcGIS Engine ESRI ®
Page 7 and 8:
ARCGIS 9 OVERVIEW ArcGIS Server Arc
Page 9 and 10:
ARCGIS 9 OVERVIEW ArcGIS Engine and
Page 11 and 12:
OVERVIEW OF ARCGIS ENGINE Chapter 3
Page 13 and 14:
OVERVIEW OF A RCGIS ENGINE The Stre
Page 15 and 16:
WHO CAN USE ARCGIS ENGINE? authored
Page 17 and 18:
ARCGIS ENGINE CAPABILITIES SPATIAL
Page 19 and 20:
ARCGIS ENGINE CAPABILITIES NETWORK
Page 21 and 22:
GETTING STARTED Throughout most of
Page 23 and 24:
USING THIS BOOK This book, ArcGIS E
Page 25:
DEVELOPER RESOURCES ESRI DEVELOPER
Page 28 and 29:
ARCGIS SOFTWARE ARCHITECTURE For a
Page 30 and 31:
ARCGIS SOFTWARE ARCHITECTURE ESRI h
Page 32 and 33:
ARCGIS SOFTWARE ARCHITECTURE Althou
Page 34 and 35:
ARCGIS APPLICATION PROGRAMMING INTE
Page 36 and 37:
ARCGIS ENGINE LIBRARIES Carto Conta
Page 38 and 39:
ARCGIS ENGINE LIBRARIES cluded in t
Page 40 and 41:
ARCGIS ENGINE LIBRARIES 22 Spatial-
Page 42 and 43:
ARCGIS ENGINE LIBRARIES NETWORKANAL
Page 45 and 46:
3 Developing with ArcGIS controls A
Page 47 and 48:
WORKING WITH THE ARCGIS CONTROLS me
Page 49 and 50:
WORKING WITH THE ARCGIS CONTROLS Ar
Page 51 and 52:
WORKING WITH THE ARCGIS CONTROLS If
Page 53 and 54:
WORKING WITH THE ARCGIS CONTROLS Li
Page 55 and 56:
BUILDING APPLICATIONS WITH THE ARCG
Page 57 and 58:
Page 59:
Page 62 and 63:
THE MICROSOFT COMPONENT OBJECT MODE
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
DEVELOPING WITH ARCOBJECTS ArcGIS a
Page 76 and 77:
DEVELOPING WITH A RCOBJECTS Accessi
Page 78 and 79:
DEVELOPING WITH A RCOBJECTS As an e
Page 80 and 81:
DEVELOPING WITH A RCOBJECTS COM App
Page 82 and 83:
DEVELOPING WITH A RCOBJECTS The Cus
Page 84 and 85:
THE V ISUAL BASIC 6 ENVIRONMENT Use
Page 86 and 87:
THE V ISUAL BASIC 6 ENVIRONMENT Whi
Page 88 and 89:
THE V ISUAL BASIC 6 ENVIRONMENT Pri
Page 90 and 91:
THE V ISUAL BASIC 6 ENVIRONMENT Tha
Page 92 and 93:
THE V ISUAL BASIC 6 ENVIRONMENT per
Page 94 and 95:
THE V ISUAL BASIC 6 ENVIRONMENT If
Page 96 and 97:
THE V ISUAL BASIC 6 DEVELOPMENT ENV
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
VISUAL C++ IXxxImpl CComXxxThreadMo
Page 106 and 107:
VISUAL C++ Linking ATL code One of
Page 108 and 109:
VISUAL C++ removal would result in
Page 110 and 111:
VISUAL C++ switches are used to cha
Page 112 and 113:
VISUAL C++ 4. To create the noncrea
Page 114 and 115:
VISUAL C++ Grimes, Richard, Reilly
Page 116 and 117:
VISUAL C++ IFooPtr ipFoo; HRESULT h
Page 118 and 119:
VISUAL C++ expected. It is better t
Page 120 and 121:
VISUAL C++ Here are some suggestion
Page 122 and 123:
VISUAL C++ Symbol d, i Format signe
Page 124 and 125:
VISUAL C++ Loading the following sh
Page 126 and 127:
VISUAL C++ #import "C:\Program File
Page 128 and 129:
VISUAL C++ Make sure dialog boxes t
Page 130 and 131:
VISUAL C++ Creating an MFC dialog b
Page 132 and 133:
VISUAL C++ This environment does no
Page 134 and 135:
VISUAL C++ Connection point mechani
Page 136 and 137:
VISUAL C++ The following issues wit
Page 138 and 139:
VISUAL C++ { } DECLARE_REGISTRY_RES
Page 140 and 141:
VISUAL C++ 5. Clicking OK will modi
Page 142 and 143:
VISUAL C++ delete[] pvars; // Clean
Page 144 and 145:
VISUAL C++ // Create dialog class o
Page 146 and 147:
.NET APPLICATION PROGRAMMING INTERF
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
JAVA APPLICATION PROGRAMMING INTERF
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
C++ APPLICATION PROGRAMMING INTERFA
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 257 and 258:
5 Licensing and deployment Developm
Page 259 and 260:
ARCGIS LICENSING OPTIONS PRODUCT LI
Page 261 and 262:
ARCGIS LICENSING OPTIONS ArcGIS Eng
Page 263 and 264:
ARCGIS ENGINE DEVELOPER KIT At the
Page 265 and 266:
APPLICATION DEVELOPMENT AND LICENSE
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
TESTING WITH ARCGIS ENGINE RUNTIME
Page 281 and 282:
DEPLOYMENT To successfully deploy c
Page 283 and 284:
DEPLOYMENT 3. You or your client in
Page 285 and 286:
6 Developer scenarios Throughout th
Page 287 and 288:
BUILDING APPLICATIONS WITH ACTIVEX
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
BUILDING APPLICATIONS WITH VISUAL J
Page 311 and 312: BUILDING APPLICATIONS WITH VISUAL J
Page 335 and 336: BUILDING APPLICATIONS WITH WINDOWS
Page 361: BUILDING APPLICATIONS WITH C++ AND
Page 365 and 366: BUILDING APPLICATIONS WITH C++ AND
Page 413 and 414:
BUILDING A COMMAND-LINE JAVA APPLIC
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
BUILDING A COMMAND-LINE C++ APPLICA
Page 433 and 434:
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
A Reading the object model diagrams
Page 447 and 448:
CLASSES AND RELATIONSHIPS There are
Page 449 and 450:
CLASSES AND RELATIONSHIPS N-ary ass
Page 451 and 452:
INTERFACES AND MEMBERS error messag
Page 453:
PUTTING IT TOGETHER—AN EXAMPLE IW
Page 456 and 457:
ARCGIS SOFTWARE DEVELOPER KIT The A
Page 458 and 459:
ARCGIS SOFTWARE DEVELOPER KIT • E
Page 461 and 462:
C Conver erting personal geodatabas
Page 463 and 464:
CONVERTING DATA FOR USE WITH THE GI
Page 465 and 466:
CONVERTING DATA FOR USE WITH THE GI
Page 467 and 468:
D Installing ArcGIS Engine Runtime
Page 469 and 470:
INSTALLING ARCGIS ENGINE RUNTIME ON
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
Page 495 and 496:
E Glossary The following is a gloss
Page 497 and 498:
GLOSSARY ASP.NET assembly associati
Page 499 and 500:
GLOSSARY composition computer-aided
Page 501 and 502:
GLOSSARY FGDC framework GDB GDI Geo
Page 503 and 504:
GLOSSARY JSF JSP JSTL late binding
Page 505 and 506:
GLOSSARY the EXE in which they are
Page 507 and 508:
GLOSSARY server account server cont
Page 509 and 510:
GLOSSARY URL usage time utility COM
Page 511 and 512:
A Index Abstract class 61 defined 4
Page 513 and 514:
Building applications with ActiveX
Page 515 and 516:
debugging defined 495 Deeply statef
Page 517 and 518:
IIS 143 ILineSymbol interface 292,
Page 519 and 520:
OLE automation. See Microsoft Compo
Page 521 and 522:
SXD defined 504 Synchronization def
Page 523:
XSLT defined 506 Index • 519
show all

ArcGIS Engine Developer Guide

Create successful ePaper yourself

Delete template?

Save as template?