<div class="gmail_quote">On Wed, May 25, 2011 at 1:21 PM, Radim Blazek <span dir="ltr"><<a href="mailto:radim.blazek@gmail.com">radim.blazek@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Wed, May 25, 2011 at 10:39 AM, Giuseppe Sucameli <<a href="mailto:brush.tyler@gmail.com">brush.tyler@gmail.com</a>> wrote:<br><div class="im">
<br>
</div><div class="im">> However we should consider to integrate useful python plugins in qgis code, porting<br>
> their base functions to C++ if necessary.<br>
<br>
</div>So why to write another important plugin in Python, with perspective<br>
that it has to be ported later to C++?<br></blockquote><div><br>Again, I would develop in python the GUI only, not the base functions ;)<br><br></div></div>Tell me what in the QBrowser class cannot be done in python, it's just a <br>
container. It uses the QgsBrowserModel and some other Qt based classes <br>I can easily handle in python without any problem. <br><br>I don't think the QBrowser code makes particular GUI widgets/functions we <br>should insert in app/core/gui. Different would be if you had developed a <br>
QgsBrowser tree widget implementing also the QgsLegend interface, as <br>everybody could reuse that.<br><br>However, discussing it we're also going to find what the current implementation <br>misses and what should be changed, doesn't matter if at the end it will be <br>
done in C++ or python. It will be Martin who has to decide.<br><br>No other devs want to partecipate to the discussion? ;)<br>I think that a lot of interesting things are coming out.<br><br>Regards.<br clear="all"><br>-- <br>
Giuseppe Sucameli<br>