<div dir="ltr">> <span style="font-family:arial,sans-serif;font-size:13px">martin I will push the code for my project view sometime this weekend, got a few things on so not sure when i will get a minute.</span><div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Oly : Thank you - I've just installed the geanypy from upstream (</span><font face="arial, sans-serif"><a href="https://github.com/codebrainz/geanypy">https://github.com/codebrainz/geanypy</a>) to play with.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Lex : For the "packaging issues" : I understand that having a plugin as part of the geany-plugins ecosystem is no walk-in-the-park. On the other hand, it's definitely good to know that other people can make use of what one is building - even if that means having to stay on top of things if there are breaking changes in APIs, etc (or indeed, good patches, bug reports or ideas submitted). I agree that starting off 'third party' may be a good idea, although it would make sense to structure the package so that it could be dropped into the main tree relatively painlessly, later.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Cross-fingers I can make sense of the Pythonic interface : It would be great not to have to do a ton of string/tree manipulation in C.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Best Wishes</font></div><div><font face="arial, sans-serif">Martin</font></div><div><font face="arial, sans-serif">:-)</font></div><div>
<font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif"><br></font></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 18 April 2014 15:10, Oly <span dir="ltr"><<a href="mailto:olymk2@gmail.com" target="_blank">olymk2@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I would like to get some of my plugins into the main plugin list, perhaps i could create a pull request for one and we can use it as a test, i dont mind supporting it and fixing bugs the only part i dont really know anything about is the automake side of things.<br>
<br></div><div>I will perhaps push the python code checker, its reasonably small / simple plugin.<br></div><div><br></div><div>also not sure how you sort out dependency issues when its not packaged.<br><br></div><div>martin I will push the code for my project view sometime this weekend, got a few things on so not sure when i will get a minute.<br>
</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Apr 18, 2014 at 6:32 AM, Lex Trotman <span dir="ltr"><<a href="mailto:elextr@gmail.com" target="_blank">elextr@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">[...]<br>
<div>><br>
> On the packaging side, it would be great to have the incentive of getting<br>
> something onto the standard packaging system, since then it becomes a<br>
> simpler (more incremental) task to 'stay current' with geany, and not get<br>
> left behind (as happened with my previous SciTE dependency).<br>
<br>
</div>To make sure you don't have incorrect expectations let me explain.<br>
<br>
Geany-Plugins is a separate project from Geany providing a collection<br>
of plugins. Although some of its plugins are made by Geany<br>
developers, and it tries to synchronise releases with Geany for user<br>
convenience, the plugins are not supported by the Geany project or the<br>
Geany-Plugins project. You will still have to maintain any plugin<br>
that is part of the collection yourself (or get someone to volunteer<br>
for you). And being part of the collection means there is an extra<br>
step to that maintenance, beyond just having it in your own github, as<br>
you need to submit pull requests to the collection.<br>
<br>
Plugins that are not maintained are considered orphaned, and may be<br>
removed from the collection. (Well, that threat has not been carried<br>
out ... yet :)<br>
<br>
Of course being part of the Geany-Plugins collection means you *might*<br>
get more contributors than you would just on github, but you *will*<br>
get more feature demands, bug reports, complaints etc all of which<br>
have to be dealt with. If you would have trouble staying 'current'<br>
when your plugin is not in the Geany-Plugins collection, you will have<br>
more trouble if your plugin is in the collection, because there is<br>
more to do. Of course having other people using your plugin may<br>
provide you with an incentive you need.<br>
<br>
Initially you may be better off just using github and getting yourself<br>
listed on the "Third Party" list on the plugins website.<br>
<br>
Cheers<br>
Lex<br>
<br>
><br>
> Martin<br>
> :-)<br>
><br>
><br>
><br>
>[...]<br>
<div><div>_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.geany.org" target="_blank">Devel@lists.geany.org</a><br>
<a href="https://lists.geany.org/cgi-bin/mailman/listinfo/devel" target="_blank">https://lists.geany.org/cgi-bin/mailman/listinfo/devel</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.geany.org">Devel@lists.geany.org</a><br>
<a href="https://lists.geany.org/cgi-bin/mailman/listinfo/devel" target="_blank">https://lists.geany.org/cgi-bin/mailman/listinfo/devel</a><br>
<br></blockquote></div><br></div>