[Qgis-user] Re: [Qgis-developer] announcing DPSimplify

[Maxim Dubinin]

Hi all,

The idea of DPSimplify was mine and responsibility
for overlooking close functionality in fTools is also mine. However,
our plugin is 3 times better ;)

We'll be happy to move the plugin to fTools when we're done with
it which will greatly improve its functionality.

In general, we see most of our development in Vector area (Statist,
JoinLines, DPSimplify to name the few) as potentially included in
fTools (Vector) or enhancing present tools.

Maxim

Вы писали 5 марта 2010 г., 4:55:59:

CF> Hello list,

CF> I'm a bit late coming into this discussion, by I thought I might be a
CF> good place to make a few comments:

CF> New plugins that add new functionality are always very welcome,
CF> however I would also like to encourage plugin developers to have a
CF> look at (particularly core plugins) existing plugins, and if they find
CF> something they would like to improve/replace, to do so! I don't have a
CF> lot of time to update fTools, but improvements are always welcome, and
CF> if they are added/applied to fTools directly, then the whole QGIS
CF> community benefits from the improvements/changes without having to
CF> install another plugin (and without duplication in the eyes of the
CF> user).

>> And to make myself clear: I do not want to discourage Alexander to develop
>> the plugin!! Because if I'm correct, the current vector-menu stuff is
>> actually cpp ported from the former python plugin as well.

CF> Just to clarify, most of the fTools functions have still not been
CF> ported to cpp, and in fact anything running from fTools at the moment
CF> is still using the original Python implementation. So again, I would
CF> encourage developers of fTools functionality to try to include them
CF> with fTools so that they can be installed by users by default. Patches
CF> are always welcome, and credit will always be given where credit is
CF> due!

CF> Regards,

CF> Carson