Download - All IT eBooks

Transcript
Creating QGIS Plugins with PyQGIS and Problem Solving
PyQGIS cookbook
The main resource is a community content-driven cookbook that gives a general
introduction to scripting QGIS. You can find this documentation at http://www.
qgis.org/en/docs/index.html.
You have to choose the QGIS target version of your plugin and then choose the
PyQGIS Developer Cookbook link. If you are interested in the latest QGIS APIs,
you have to choose the testing version or directly go to http://docs.qgis.org/
testing/en/docs/pyqgis_developer_cookbook/.
If you need a copy on your system, you can also download a PDF version of the
cookbook from http://docs.qgis.org/<qgis version or testing>/pdf/.
For example, if you need the documentation for the version 2.2, you have to direct
your browser to http://docs.qgis.org/2.2/pdf/.
However, if you need documentation of a version under development, you can visit
http://docs.qgis.org/testing/pdf/.
Once you open the PDF documentation page, you can choose your
preferred translation.
QGIS even versions (for example, 2.2, 2.4, 2.6, and so
on) are always stable versions. Odd versions are always
developing versions (for example, 2.3 or 2.5). Odd versions
are generally known as testing versions.
API documentation
APIs are the doors that use the components of a software program. As a program
evolves, the APIs can change affecting, in our case, all the plugins that directly
use them.
The biggest QGIS API changes append jumping from version 1.8 to 2.0, but
moving from one version to another, there are new APIs added and others are
deprecated because of the normal development life cycle of a complex software.
Generally, deprecation and new APIs are added to satisfy new features (for example,
multithreading visualization added in version 2.4 or the newer legend engine added
in version 2.6) or due to code refactoring (refer to http://en.wikipedia.org/wiki/
Code_refactoring).
[ 302 ]