Yes why not. I used originally the 2.0 version but changed to 2.0.2
later. There are two options: to use it as it comes with the provided
interface components or to use the Ziggis Classes in your own
implementation. That depends on your requirements concerning the
integration of postgis editing in your own processes. I used the
classes for my own implementation. For instance I had to change the
code because I wanted to include some edits of related attribute data
in the ziggis transaction so that everything is committed or rolled
back together. There were some other things which I changed to fit my
project e.g. loading of layers from a own function and connecting data
sources to layer files for predefined map representation and others. I
struggled in the beginning but now it seams to work ok. It is
recommended to develop some trigger functions in the database as well
for checking the integrity and topology of you edits. The performance
is ok if you have not loads of data. However you can easily filter
data in the definition query for larger data sets.
Some postgesql datatypes are not supported - so you have to check your
data model and may be adapt to ziggis.
Regards
Volkmar
On Jun 11, 2:40 pm, Intengu Technologies <
sindile.bi...@gmail.com>
wrote: