On Tue, 20 Oct 2020 at 19:40, Raymond Nijssen wrote:
>
> If the code snippets are not suitable for the cookbook (because they are
> too odd cases and/or they do not match the cookbook chapters) and you
> decide to put them anywhere else, it would be good practice to add the
> QGIS version number
This is why I mentioned snibox, as it's the best self hosted platform I've
found of the bunch for this sort of thing... They have a demo app:
https://snibox.github.io/docs/demo.html
I'm +1 for Raymond's suggestion on versioning, however I think we need a
decent convention for this that makes it
This is an interesting discussion. I am an outsider in that I do not use
PyQGIS particularly often. However, based on similar experiences, I can
feel I can add my two cents.
Any repository (software or otherwise!) requires a maintenance plan,
active maintainer(s) and a search tool of sorts to
Thanks for a really thoughtful overview of the issues.
I don't think Stack Overflow or any of the Stack Exchange sites are
the right way to go. In addition to your gamification objections (to
which I add the obsessive "that's two questions" objections), it's
just
If the code snippets are not suitable for the cookbook (because they are
too odd cases and/or they do not match the cookbook chapters) and you
decide to put them anywhere else, it would be good practice to add the
QGIS version number somewhere.
Raymond
On 20-10-2020 11:20, Charles
I agree that the cookbook is a great resource (which is why I put it first
on my list), but I think it's better suited to general examples and giving
a solid outline of the best practices. If it's not kept concise, it could
become a bit of a convoluted mess, in addition to all the broken code
On 10/20/20 10:48 AM, Jorge Gustavo Rocha wrote:
> Hi,
>
> I think the PyQGIS Cookbook is the perfect place to share these scripts. The
> Cookbook is not the API reference documentation. It is the place to share
> solutions for common problems using the QGIS API.
While I agree with this, note
Hi,
I think the PyQGIS Cookbook is the perfect place to share these scripts.
The Cookbook is not the API reference documentation. It is the place to
share solutions for common problems using the QGIS API.
Regards,
Jorge
Às 08:34 de 20/10/20, Charles Dixon-Paver escreveu:
> Personally I feel
Personally I feel like this outlines a greater problem of snippet sharing
in many developer communities and is not a problem that is well suited to
the resource sharing plugin, or even a single traditional GitHub repo.
My personal approach was to set up a subdirectory on GitHub with code
snippets
Is there a place where folks can contribute scripts that others
might find useful? I know about the Resource Sharing plug-in, which
is a way to point to a repository one is maintaining. I'm thinking
more of a common repository where some might contribute the odd
script.
10 matches
Mail list logo
