Re: [Geany-Devel] Spawn module API
On 2015-06-21 04:25 AM, Dimitar Zhekov wrote: On 21.6.2015 г. 06:12, Matthew Brush wrote: I just noticed that the new spawn code exposes almost every single bit of API possible. Do we really want to do that, or should we limit it only to what is currently needed by any plugins? A quick survey of Geany-Plugins shows no usage of any of this yet. IMO, we shouldn't expose anything which is not needed by plugins, especially if it's not related to the plugin API. The API is designed not only to ease/fix the spawn pipe I/O, but as a possible replacement for all glib spawn functions - and these may be invoked by any plugin. (There is no replacement for g_spawn_close_pid, which works fine, and for g_spawn_check_exit_status, because it's 2.34+ only - instead, the WIF* macros are defined system-independently.) Spawn neither requires not uses anything from Geany (except i18n), and does not change anything in Geany state, so it's functions are not strictly "Geany" - it could be a separate library just as well. Yeah, it almost should be a "separate" library (at least like TM or MIO). Personally I don't like the tendency of Geany's plugin API to be getting bloated with stuff that has nothing to do with Geany or plugins, but rather general purpose stuff making up for shortcomings in GLib, or general-purpose convenience functions. But I think maybe this is a conversation for another day. In the next plugins (after this release), Scope will require at least WIF*, spawn_kill_process, SpawnFlags, SpawnReadFunc, spawn_with_callbacks, SpawnWriteData and spawn_write_data. It'll be good if 'debugger' uses them as well... I figured there would be some use in at least Scope. Do you have any problem if we make all the API private for now and then as you need it in Scope (or any other plugins requesting it) we can export precisely what is needed, at that time? Cheers, Matthew Brush ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
[Geany-Devel] String freeze of Geany core and Geany-Plugins for 1.25
Hi translators and friends of Geany, As by Colomban's mail we are only two weeks away from upcoming, new, amazing 1.25 release of Geany! It's scheduled for 2015-07-12. In prior of that we have to ensure, all translations of Geany and it's plugins are up to date and as complete as possible to get a great user experience using Geany. In preparation of that I've update po-files for Geany core as well as the geany-plugins project inside github repositories and asking you whether you could update translations, review them or maybe add new ones. I'd be very happy if you could send a patch, a pull request or single file with translation to either the geany-i18n mailing list or direct to me within the next two weeks so we can include it to the next release. Deadline will be 2015-07-11 CEST. To get most recent files you could just clone the repositories from Geany: https://github.com/geany/geany Geany-Plugins: https://github.com/geany/geany-plugins This can be done e.g. with git clone https://github.com/geany/geany.git or for the plugins git clone https://github.com/geany/geany-plugins.git Also at http://i18n.geany.org or http://i18n.geany.org/plugins for plugins are statistics and daily updated files available If your language was translated by two or more in past, please double check directly with them or by pinging me, so we don't need to translate same things two or three times. Also please feel to ping me for every question or if you like to start a new translation for an unsupported language. If you have any questions, don't hesitate to ping me directly via IRC: geany @freenode Jabber/XMPP: fr...@jabber.ccc.de or via Mail: look above or some of the mailing lists. @Plugin Maintainer: Please don't add new strings by now as they most likely will be properly translated for next release. Thanks and happy translating Frank signature.asc Description: OpenPGP digital signature ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] Spawn module API
On 21.6.2015 г. 06:12, Matthew Brush wrote: I just noticed that the new spawn code exposes almost every single bit of API possible. Do we really want to do that, or should we limit it only to what is currently needed by any plugins? A quick survey of Geany-Plugins shows no usage of any of this yet. IMO, we shouldn't expose anything which is not needed by plugins, especially if it's not related to the plugin API. The API is designed not only to ease/fix the spawn pipe I/O, but as a possible replacement for all glib spawn functions - and these may be invoked by any plugin. (There is no replacement for g_spawn_close_pid, which works fine, and for g_spawn_check_exit_status, because it's 2.34+ only - instead, the WIF* macros are defined system-independently.) Spawn neither requires not uses anything from Geany (except i18n), and does not change anything in Geany state, so it's functions are not strictly "Geany" - it could be a separate library just as well. In the next plugins (after this release), Scope will require at least WIF*, spawn_kill_process, SpawnFlags, SpawnReadFunc, spawn_with_callbacks, SpawnWriteData and spawn_write_data. It'll be good if 'debugger' uses them as well... -- E-gards: Jimmy ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] Spawn module API
On 2015-06-20 08:12 PM, Matthew Brush wrote: Hi All, I just noticed that the new spawn code exposes almost every single bit of API possible. Do we really want to do that, or should we limit it only to what is currently needed by any plugins? A quick survey of Geany-Plugins shows no usage of any of this yet. IMO, we shouldn't expose anything which is not needed by plugins, especially if it's not related to the plugin API. See: https://github.com/geany/geany/pull/523 Cheers, Matthew Brush ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
