Re: [Geany-Devel] Storing per-project settings for plugins

2017-02-16 Thread Lex Trotman
> >> >> What does that mean? It's not 100% perfect, but it does what it's intended >> to do quite well. Should we just start committing random changes so it's >> "actively developed"? > > > > It's not being updated for new Geany APIs, nor does the upstream developer > (you :-) review PRs in a

Re: [Geany-Devel] Storing per-project settings for plugins

2017-02-16 Thread Vasiliy Faronov
Hi Thomas, On Thu, Feb 16, 2017 at 2:15 PM, Thomas Martitz wrote: > Geanypy is not actively developed at this time. Let me suggest to give my > Peasy plugin a > try, as all the signals should be working there. Peasy is a newer approach > to support Python (and lua) > plugins

Re: [Geany-Devel] Storing per-project settings for plugins

2017-02-16 Thread Thomas Martitz
Am 16.02.2017 um 15:55 schrieb Matthew Brush: On 2017-02-16 03:15 AM, Thomas Martitz wrote: Am 16.02.2017 um 11:58 schrieb Vasiliy Faronov: Jiří, Matthew, thanks! I missed the GKeyFile thing. Actually, my plugin is written in Python (via Geanypy), and doesn't get the GKeyFile on

Re: [Geany-Devel] Storing per-project settings for plugins

2017-02-16 Thread Matthew Brush
On 2017-02-16 03:15 AM, Thomas Martitz wrote: Am 16.02.2017 um 11:58 schrieb Vasiliy Faronov: Jiří, Matthew, thanks! I missed the GKeyFile thing. Actually, my plugin is written in Python (via Geanypy), and doesn't get the GKeyFile on project-open/project-save. Probably because there are no

Re: [Geany-Devel] Storing per-project settings for plugins

2017-02-15 Thread Jiří Techet
Hello Vasiliy, there should be no problem with your approach (the extra content of the config file will be preserved by Geany). However, Geany offers plugins the possibility to read/write from/to the project config files natively. When you register for the "project-open" signal, the callback is

[Geany-Devel] Storing per-project settings for plugins

2017-02-15 Thread Vasiliy Faronov
Hi, I have a small Geany plugin that needs some settings per Geany project. Currently, I do it as follows: the user manually writes a special section in the .geany project file, which my plugin reads as a generic INI file. I really like this approach (as a user) because it keeps all Geany