That sounds like a pretty good idea too. Shoudn't be too hard to whip up a prototype for that.<br><br><div class="gmail_quote">On Thu, Jun 16, 2011 at 10:27 PM, Barry Rowlingson <span dir="ltr"><<a href="mailto:b.rowlingson@lancaster.ac.uk">b.rowlingson@lancaster.ac.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Thu, Jun 16, 2011 at 12:33 PM, Nathan Woodrow <<a href="mailto:madmanwoo@gmail.com">madmanwoo@gmail.com</a>> wrote:<br>
<br>
> I would appreciated any feedback anyone has. I'm not a python expert so the<br>
> code could be done better if done for real but at the moment it's just rough<br>
> to get the idea out there.<br>
<br>
</div> I like the idea of supplying console functionality for plugins.<br>
<br>
I don't like the idea of piggybacking via "PREFIX: foo" syntax onto Python.<br>
<br>
People might think they can mix python variables with variables in<br>
other DSLs. Which would be tricky.<br>
<br>
What might be nice would be if the Python console could exist in a<br>
tabbed window, and plugins could have an 'open console' option, which<br>
would add a tab to the python console. This would provide standard<br>
console functionality and then feed the lines to a handler registered<br>
by the plugin.<br>
<br>
Maybe you could even have seventeen python console tabs open at once<br>
next to four SQL command tabs and one interface to the QGIS API<br>
written in perl?<br>
<font color="#888888"><br>
Barry<br>
</font></blockquote></div><br>