> 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.

Oly : Thank you - I've just installed the geanypy from upstream (https://github.com/codebrainz/geanypy) to play with.

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.

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.

Best Wishes
Martin
:-)




On 18 April 2014 15:10, Oly <olymk2@gmail.com> wrote:
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.

I will perhaps push the python code checker, its reasonably small / simple plugin.

also not sure how you sort out dependency issues when its not packaged.

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.


On Fri, Apr 18, 2014 at 6:32 AM, Lex Trotman <elextr@gmail.com> wrote:
[...]
>
> On the packaging side, it would be great to have the incentive of getting
> something onto the standard packaging system, since then it becomes a
> simpler (more incremental) task to 'stay current' with geany, and not get
> left behind (as happened with my previous SciTE dependency).

To make sure you don't have incorrect expectations let me explain.

Geany-Plugins is a separate project from Geany providing a collection
of plugins.  Although some of its plugins are made by Geany
developers, and it tries to synchronise releases with Geany for user
convenience, the plugins are not supported by the Geany project or the
Geany-Plugins project.  You will still have to maintain any plugin
that is part of the collection yourself (or get someone to volunteer
for you).  And being part of the collection means there is an extra
step to that maintenance, beyond just having it in your own github, as
you need to submit pull requests to the collection.

Plugins that are not maintained are considered orphaned, and may be
removed from the collection. (Well, that threat has not been carried
out ... yet :)

Of course being part of the Geany-Plugins collection means you *might*
get more contributors than you would just on github, but you *will*
get more feature demands, bug reports, complaints etc all of which
have to be dealt with.  If you would have trouble staying 'current'
when your plugin is not in the Geany-Plugins collection, you will have
more trouble if your plugin is in the collection, because there is
more to do.  Of course having other people using your plugin may
provide you with an incentive you need.

Initially you may be better off just using github and getting yourself
listed on the "Third Party" list on the plugins website.

Cheers
Lex

>
> Martin
> :-)
>
>
>
>[...]
_______________________________________________
Devel mailing list
Devel@lists.geany.org
https://lists.geany.org/cgi-bin/mailman/listinfo/devel


_______________________________________________
Devel mailing list
Devel@lists.geany.org
https://lists.geany.org/cgi-bin/mailman/listinfo/devel