Table of Contents

Fernando Bagnara Mussio


**PROPOSTA DE TRABALHO/MONOGRAFIA**

Para Eduardo e Fernando - Miguel -> 4/4

Para Miguel - Fernando -> 6/4

Para Eduardo e Fernando - Miguel -> 9/4

Para Eduardo e Fernando - Miguel -> 12/4

Relatório parcial, 23/4 (relat_libjava1.pdf)

Laboratórios

Laboratório 1 (fernandobm_lab1.pdf)

Laboratório 2 (fernandobm_lab2.pdf)

Laboratório 3 (fernandobm_lab3.pdf)

DISCUSSÃO DA PROPOSTA

Mesma que a de Eduardo Laino (ver wiki eduardo)

Trabalho Final

Resumo em Inglês:

This report presents a brief explanation of how to use TerraLib framework, a powerful platform for GIS development, with the Java programming language. TerraLib code is written in pure C++. The Java programming language has been widely adopted for its portability and user friendliness. In order to use TerraLib with other languagens than C++ a binding to the specific language is necessary. A language binding is a common strategy to allow C/C++ code to be used from another language. It improves software reuse as it avoids the need for reimplementing the library in several languages. Sometimes it also provides more efficiency due to the impossibility of implementing certain algorithms (efficiently) in high-level languages like Java. The TerraLib platform provides bindings for several higher-level languages including Java. In this report is explained how to add native TerraLib C++ code to a Java program by using an interface for hybrid implementation called Java Native Interface, or JNI. Java classes were implemented in order to allow Java users to develop GIS applications in a similar way C++ users should done using TerraLib framework. For the Java classes which add native TerraLib code it shall be indicated the use of the corresponding dynamic library containing the native code.

Artigo em pdf (api_java_para_terralib5.pdf)