Re: [Geany-Devel] Windows installer snapshots with GTK 2.24
On 27/06/15 20:53, Thomas Martitz wrote: Am 27.06.2015 um 01:09 schrieb Enrico Tröger: Hi, I've built new Windows installers from current GIT master. Downloads can be found here: http://download.geany.org/snapshots/ Please note that these are test builds from the current development version, don't expect release quality. You have been warned :). After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation). Any feedback is welcome. Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow). Nice too! Since this may affect your work too: after Jiří's feedback, I made two changes to the Windows installer: - include grep.exe - update geany-themes repo in release.py I added a note about including grep.exe on https://wiki.geany.org/howtos/win32/build#create_a_stripped_down_gtk_runtime_environment. It'd be cool if you could do something similar in your scripts (grep.exe doesn't need to be in the GTK runtime directory, as long as will result in the Geany bin installation directory at the end). And I updated the Geany release.py linked in the Wiki with a 'git pull' command in the geany-themes repository. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc 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] Windows installer snapshots with GTK 2.24
On 27/06/15 12:01, Jiří Techet wrote: On Sat, Jun 27, 2015 at 1:09 AM, Enrico Tröger enrico.troe...@uvena.de wrote: Hi, I've built new Windows installers from current GIT master. Downloads can be found here: http://download.geany.org/snapshots/ Please note that these are test builds from the current development version, don't expect release quality. You have been warned :). After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation). Any feedback is welcome. One more minor thing I have noticed is there are some themes included in the installer but some from geany-themes are missing so you might want to update them. Oops, I completely forgot about this. Themes are updated on my build machine (this is as easy as 'git pull' :D) and I added the command to the release script to not forget it again :). Thanks. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc 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] Windows installer snapshots with GTK 2.24
On 27/06/15 01:09, Enrico Tröger wrote: Hi, I've built new Windows installers from current GIT master. Downloads can be found here: http://download.geany.org/snapshots/ New installers uploaded, download location and installer names are the same. Changes since last time: - include grep.exe to instantly use Find in Files without any further user interaction - updated included colorschemes from the geany-themes project - whatever happened in GIT master of Geany and Geany-Plugins Thanks to Jiří. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc 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] Windows installer snapshots with GTK 2.24
On 28/06/15 15:09, Thomas Martitz wrote: Am 28.06.2015 um 12:36 schrieb Enrico Tröger: On 27/06/15 20:53, Thomas Martitz wrote: Am 27.06.2015 um 01:09 schrieb Enrico Tröger: Hi, I've built new Windows installers from current GIT master. Downloads can be found here: http://download.geany.org/snapshots/ Please note that these are test builds from the current development version, don't expect release quality. You have been warned :). After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation). Any feedback is welcome. Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow). Nice too! Not sure I'll bother anymore. To me it doesn't look like there is any interest in a GTK3-based windows version seeing how immediately my bug fixes got post-poned. I also feel uneasy with myself releasing a GTK3-1.25 which is actually a 1.25+ because it has patches applied (because my bug fixes aren't accepted in time, and plain git master isn't up to it) As said in PR #539, the 'immediate post-poning' was not because of lacking interest in GTK3-based Windows version but rather being a bit anxious with changing Windows-stuff before a release. But that's my personal problem not having the balls on Windows changes :). Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc 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] Windows installer snapshots with GTK 2.24
Hi Jiří, I've built new Windows installers from current GIT master. [..] Any feedback is welcome. Hi Enrico, seems to be working fine here. One idea: wouldn't it be good to package the grep binary to the installer (and if possible somehow set the preferences to the location where it was installed) so find in files works out of the box? Right now the message you get when trying to use find in files is: great idea! Will be included in the next installer, it's just 79kB. Luckily, and if I don't miss anything, we don't need to set any paths because the default path for grep is just grep and when grep.exe is in the bin/ directory next to Geany.exe, it should work out of the box. search_find_in_files: spawn_with_callbacks() failed: CreateProcess() failed: The system cannot find the file specified. which isn't the most user-friendly message and I guess many people will interpret it as find in files doesn't work on Windows. True. I guess we can improve the error message but maybe better after 1.25 to not bother the translators too much by breaking the string freeze :). Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc 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] Windows installer snapshots with GTK 2.24
Am 28.06.2015 um 12:36 schrieb Enrico Tröger: On 27/06/15 20:53, Thomas Martitz wrote: Am 27.06.2015 um 01:09 schrieb Enrico Tröger: Hi, I've built new Windows installers from current GIT master. Downloads can be found here: http://download.geany.org/snapshots/ Please note that these are test builds from the current development version, don't expect release quality. You have been warned :). After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation). Any feedback is welcome. Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow). Nice too! Not sure I'll bother anymore. To me it doesn't look like there is any interest in a GTK3-based windows version seeing how immediately my bug fixes got post-poned. I also feel uneasy with myself releasing a GTK3-1.25 which is actually a 1.25+ because it has patches applied (because my bug fixes aren't accepted in time, and plain git master isn't up to it) Best regards. ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] Windows installer snapshots with GTK 2.24
[...] Not sure I'll bother anymore. To me it doesn't look like there is any interest in a GTK3-based windows version seeing how immediately my bug fixes got post-poned. I also feel uneasy with myself releasing a GTK3-1.25 which is actually a 1.25+ because it has patches applied (because my bug fixes aren't accepted in time, and plain git master isn't up to it) As said in PR #539, the 'immediate post-poning' was not because of lacking interest in GTK3-based Windows version but rather being a bit anxious with changing Windows-stuff before a release. But that's my personal problem not having the balls on Windows changes :). Its more the intelligence to learn from past mistakes :) Cheers Lex Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc ___ 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
Re: [Geany-Devel] f403e7e (PR#188) - Maintain edit history on document reload
Am 26.06.2015 um 07:22 schrieb Thomas Martitz: Hello, I hacked up a document message to inform the user about this new behavior, see attached screenshot. However, as we entered string freeze, I don't suppose a new dialog like this is acceptable at this point? What else can we do for *this* release? Bump. IMO this should be resolved for 1.25. Should I do a PR regardless of the string freeze? Best regards. ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] Windows installer snapshots with GTK 2.24
On Sun, Jun 28, 2015 at 11:53 AM, Enrico Tröger enrico.troe...@uvena.de wrote: Hi Jiří, I've built new Windows installers from current GIT master. [..] Any feedback is welcome. Hi Enrico, seems to be working fine here. One idea: wouldn't it be good to package the grep binary to the installer (and if possible somehow set the preferences to the location where it was installed) so find in files works out of the box? Right now the message you get when trying to use find in files is: great idea! Will be included in the next installer, it's just 79kB. Luckily, and if I don't miss anything, we don't need to set any paths because the default path for grep is just grep and when grep.exe is in the bin/ directory next to Geany.exe, it should work out of the box. Just tried the latest installer and works great, thanks! Cool it wasn't necessary to modify the config file when installing. search_find_in_files: spawn_with_callbacks() failed: CreateProcess() failed: The system cannot find the file specified. which isn't the most user-friendly message and I guess many people will interpret it as find in files doesn't work on Windows. True. I guess we can improve the error message but maybe better after 1.25 to not bother the translators too much by breaking the string freeze :). I have just created a bug report here https://github.com/geany/geany/issues/541 It can wait for the next release especially as grep works now. Cheers, Jiri ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] Spawn module API
Am 28.06.2015 um 05:14 schrieb Matthew Brush: On 2015-06-27 07:54 PM, Lex Trotman wrote: On 28 June 2015 at 12:40, Matthew Brush mbr...@codebrainz.ca wrote: On 2015-06-27 12:46 PM, Dimitar Zhekov wrote: [...] An updated list of the API-s asked to remain public: meWIF* lexspawn_get_program_name lexspawn_check_command me/lexspawn_kill_process spawn_async_with_pipes lexspawn_async me/lexspawn_with_callbacks mespawn_write_data lex?spawn_get_exit_status_cb lexspawn_sync We should only export what you have concrete plans to use during the next cycle. If Lex wants update plugins during the next cycle to use other parts of the API, we can expose them at the time that the PR is made. No point to speculatively expose API that nobody has immediate plans to use. If no API is available then nobody will have any plans so no API is needed so nobody will have any plans for the egg so no chicken is needed so It can easily be made available on-demand, as normal. We should only be concerned about what Scope is requesting as it has concrete plans to use them during the next development cycle and doesn't want the plugin to depend on the next development version of Geany during that time[0]. There's no reason to speculatively rush other APIs in if no plugins have immediate plans to use them nor have the concern about depending on the development version of Geany. Depending on a development version of Geany can be a concern. I don't want to judge on the specific spawn_* APIs. But why not just release with the APIs being available (linkable by plugins) without already setting them officially in stone. In other words, find a method to mark these APIs experimental so that we can more easily change or remove them. This experimental flag should be set for at least one release cycle (but perhaps more depending on the situation). Then only plugin developers that are prepared to adapt their plugins quickly can use them (likely the same plugin developers who pushed the API into Geany for their plugins in the first place). Arguably, this should be the default process for any new API (IMO). Best regards ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] f403e7e (PR#188) - Maintain edit history on document reload
Le 26/06/2015 07:22, Thomas Martitz a écrit : […] However, as we entered string freeze, I don't suppose a new dialog like this is acceptable at this point? It would be really better not to indeed? What else can we do for *this* release? Hum. If this is an important enough issue, I can see these solutions: - Default to not keep history (hence prompt); - Add an extra hidden setting don't show this message again-like for a *future* dialog/infobar, so it still always asks unless the user manually changes this hidden setting. Both are suboptimal for this feature, but if it's a problem we can probably delay default enabling to the next cycle. Colomban ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] [Geany-devel] Geany-Plugins: Windows test build for 1.22 available
Am 28.06.2015 um 21:30 schrieb Thomas Martitz: Am 28.06.2015 um 20:39 schrieb Colomban Wendling: Le 03/07/2012 20:15, Enrico Tröger a écrit : […] If someone have more information about available builds (and a related -dev package) I might have a look though I doubt we'll manage that for the 1.22 release which is, AFAIK, due on upcoming Sunday. As I heard msys2 has builds for everything, maybe it has WebKitGtk too? Just a passing thought :) It has: mingw/*mingw-w64-webkitgtk2* 2.4.8-2 GTK+ Web content engine library (mingw-w64) for GTK2 mingw/*mingw-w64-webkitgtk3* 2.4.8-2 GTK+ Web content engine library (mingw-w64) (all mingw-w64-* prefixed packages are built for i686 (32bit) and x86_64 (64bit)) I think that's a yes? Oh, and the script I add in [1] can be used to gather all other dependency packages for destribution.However webkitgtk in this case would ship with geany-plugins and not geany core. [1] https://github.com/kugel-/geany/commit/d66f63660e1bf40f7f34e963a2182b0d41f4ca14 Best regards ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] [Geany-devel] Geany-Plugins: Windows test build for 1.22 available
Am 28.06.2015 um 20:39 schrieb Colomban Wendling: Le 03/07/2012 20:15, Enrico Tröger a écrit : […] If someone have more information about available builds (and a related -dev package) I might have a look though I doubt we'll manage that for the 1.22 release which is, AFAIK, due on upcoming Sunday. As I heard msys2 has builds for everything, maybe it has WebKitGtk too? Just a passing thought :) It has: mingw/*mingw-w64-webkitgtk2* 2.4.8-2 GTK+ Web content engine library (mingw-w64) for GTK2 mingw/*mingw-w64-webkitgtk3* 2.4.8-2 GTK+ Web content engine library (mingw-w64) (all mingw-w64-* prefixed packages are built for i686 (32bit) and x86_64 (64bit)) I think that's a yes? ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] f403e7e (PR#188) - Maintain edit history on document reload
On 29 June 2015 at 07:41, Colomban Wendling lists@herbesfolles.org wrote: Le 26/06/2015 07:22, Thomas Martitz a écrit : […] However, as we entered string freeze, I don't suppose a new dialog like this is acceptable at this point? It would be really better not to indeed? What else can we do for *this* release? Hum. If this is an important enough issue, I can see these solutions: - Default to not keep history (hence prompt); - Add an extra hidden setting don't show this message again-like for a *future* dialog/infobar, so it still always asks unless the user manually changes this hidden setting. Both are suboptimal for this feature, but if it's a problem we can probably delay default enabling to the next cycle. Or just put a BIG notice in the release notes Reload is now undoable so it doesn't prompt any more Colomban ___ 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
Re: [Geany-Devel] Beginner Help
Hi everyone! , I want to pick a project to work on and needed some help. I was wondering what would be a perfect beginners project/ or practise assignment. Also, if there is such a thing what files should I read and what source code should I take a look at. PS: I have looked at the HACKING file and have had a decent look at the bugs and feature requests Thanks, Atal Akbari From: devel-requ...@lists.geany.org Subject: Devel Digest, Vol 87, Issue 27 To: devel@lists.geany.org Date: Sun, 28 Jun 2015 09:00:02 + Send Devel mailing list submissions to devel@lists.geany.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.geany.org/cgi-bin/mailman/listinfo/devel or, via email, send a message with subject or body 'help' to devel-requ...@lists.geany.org You can reach the person managing the list at devel-ow...@lists.geany.org When replying, please edit your Subject line so it is more specific than Re: Contents of Devel digest... Today's Topics: 1. Re: Spawn module API (Lex Trotman) 2. Re: Spawn module API (Lex Trotman) 3. Re: Spawn module API (Matthew Brush) -- Message: 1 Date: Sun, 28 Jun 2015 12:54:56 +1000 From: Lex Trotman ele...@gmail.com To: Geany development list devel@lists.geany.org Subject: Re: [Geany-Devel] Spawn module API Message-ID: CAKhWKDP9E-pcyrUQT0Og7wB-g45BnPT_RBoGM=4-f3lykca...@mail.gmail.com Content-Type: text/plain; charset=UTF-8 On 28 June 2015 at 12:40, Matthew Brush mbr...@codebrainz.ca wrote: On 2015-06-27 12:46 PM, Dimitar Zhekov wrote: [...] An updated list of the API-s asked to remain public: meWIF* lexspawn_get_program_name lexspawn_check_command me/lexspawn_kill_process spawn_async_with_pipes lexspawn_async me/lexspawn_with_callbacks mespawn_write_data lex?spawn_get_exit_status_cb lexspawn_sync We should only export what you have concrete plans to use during the next cycle. If Lex wants update plugins during the next cycle to use other parts of the API, we can expose them at the time that the PR is made. No point to speculatively expose API that nobody has immediate plans to use. If no API is available then nobody will have any plans so no API is needed so nobody will have any plans for the egg so no chicken is needed so Cheers, Matthew Brush ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel -- Message: 2 Date: Sun, 28 Jun 2015 13:04:07 +1000 From: Lex Trotman ele...@gmail.com To: Geany development list devel@lists.geany.org Subject: Re: [Geany-Devel] Spawn module API Message-ID: cakhwkdpovzma--nnlxw83q4unqxqyxdmyd9yjfaq+nqztew...@mail.gmail.com Content-Type: text/plain; charset=UTF-8 On 28 June 2015 at 12:54, Lex Trotman ele...@gmail.com wrote: On 28 June 2015 at 12:40, Matthew Brush mbr...@codebrainz.ca wrote: On 2015-06-27 12:46 PM, Dimitar Zhekov wrote: [...] An updated list of the API-s asked to remain public: meWIF* lexspawn_get_program_name lexspawn_check_command me/lexspawn_kill_process spawn_async_with_pipes lexspawn_async me/lexspawn_with_callbacks mespawn_write_data lex?spawn_get_exit_status_cb lexspawn_sync We should only export what you have concrete plans to use during the next cycle. If Lex wants update plugins during the next cycle to use other parts of the API, we can expose them at the time that the PR is made. No point to speculatively expose API that nobody has immediate plans to use. If no API is available then nobody will have any plans so no API is needed so nobody will have any plans for the egg so no chicken is needed so Or to look at it another way: Welcome to Geany 1.25, so that their command parsing is the same as Geanys, all plugins are recommended to upgrade to the spawn_* API - that we havn't released. Cheers Lex Cheers, Matthew Brush ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel -- Message: 3 Date: Sat, 27 Jun 2015 20:14:06 -0700 From: Matthew Brush mbr...@codebrainz.ca To: devel@lists.geany.org Subject: Re: [Geany-Devel] Spawn module API Message-ID: 558f667e.90...@codebrainz.ca Content-Type: text/plain; charset=windows-1252; format=flowed On 2015-06-27 07:54 PM, Lex Trotman wrote: On 28 June 2015 at 12:40, Matthew Brush mbr...@codebrainz.ca wrote: On 2015-06-27 12:46 PM, Dimitar Zhekov wrote: [...] An updated list of the API-s asked to remain public: meWIF* lexspawn_get_program_name lex
