Re: [Geany-devel] [RFC] Geany Plugin Names
Am Freitag, den 28.10.2011, 22:41 -0700 schrieb Matthew Brush: Anyway, just a thought to make things more consistent and less redundant. It seems like while converting and moving to Git would be an ideal time to do this. Feel free to +1, -1, comment or ignore. +1 :) -- Dominic Hopf dma...@googlemail.com http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [RFC] Geany Plugin Names
29.10.2011 09:41, Matthew Brush пишет: Hi all, Is anybody opposed to removing the geany and Geany prefix from the plugins in Geany-Plugins. I mean at least for the directory name in the source tree, README/Site, and PLUGIN_SET_INFO() name? It's always bothered me when I go into *Geany's* plugin manager and see plugin names like GeanyFooBar. Obviously the plugin is for Geany and the Geany prefix makes the plugin not ordered correctly. Same goes for the SVN/Git repository source tree directory names. For example: Geany-Zencoding plugin could be Zencoding under the directory in the repo called zencoding. This is like many plugins already, for example: addons, codenav, debugger, devhelp, gproject (sorta :), pretty-printer, shiftcolumn, spellcheck, tableconvert, treebrowser, updatechecker, webhelper, and xmlsnippets. IMO these would be reasonable renames for the others: Old Name Plugin Info Name Directory = GeanyDoc Documentation?[1] doc or geanydoc GeanyExtrasel Extra Selections extrasel Geanygdb GNU Debugger[2] gdb GeanyGenDoc Documentation Generator gendoc GeanyInsertNum Insert Numbers[3] insertnum GeanyLatex LaTeX (Addons) latex GeanyLipsum Lorem Ipsum Generator lipsum GeanyLua Lua Plugins lua GeanyMacro Macro Recorder macro GeanyNumberedBookmarks Numbered Bookmarks numberedbookmarks GeanyPg Privacy Guard pg or gpg GeanyPrj Project Manager?[4] prj or project GeanySendMail Send Mail sendmail GeanyVC Version Control vc or vcs --[coming soon]--- GeanyMultiTerm Multi-Tabbed Terminal multiterm GeanyPy Python Plugins python GeanyZencoding Zen Coding zencoding == [1] Could we merge Devhelp and GeanyDoc? [2] Could we replace in favour of Debugger? [3] Should this go in Addons? [4] Could we merge GProject and GeanyPrj or are totally different? == Anyway, just a thought to make things more consistent and less redundant. It seems like while converting and moving to Git would be an ideal time to do this. Feel free to +1, -1, comment or ignore. Cheers, Matthew Brush ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel +1 was thinking of it when translating plugin names ) as to gproject and geanyprj they differs in that gproject utilizes geany built-in project support while geanyprj uses it's own, so they are unlikely to be merged. Regards, Alexander ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [RFC] Geany Plugin Names
On Fri, 28 Oct 2011 22:41:07 -0700 Matthew Brush mbr...@codebrainz.ca wrote: Is anybody opposed to removing the geany and Geany prefix from the plugins in Geany-Plugins. I mean at least for the directory name in the source tree, README/Site, and PLUGIN_SET_INFO() name? -1. When installing binary packages, typing geany in the search box is the easiest way to see all the plugins. Personally I don't feel like installing the entire geany-plugins package (or all xfce panel plugins, all X11 video drivers etc.) If we decide to remove the prefix, Extra Selections should be Extra Selection. -- E-gards: Jimmy ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [RFC] Geany Plugin Names
On 29 October 2011 20:44, Dimitar Zhekov dimitar.zhe...@gmail.com wrote: On Fri, 28 Oct 2011 22:41:07 -0700 Matthew Brush mbr...@codebrainz.ca wrote: Is anybody opposed to removing the geany and Geany prefix from the plugins in Geany-Plugins. I mean at least for the directory name in the source tree, README/Site, and PLUGIN_SET_INFO() name? -1. When installing binary packages, typing geany in the search box is the easiest way to see all the plugins. Personally I don't feel like installing the entire geany-plugins package (or all xfce panel plugins, all X11 video drivers etc.) 1. the question is about the plugins *within* the g-p package and directory names and names shown in plugin manager 2. you are right that any plugin packaged *separately* should indeed have geany in the package name but that doesn't affect directory names or plugin manager names Cheers Lex If we decide to remove the prefix, Extra Selections should be Extra Selection. -- E-gards: Jimmy ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [RFC] Geany Plugin Names
29.10.2011 14:22, Lex Trotman ?: you are right that any plugin packaged*separately* should indeed have geany in the package name but that doesn't affect directory names or plugin manager names +1 package names are packaging teams buisness, as they are already named with geany- prefix (at least *.deb ones) no changes for them except new folder names. ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany Plugins Warnings (again)
Am 29.10.2011 05:38, schrieb Lex Trotman: Well done, I tested all but GeanyGDB and found some extra warnings, see [1] probably as my checking is stricter than yours. -Wall -Wextra -O2 -no-unused-parameter Plugin maintainers should look at these since they may indicate real errors, eg warning: comparison of unsigned expression = 0 is always true and various uninitialised things. My understanding was that these flags are already set on make check. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany Plugins Warnings (again)
Am 29.10.2011 05:38, schrieb Lex Trotman: Starting from a clean machine, I found many dependencies are undocumented. Many plugins required the dev package as well as the specified package, ok its sort of obvious, but it would be nice to mention as well. Other than the dev packages, unexpected and undocumented dependencies I found were: debugger - vte-dev geanypg - gpgme not just gpg update checker - webkitdev Are you just referring to documentation or to build system as well? Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [RFC] Geany Plugin Names / Lua Scripting
On 29/10/2011 06:41, Matthew Brush wrote: Hi all, Is anybody opposed to removing the geany and Geany prefix from the plugins in Geany-Plugins. I mean at least for the directory name in the source tree, README/Site, and PLUGIN_SET_INFO() name? It's always bothered me when I go into *Geany's* plugin manager and see plugin names like GeanyFooBar. Obviously the plugin is for Geany and the Geany prefix makes the plugin not ordered correctly. Same goes for the SVN/Git repository source tree directory names. +1 I think we should definitely drop Geany from all the names shown in the plugin manager, even for independently maintained plugins. GeanyLua Lua Plugins lua IIRC the PM name is 'Lua Scripting'. It doesn't really have a maintainer ATM but I am the named maintainer. Feel free to change 'GeanyLua' and/or the directory name - I would suggest 'luascript'. It doesn't allow true Lua plugins. ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [RFC] Geany Plugin Names
Le 29/10/2011 14:25, Alexander Petukhov a écrit : 29.10.2011 14:22, Lex Trotman пишет: you are right that any plugin packaged *separately* should indeed have geany in the package name but that doesn't affect directory names or plugin manager names +1 package names are packaging teams buisness, as they are already named with geany- prefix (at least *.deb ones) no changes for them except new folder names. Yeah actually under Debian the plugin packages already have the geany prefix removed, but all starts with geany-plugin-: geany-plugin-addons geany-plugin-codenav geany-plugin-doc geany-plugin-extrasel geany-plugin-gdb geany-plugin-gendoc geany-plugin-insertnum geany-plugin-latex geany-plugin-lipsum geany-plugin-lua geany-plugin-prettyprinter geany-plugin-prj geany-plugin-sendmail geany-plugin-shiftcolumn geany-plugin-spellcheck geany-plugin-treebrowser geany-plugin-updatechecker geany-plugin-vc geany-plugin-webhelper So I'd say don't worry, it's already fine here :) Cheers, Colomban ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany Plugins Warnings (again)
On 30 October 2011 02:07, Frank Lanitz fr...@frank.uvena.de wrote: Am 29.10.2011 05:38, schrieb Lex Trotman: Starting from a clean machine, I found many dependencies are undocumented. Many plugins required the dev package as well as the specified package, ok its sort of obvious, but it would be nice to mention as well. Other than the dev packages, unexpected and undocumented dependencies I found were: debugger - vte-dev geanypg - gpgme not just gpg update checker - webkitdev Are you just referring to documentation or to build system as well? They should be documented, IIUC the build script checks, thats why they fail to build. Having to search the build script to find dependencies is not good. Cheers Lex Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany Plugins Warnings (again)
On 11-10-29 05:36 PM, Lex Trotman wrote: On 30 October 2011 02:07, Frank Lanitzfr...@frank.uvena.de wrote: Am 29.10.2011 05:38, schrieb Lex Trotman: Starting from a clean machine, I found many dependencies are undocumented. Many plugins required the dev package as well as the specified package, ok its sort of obvious, but it would be nice to mention as well. Other than the dev packages, unexpected and undocumented dependencies I found were: debugger - vte-dev geanypg - gpgme not just gpg update checker - webkitdev Are you just referring to documentation or to build system as well? They should be documented, IIUC the build script checks, thats why they fail to build. Having to search the build script to find dependencies is not good. The best situation would be to have the ./configure summary print something like this: Plugins: Addons: yes [automatic] CodeNav: no [disabled by user] Debugger: no [missing `vte' package] [...] I'm not sure how much a PITA this would be to write though. Cheers, Matthew Brush ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany Plugins Warnings (again)
[..] They should be documented, IIUC the build script checks, thats why they fail to build. Having to search the build script to find dependencies is not good. The best situation would be to have the ./configure summary print something like this: Plugins: Addons: yes [automatic] CodeNav: no [disabled by user] Debugger: no [missing `vte' package] [...] I'm not sure how much a PITA this would be to write though. That of course is a better solution, but I assumed it was too hard with autofools, WAF would of course just be print I can't find ... in appropriate places. Cheers Lex ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
