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
On 29 October 2011 16:41, Matthew Brush mbrush@codebrainz.ca 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.
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
or Search Docs which describes its intended use, although it is much more general, and directory searchdocs which doesn't clash with the usual meaning of doc
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?
IIUC addons and insertnum have different maintainers
[4] Could we merge GProject and GeanyPrj or are totally different?
I bet their developers think so :)
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
==================================================================
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, as some smarty said on IRC, do you think someones going to confuse them with Emacs plugins if they don't start with Geanty
Cheers Lex
On Sat, Oct 29, 2011 at 08:09, Lex Trotman elextr@gmail.com wrote:
On 29 October 2011 16:41, Matthew Brush mbrush@codebrainz.ca 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.
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
or Search Docs which describes its intended use, although it is much more general, and directory searchdocs which doesn't clash with the usual meaning of doc
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?
IIUC addons and insertnum have different maintainers
[4] Could we merge GProject and GeanyPrj or are totally different?
I bet their developers think so :)
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
Not completely. The main difference is that gproject is an extension of Geany's projects. As such, displays just single project's files in the sidebar and shares the Geany's project settings file for its settings. geanyprj on the other hand can display multiple project's files in the sidebar and has separate project settings file for every project. This is slightly messy because you have two different projects next to each other. Originally gproject was like this too but then I decided to sacrifice the multiple project ability and play more nicely with Geany.
About the project name change - I don't care as long as someone is able to invent two different names for the project plugins ;-).
Cheers, Jiri
[...]
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
Not completely. The main difference is that gproject is an extension of Geany's projects. As such, displays just single project's files in the sidebar and shares the Geany's project settings file for its settings. geanyprj on the other hand can display multiple project's files in the sidebar and has separate project settings file for every project. This is slightly messy because you have two different projects next to each other. Originally gproject was like this too but then I decided to sacrifice the multiple project ability and play more nicely with Geany.
About the project name change - I don't care as long as someone is able to invent two different names for the project plugins ;-).
Thanks Jiri,
Based on your description, project for gproject and projects for geanyprj?
Cheers Lex
Cheers, Jiri _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Mon, 31 Oct 2011 10:20:23 +1100 Lex Trotman elextr@gmail.com wrote:
[...]
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
Not completely. The main difference is that gproject is an extension of Geany's projects. As such, displays just single project's files in the sidebar and shares the Geany's project settings file for its settings. geanyprj on the other hand can display multiple project's files in the sidebar and has separate project settings file for every project. This is slightly messy because you have two different projects next to each other. Originally gproject was like this too but then I decided to sacrifice the multiple project ability and play more nicely with Geany.
About the project name change - I don't care as long as someone is able to invent two different names for the project plugins ;-).
Thanks Jiri,
Based on your description, project for gproject and projects for geanyprj?
I disagree. Names do not differ enough. They look pretty much the same.
Cheers, Frank
Le 31/10/2011 08:37, Frank Lanitz a écrit :
On Mon, 31 Oct 2011 10:20:23 +1100 Lex Trotman elextr@gmail.com wrote:
[...]
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
Not completely. The main difference is that gproject is an extension of Geany's projects. As such, displays just single project's files in the sidebar and shares the Geany's project settings file for its settings. geanyprj on the other hand can display multiple project's files in the sidebar and has separate project settings file for every project. This is slightly messy because you have two different projects next to each other. Originally gproject was like this too but then I decided to sacrifice the multiple project ability and play more nicely with Geany.
About the project name change - I don't care as long as someone is able to invent two different names for the project plugins ;-).
Thanks Jiri,
Based on your description, project for gproject and projects for geanyprj?
I disagree. Names do not differ enough. They look pretty much the same.
I agree with Frank, the user is unlikely to see the difference, and would then be confused.
Cheers, Colomban
On Mon, 31 Oct 2011 13:47:44 +0100 Colomban Wendling lists.ban@herbesfolles.org wrote:
Le 31/10/2011 08:37, Frank Lanitz a écrit :
On Mon, 31 Oct 2011 10:20:23 +1100 Lex Trotman elextr@gmail.com wrote:
[...]
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
Not completely. The main difference is that gproject is an extension of Geany's projects. As such, displays just single project's files in the sidebar and shares the Geany's project settings file for its settings. geanyprj on the other hand can display multiple project's files in the sidebar and has separate project settings file for every project. This is slightly messy because you have two different projects next to each other. Originally gproject was like this too but then I decided to sacrifice the multiple project ability and play more nicely with Geany.
About the project name change - I don't care as long as someone is able to invent two different names for the project plugins ;-).
Thanks Jiri,
Based on your description, project for gproject and projects for geanyprj?
I disagree. Names do not differ enough. They look pretty much the same.
I agree with Frank, the user is unlikely to see the difference, and would then be confused.
BTW: The discussion here already shows the difficulty of difference. Unfortunately I don't have a golden solution to clean this up. Just merging isn't a valid option.
On 10/31/11 4:47 PM, Colomban Wendling wrote:
Le 31/10/2011 08:37, Frank Lanitz a écrit :
On Mon, 31 Oct 2011 10:20:23 +1100 Lex Trotmanelextr@gmail.com wrote:
[...]
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
Not completely. The main difference is that gproject is an extension of Geany's projects. As such, displays just single project's files in the sidebar and shares the Geany's project settings file for its settings. geanyprj on the other hand can display multiple project's files in the sidebar and has separate project settings file for every project. This is slightly messy because you have two different projects next to each other. Originally gproject was like this too but then I decided to sacrifice the multiple project ability and play more nicely with Geany.
About the project name change - I don't care as long as someone is able to invent two different names for the project plugins ;-).
Thanks Jiri,
Based on your description, project for gproject and projects for geanyprj?
I disagree. Names do not differ enough. They look pretty much the same.
I agree with Frank, the user is unlikely to see the difference, and would then be confused.
Cheers, Colomban _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
just some thoughts:
1. current gproject (if I get it right there is another branch with multiple opened project support or other features) utilizes Geany built-in project support engine, actually it shows files with project-matching extensions in a tree view, don't anybody think that it can be included in Geany and be switched off/on like files and tags list? It will eliminate the problem of renaming.
2. rename geanyprj to something "project"-free. The concern for this: there is a Project root item menu in Geany and some other places where a user is faced with built-in projects; if we'll have a plugin naming *project/prj* it will definitely make hard for a user to understand what project is he working with now.
Regards, Alexander
On Mon, Oct 31, 2011 at 00:20, Lex Trotman elextr@gmail.com wrote:
[...]
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
Not completely. The main difference is that gproject is an extension of Geany's projects. As such, displays just single project's files in the sidebar and shares the Geany's project settings file for its settings. geanyprj on the other hand can display multiple project's files in the sidebar and has separate project settings file for every project. This is slightly messy because you have two different projects next to each other. Originally gproject was like this too but then I decided to sacrifice the multiple project ability and play more nicely with Geany.
About the project name change - I don't care as long as someone is able to invent two different names for the project plugins ;-).
Thanks Jiri,
Based on your description, project for gproject and projects for geanyprj?
Like others, I think these are too similar, possibly causing confusion among users.
Another possibility could be Project/Multiproject - in fact, I still have my original sources of gproject with support of multiple projects under a github repository with this name (and this plugin is in my opinion a superset of geanyprj and could be used as a substitute of geanyprj if there's such interest).
Cheers, Jiri
On 1 November 2011 00:03, Jiří Techet techet@gmail.com wrote:
On Mon, Oct 31, 2011 at 00:20, Lex Trotman elextr@gmail.com wrote:
[...]
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
Not completely. The main difference is that gproject is an extension of Geany's projects. As such, displays just single project's files in the sidebar and shares the Geany's project settings file for its settings. geanyprj on the other hand can display multiple project's files in the sidebar and has separate project settings file for every project. This is slightly messy because you have two different projects next to each other. Originally gproject was like this too but then I decided to sacrifice the multiple project ability and play more nicely with Geany.
About the project name change - I don't care as long as someone is able to invent two different names for the project plugins ;-).
Thanks Jiri,
Based on your description, project for gproject and projects for geanyprj?
Like others, I think these are too similar, possibly causing confusion among users.
Another possibility could be Project/Multiproject - in fact, I still have my original sources of gproject with support of multiple projects under a github repository with this name (and this plugin is in my opinion a superset of geanyprj and could be used as a substitute of geanyprj if there's such interest).
Yes, or maybe project-extensions and multi-project. Although IIUC from the docs geanyprj is really one project at a time with auto swapping?
What should be done is to make some changes inside Geany, but thats OT here, see separate thread I'll start soon.
Cheers Lex
Cheers, Jiri _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Am 29.10.2011 08:09, schrieb Lex Trotman:
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
Did anyone heck if geanyprj even works (as intended)? IIUC it's largely unmaintained since a very long time. If it turns out broken it should just be dropped.
Best regards.
On Tue, Nov 1, 2011 at 09:46, Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
Am 29.10.2011 08:09, schrieb Lex Trotman:
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
Did anyone heck if geanyprj even works (as intended)? IIUC it's largely unmaintained since a very long time. If it turns out broken it should just be dropped.
Unfortunately I have to admit that GeanyPRJ is indeed quite broken and lags the whole interface when enabled on a recent build of Geany.
Does Gproject index a whole tree so that symbol and calltip autocomplete work? I can't seem to find how to enable that, so I guess not... :(
Harold
On 1 November 2011 20:04, Harold Aling geany@sait.nl wrote:
On Tue, Nov 1, 2011 at 09:46, Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
Am 29.10.2011 08:09, schrieb Lex Trotman:
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
Did anyone heck if geanyprj even works (as intended)? IIUC it's largely unmaintained since a very long time. If it turns out broken it should just be dropped.
Unfortunately I have to admit that GeanyPRJ is indeed quite broken and lags the whole interface when enabled on a recent build of Geany.
Dunno about lags, more frags, see attached traceback :)
Cheers Lex
Does Gproject index a whole tree so that symbol and calltip autocomplete work? I can't seem to find how to enable that, so I guess not... :(
Harold _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Tue, Nov 1, 2011 at 10:04, Harold Aling geany@sait.nl wrote:
On Tue, Nov 1, 2011 at 09:46, Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
Am 29.10.2011 08:09, schrieb Lex Trotman:
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
Did anyone heck if geanyprj even works (as intended)? IIUC it's largely unmaintained since a very long time. If it turns out broken it should just be dropped.
Unfortunately I have to admit that GeanyPRJ is indeed quite broken and lags the whole interface when enabled on a recent build of Geany.
Does Gproject index a whole tree so that symbol and calltip autocomplete work? I can't seem to find how to enable that, so I guess not... :(
Yes, it should. There's "generate tags for all project files" option under GProject tab of project properties for that (off by default because it's too slow for tens-of-thousand file projects I use GProject for). I hope it works alright, I haven't tested it for quite some time now but unless there was some change in Geany, it should work fine.
Cheers, Jiri
On Tue, Nov 1, 2011 at 14:05, Jiří Techet techet@gmail.com wrote:
On Tue, Nov 1, 2011 at 10:04, Harold Aling geany@sait.nl wrote:
On Tue, Nov 1, 2011 at 09:46, Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
Am 29.10.2011 08:09, schrieb Lex Trotman:
Although in my, probably poorly informed, opinion, gproject seems to encompass most of geanyprj
Did anyone heck if geanyprj even works (as intended)? IIUC it's largely unmaintained since a very long time. If it turns out broken it should just be dropped.
Unfortunately I have to admit that GeanyPRJ is indeed quite broken and lags the whole interface when enabled on a recent build of Geany.
Does Gproject index a whole tree so that symbol and calltip autocomplete work? I can't seem to find how to enable that, so I guess not... :(
Yes, it should. There's "generate tags for all project files" option under GProject tab of project properties for that (off by default because it's too slow for tens-of-thousand file projects I use GProject for). I hope it works alright, I haven't tested it for quite some time now but unless there was some change in Geany, it should work fine.
Nice!!!
Too bad it only uses 1 core instead of all 6 available; indexing takes quite a while... But it works and it seems stable!
-H-
Pleeeeeeeeease don't kill geanyprj : It's a killer plugin !!!
I've been using it for three years now and tweaked it to my needs (but still haven't found the time to make it clean and push it to the maintainer).
I couldn't live without it either at work or at home.
2011/11/1 Harold Aling geany@sait.nl
On Tue, Nov 1, 2011 at 14:05, Jiří Techet techet@gmail.com wrote:
On Tue, Nov 1, 2011 at 10:04, Harold Aling geany@sait.nl wrote:
On Tue, Nov 1, 2011 at 09:46, Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
Am 29.10.2011 08:09, schrieb Lex Trotman:
Unfortunately I have to admit that GeanyPRJ is indeed quite broken and lags the whole interface when enabled on a recent build of Geany.
What do you mean by broken ? I must admit that I don't look closely at it as far as it works as expected :)
Cheers, Johann
On Wed, Nov 2, 2011 at 15:27, Johann SAUNIER jsaunier.devel@gmail.com wrote:
Unfortunately I have to admit that GeanyPRJ is indeed quite broken and lags the whole interface when enabled on a recent build of Geany.
What do you mean by broken ? I must admit that I don't look closely at it as far as it works as expected :)
Since 'Symbol list update frequency' (aka real time symbol parsing) got in, GeanyPRJ lags every <freq> miliseconds. Geany stops taking input every cycle until the cycle is done. Secondly: saving a file takes 1-2 seconds.
Gproject is able to do the same (plus more) without any lags.
Both plugins index in a single thread, which is a pity for multi-core PC's as it takes quite a while to open a project and index all tags.
I changed from geanyprj to gproject 1-2 days ago and I'll probably never look back!
-H-
Ok, I gave Gproject a try :
Since 'Symbol list update frequency' (aka real time symbol parsing) got in, GeanyPRJ lags every <freq> miliseconds. Geany stops taking input every cycle until the cycle is done.
I haven't noticed that
Secondly: saving a file takes 1-2 seconds.
Ok, but closing Geany with Gproject is so long that Metacity gets upset and asks me if it should be forced to close ;) It was instantaneous with Geanyprj
Gproject is able to do the same (plus more) without any lags.
I agree, it seems to be more reactive
Both plugins index in a single thread, which is a pity for multi-core PC's as it takes quite a while to open a project and index all tags.
Still too long to load :(
At last, here is what the Gproject's documentation says about their differences :
- GProject is an extension of Geany's project so every Geany project is a GProject at the same time and vice versa. On the other hand, GeanyPrj project is a separate project so if you want to set build properties for a GeanyPrj project, you have to set up a second Geany project in parallel.
I don't use this facility much, but it's a good thing anyway (+1 for Gproject)
- Because GeanyPrj is a separate project management plugin, it can do some things that GProject cannot - in particular, it can manage several projects in parallel. If you need to switch between several projects, GeanyPrj might be a better option for you. Alternatively, you can open several Geany instances for different projects to work on several projects in parallel using GProject.
I often have more than one project opened in the same instance of Geany -> I will hardly get used to this (-1)
- GProject displays full tree in the sidebar while GeanyPrj displays only two-level tree (full directory name as a parent and a list of files under the directory).
I agree, Geanyprj's project view is unusable. That's one the patches I've made -> don't display the project sidebar (0)
- GProject has configurable patterns while patterns in GeanyPrj are hard-coded
That just make Geanyprj more straightforward to configure since I don't need patterns. I use C for the project itself, Python for functional testing, CMake files for the build system and interfaces are written in C++, Java and even C# -> so I have to use * as the pattern filter in Gproject (-1)
- GProject offers header/source swapping
So does "code navigation" plugin -> redundant in Gproject (0)
- GProject offers finding project files by name
Never use it because my brain is too small to remember the hundredths of file names I have in my projects :) I prefer walking the treeview to find a file (0)
In conclusion, I will try it for a few days and hope I can get used to it, and who knows ... adopt it :)
Cheers, Johann
It would be interesting to know which features you enjoy most. Perhaps gproject already offers them or can be extended.
1) Multi projects opened in a single instance of Geany
2) Setting up a new project is more straightforward :
- Download a tarball -> open a file on the root -> click menu : tools->project->create a project -> enter and you're set up to browse the source code.
- With Gproject, one have to walk the directories to set the base of the project (even if one of its files is already opened), and then set up wildcards (ok I'm a lazy person ;)
Point 2 would be a simple improvement I guess, but point 1 would expect much more dev :(
Gproject is anyway better and more polished, I admit.
Best Regards Johann
Am 02.11.2011 15:27, schrieb Johann SAUNIER:
I couldn't live without it either at work or at home.
It would be interesting to know which features you enjoy most. Perhaps gproject already offers them or can be extended.
Best regards.
[...]
What do you mean by broken ? I must admit that I don't look closely at it as far as it works as expected :)
Unfortunately compiled against Geany Git it crashes creating a new project. I don't have time (or interest I admit) to find out why, but it may need some maintenance.
Cheers Lex
Cheers, Johann _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
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
:)
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
On Fri, 28 Oct 2011 22:41:07 -0700 Matthew Brush mbrush@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".
On 29 October 2011 20:44, Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
On Fri, 28 Oct 2011 22:41:07 -0700 Matthew Brush mbrush@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
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.
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
Am Samstag, den 29.10.2011, 19:19 +0200 schrieb Colomban Wendling:
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
On Fedora it's currently geany-plugins-$pluginname, which partly looks quite ugly:
geany-plugins-addons geany-plugins-common geany-plugins-geanydoc geany-plugins-geanygdb geany-plugins-geanylatex geany-plugins-geanylua geany-plugins-geanyprj geany-plugins-geanysendmail geany-plugins-geanyvc geany-plugins-pretty-print geany-plugins-spellcheck geany-plugins-updatechecker geany-plugins-webhelper geany-plugins-codenav geany-plugins-geanyextrasel geany-plugins-geanygendoc geany-plugins-geanyinsertnum geany-plugins-geanylipsum geany-plugins-shiftcolumn geany-plugins-treebrowser
Regards, Dominic
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.
Le 29/10/2011 07:41, Matthew Brush a écrit :
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 :)
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
I'd probably better go "Lua Scripts", but that's no big deal anyway.
GeanyMacro Macro Recorder macro GeanyNumberedBookmarks Numbered Bookmarks numberedbookmarks GeanyPg Privacy Guard pg or gpg
I'd better see something less technical, like "Encryption & Signing" or something. But again, it's just a suggestion.
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
If "Zencoding" is a brand/tool name, I think it's better to not insert a space but keep the "official" typing.
Cheers, Colomban
On Fri, 28 Oct 2011 22:41:07 -0700 Matthew Brush mbrush@codebrainz.ca wrote:
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.
I don't have any strong opinion about that, but would prefer to don't push any author to rename its plugin as its up to him.
Cheers, Frank