<font color="#888888"><br><br></font><br><div class="gmail_quote">On Mon, Mar 19, 2012 at 12:33 PM, Paolo Cavallini <span dir="ltr"><<a href="mailto:cavallini@faunalia.it">cavallini@faunalia.it</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
I think porting to C++ should be a second step. As Martin has pointed out several<br>
times, prototyping, deploying and testing is far faster in Python, so I would suggest<br>
first finishing to develop the framework in py, leaviong the porting to a second<br>
time, if necessary. The plugin in itself is not doing any heavy computation, so<br>
execution time is not an issue here.<br>
fTools could be reimplemented as an additional backend (using GEOS) of the same<br>
framework.<br>
All the best.<br><span class="HOEnZb"></span><br clear="all"></blockquote></div><br>Of course I accept that development in python has a lot of advantages, and the language is not new to me. I was more concerned about the fact that development in C++ could yield better expansion of the native API so more things can be built over. <br>
<br>In case we need to complete the task of finishing the Processing framework in Python, it would make summer even better :)<br><br><br>-- <br>Regards<br>Arunmozhi<br>Twitter: @tecoholic<br>Website: <a href="http://arunmozhi.in" target="_blank">http://arunmozhi.in</a><br>
IRC Nick: teco<br><br>