+1 from me. Sounds like a great idea. Plugin writing is something that new users tend to stuggle with and it would be good to have a nice setup to get them started.<div><br></div><div>- Nathan<br><br><div class="gmail_quote">
On Sat, Feb 11, 2012 at 8:43 AM, Larry Shaffer <span dir="ltr"><<a href="mailto:larrys@dakotacarto.com">larrys@dakotacarto.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Tim,<br>
<br>
On Fri, Feb 10, 2012 at 12:34 PM, Tim Sutton <<a href="mailto:lists@linfiniti.com">lists@linfiniti.com</a>> wrote:<br>
...<br>
<div class="im">>> My opinion is that releasing QGIS with the pre-built addition of this<br>
>> PyQt editor widget (~1 MB compressed) for use by developers, to add<br>
>> embedded text editors, would be very beneficial.<br>
>><br>
><br>
> I don't know what others think, but I for one would love to see your<br>
> plugin ship with QGIS by default (ie. have it incorporated into core).<br>
> Doing so would of course simultaneously resolve your request above.<br>
<br>
</div>Thanks for the kind words. It's been an enjoyable learning experience<br>
for me. I should have a limited experimental version out sometime next<br>
week.<br>
<br>
I'm working on the .ui, .ts, and .qrc compiling tools now, and have<br>
some more documentation to write. Things that will be missing in the<br>
initial release will be: plugin duplication, new plugins from<br>
templates, packaging and uploading to repository, and the tutorial.<br>
Everything else is working fairly well.<br>
<br>
Right now I need others to beta-test the core functionality before<br>
spending anymore time on extra features. I've had it running on my new<br>
iMac at work and under Ubuntu Oneiric with 30+ tabs open, without<br>
crashing, albeit the editor gets too glitchy to use.<br>
<br>
The interface is intended specifically for reducing the learning curve<br>
to writing plugins. Then, after a small project or two, users might<br>
migrate to a real external IDE and debugging, etc., coming back to the<br>
editor for the packaging tools and user-space<br>
tweaking/testing/browsing.<br>
<br>
The editor can always get better, since Detlev's Eric IDE has a<br>
seemingly endless selection of well-coded, modular features written in<br>
PyQt. (QScintilla support is key, though.)<br>
<div class="im"><br>
<br>
> By the way we have been mulling over updating the plugin template to<br>
> do the following:<br>
><br>
> - pep8 compliance<br>
> - pylint friendly<br>
> - ship with a unit test framework<br>
> - ship with a ready to roll sphinx project<br>
<br>
<br>
</div>Some of those sound like good verifications to add to the packaging<br>
tool in the editor as well. The packaging and uploading tools are<br>
intended to ease the repository maintainers' and plugin developers'<br>
burden by helping to ensure proper metadata and file structure/content<br>
prior to submission.<br>
<br>
I'm hoping that some other plugin developers will help add new 'use<br>
case' templates, either to the repository or to be included with the<br>
editor. This way, a new user can choose a semi-close template to what<br>
they are thinking of undertaking (e.g. raster manipulation, working<br>
with legend layers, composer usage, etc.)... basically, starter<br>
plugins inline with the conceptual sections of the cookbook.<br>
<div class="HOEnZb"><div class="h5"><br>
Regards,<br>
<br>
Larry Shaffer<br>
Dakota Cartography<br>
Black Hills, South Dakota<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</div></div></blockquote></div><br></div>