Re: [Geany-Devel] GeanyLua compatiblity with Lua 5.2
Am 25. April 2015 05:22:38 MESZ, schrieb Colomban Wendling lists@herbesfolles.org: So yeah, if anyone wishing to keep on using this plugin should consider helping maintaining it, it really needs some love from time to time. Libpeas includes lua support as of v1.14. So if my whole proxy plug-in work would be accepted (in some way or another) I can maintain lua support through my Libpeas based peasy plug-in. That would even have access to Geany APIs unlike current geanylua. Best regards ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] [geany/geany-plugins] 377322: Scope: Fix a typo
On 22.4.2015 г. 21:19, Frank Lanitz wrote: Am 22.04.2015 um 20:14 schrieb Dimitar Zhekov: -property name=label translatable=yesShow =li_brary messages/property +property name=label translatable=yesShow li_brary messages/property That's not a typo, they are =library-... library alone does not carry enough info. OK. With = it really doesn't make sense to me. But I'm fine to revert as I really thought it's just a typo. I accidentally fixed it while removing support for gtk+ 2.16... I'll change the text so something more clear, and add a TL-node. -- E-gards: Jimmy ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] [geany/geany] f03206: Windows: Compile geany_private.rc into Geany.exe for version data and icon
On 19/04/15 15:40, Enrico Tröger wrote: On 18/04/15 21:35, Matthew Brush wrote: On 15-04-18 03:51 AM, Enrico Tröger wrote: On 18/04/15 11:47, Enrico Tröger wrote: On 17/04/15 21:32, Colomban Wendling wrote: Le 12/04/2015 22:54, Enrico Tröger a écrit : Branch: refs/heads/master Author: Enrico Tröger enrico.troe...@uvena.de Committer: Enrico Tröger enrico.troe...@uvena.de Date:Sun, 12 Apr 2015 20:54:16 UTC Commit: f03206744361baac1c811db97f5d2816409d7787 https://github.com/geany/geany/commit/f03206744361baac1c811db97f5d2816409d7787 Log Message: --- Windows: Compile geany_private.rc into Geany.exe for version data and icon Should we integrate geany_private.rc in the library too? This isn't done with Autotools, but could be added. It's not really necessary. For Waf, I just added it to the binary where it is necessary and kept it for the library. The rc file serves two main purposes: - add the icon to the binary - add versioning information to the binary (e.g. in the file properties dialog in the Details tab) While especially the icon is important for the binary, I guess the rc file is just nice to have for the library but not necessary. But I agree we should do the same for Waf and autotools, either link it or don't link it. I don't mind which way to go. After thinking a bit more about this, I think we should not link the rc file against the library. We also don't link it against the plugin libraries. The rc file contains settings that the resulting binary is an executable and it includes also the geany.exe.manifest. Both do not apply to the library. So it is actually wrong to use that rc file for the library. If there are no objections, I will remove linking the rc file against the library in Waf. None here. I think the way it might make sense is if it contained artwork, UIs, translations and stuff like they often do for Win32 API projects, and that were actually used in libgeany.dll, but since we just use it for the .exe icon, meta-info, styles, etc. I tend to agree it makes more sense linked to the .exe. We might still want an .rc file for the library though, if it's important to show the correct meta-info in Windows explorer for the .dll file (I dunno if it is?). I don't think so. The only benefit I see is that in the Windows explorer file properties dialog version information would appear. I don't know if Windows or any related software rely on this information or use it in any way. We also don't add this information to the plugin libraries and so why do it for geany.dll. To finish this, I just removed linking the rc file against the library. 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] [geany/geany-plugins] 73ae49: waf: Fix the checks for openpty() on FreeBSD
On 19.4.2015 г. 16:43, Enrico Tröger wrote: On 17/04/15 21:42, Dimitar Zhekov wrote: Alright, I finally got it. To whoever might be interested: 1. The default theme for gtk+ 2.24 under Windows has been changed [...] 2. The horizontal (only) notebook tabs backgrounds under MS-Windows is unchangeable with any gtkrc settings. [...] So, how do we want to proceed? Warn the users that the default theme has been changed, and they need gtk-theme-name = Raleigh in etc/gtkrc to get the previous behavior (unless they already have set a theme, in which case there will be no difference). Using .gtkrc-2.0 in their home path will also work, for the people who prefer/need to run Win~1 as a regular user. Provided that Thomas' underline trick works with the MS-Windows theme, we could maybe add this to the Wiki by providing a copypaste ready gtkrc snippet for Windows users who want to a better visual indication of the active tab? That would be nice, I have seen editors under Win~1 providing bold as an option for the active tab. However, I don't know a way to address the editor notebook specifically under gtk+ 2, without affecting the sidebar (and any other notebooks at the same hierarchy level). Setting the editor notebook widget name to GeanyEditorNotebook does the trick, but breaks compatibility: the current widget GeanyMainWindow.GtkVBox.GtkVPaned.GtkHPaned.GtkNotebook* addressing does not match GeanyEditorNotebook any more. So, instead of setting the widget name in Geany, it may be better to write a small plugin that ui_lookups for specified widget id-s, and sets their widget names. That'll make every single geany.glade widget addressable, and let the user decide on what (s)he wants. -- E-gards: Jimmy ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
