Feel free to use any of these plugins as a start for your own, maybe by copying the directory structure and the autotools files (Makefile.am, configure.in. You can also ask for your plugin to be listed on the website as a third party plugin, helping Geany user to know about your plugin.Īt time of writing, there are some plugins already available in the repositories. In this case it is of course also a good idea to post some kind of announcement to geany-devel and maybe to the main geany mailing list – it's up to you. Just skip the part about forking geany-plugins and sending a pull request. If you don't want your plugin to be part of the geany-plugins project it is also fine. But GitHub is making it way easier for review, merging and get in touch with you for comments. Of course, you don't need to use GitHub - any Git is fine. At this point, create a pull request for adding your patch set into the master branch of the main geany-plugins repository. However, once you have done your fork of geany-plugins you can develop your plugin until you think it is the right time to publish it. Beside of adding a new plugin, geany-devel-mailing list is also the place to discuss development related questions. To add a new plugin to this project, get in touch with the people on the geany-devel-mailing list and create a fork of the geany-plugins project at. All information about this project you can find at If you want to write a plugin but don't know yet what it should do, have a look at to get an idea about what users wish.įor authors of plugins for Geany, we created a dedicated geany-plugins project on Sourceforge and GitHub to ease development of plugins and help new authors. The following hints and guidelines are only recommendations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |