Welcome to your automatically generated plugin!
-------------------------------------------------------------

This is just a starting point. You now need to modify the code to make it do
something useful....read on for a more information to get yourself started.

Documentation:
-------------------------------------------------------------

You really need to read the QGIS API Documentation now at:

http://qgis.org/api/

In particular look at the following classes:

QGisInterface : http://qgis.org/api/classQgisInterface.html
QgsMapCanvas  : http://qgis.org/api/classQgsMapCanvas.html
QgsMapTool    : http://qgis.org/api/classQgsMapTool.html
QgisPlugin    : http://qgis.org/api/classQgisPlugin.html

QGisInterface is an abstract base class (ABC) that specifies what publicly
available features of QGIS are exposed to third party code and plugins. An
instance of the QgisInterface is passed to the plugin when it loads. Please
consult the QGIS development team if there is functionality required in the
QGisInterface that is not available.

QgsPlugin is an ABC that defines required behaviour your plugin must provide.
See below for more details.

What are all the files in my generated plugin directory for?
-------------------------------------------------------------

CMakeLists.txt
This is the generated CMake file that builds the plugin. You should add you
application specific dependencies and source files to this file.

[pluginlcasename].h
[pluginlcasename].cpp  
This is the class that provides the 'glue' between your custom application
logic and the QGIS application. You will see that a number of methods are
already implemented for you - including some examples of how to add a raster or
vector layer to the main application map canvas. This class is a concrete
implementation of QgisPlugin (which defines required behaviour for a plugin).
In particular, a plugin has a number of static methods and members so that the
QgsPluginManager and plugin loader logic can identify each plugin, create an
appropriate menu entry for it etc. Note there is nothing stopping you creating
multiple toolbar icons and menu entries for a single plugin. By default though
a single menu entry and toolbar button is created and its pre-configured to
call the run() method in this class when selected. This default implementation
provided for you by the plugin builder is well documented, so please refer to
the code for further advice.

[pluginlcasename]gui.ui  
This is a Qt designer 'ui' file. It defines the look of the default plugin
dialog without implementing any application logic. You can modify this form to
suite your needs or completely remove it if your plugin does not need to
display a user form (e.g. for custom MapTools).


[pluginlcasename]gui.cpp  
[pluginlcasename]gui.h  
This is the concrete class where application logic for the above mentioned
dialog should go. The world is your oyster here really....

[pluginlcasename].qrc  
This is the Qt4 resources file for your plugin. The Makefile generated for your
plugin is all set up to compile the resource file so all you need to do is add
your additional icons etc using the simple xml file format. Note the namespace
used for all your resources e.g. (":/[pluginname]/"). It is important to use
this prefix for all your resources. We suggest you include any other images and
run time data in this resurce file too.

[pluginlcasename].png  
This is the icon that will be used for your plugin menu entry and toolbar icon.
Simply replace this icon with your own icon to make your plugin disctinctive
from the rest.

README
This file contains the documentation you are reading now!


Getting developer help:
-------------------------------------------------------------

For Questions and Comments regarding the plugin builder template and creating
your features in QGIS using the plugin interface please contact us via:

 * the QGIS developers mailing list, or
 * IRC (#qgis on freenode.net)

QGIS is distributed under the Gnu Public License. If you create a useful plugin
please consider contributing it back to the community.

Have fun and thank you for choosing QGIS.

The QGIS Team
2007