Hi,
I've just pushed quite a few changes to my GProject plugin (unfortunately in a single commit because I was making these changes while working on the tag manager and it was too painful to rebase multiple commits every time I changed the Geany API). If there are some problems, please let me know.
Before announcing the changes on the users mailing list, there's one more change I'd like to make - make the plugin name a little more descriptive so it's easier to find by users who are looking for a plugin which displays a file tree in the sidebar. For this reason I'd like to rename the plugin to ProjectTree.
Please let me know if you have a better idea for the plugin name or if you think renaming the plugin isn't a good idea.
Thanks,
Jiri
Am 11.12.2014 21:32:22, schrieb Jiří Techet:
Hi,
I've just pushed quite a few changes to my GProject plugin (unfortunately in a single commit because I was making these changes while working on the tag manager and it was too painful to rebase multiple commits every time I changed the Geany API). If there are some problems, please let me know.
Before announcing the changes on the users mailing list, there's one more change I'd like to make - make the plugin name a little more descriptive so it's easier to find by users who are looking for a plugin which displays a file tree in the sidebar. For this reason I'd like to rename the plugin to ProjectTree.
Please let me know if you have a better idea for the plugin name or if you think renaming the plugin isn't a good idea.
It will need some extra work (instalaltion and building files, plugins.geany.org, users inforamtion ...) but I think to make it more clear to the user it's worth doing it.
Cheers, Frank
Unfortunately, the suggested new name conflicts with my previously announced plugin : geany-project-tree
https://github.com/mdda/geany-project-tree
(on the list here : http://comments.gmane.org/gmane.editors.geany.devel/8851)
I chose the name because my plugin shows the selected files within the project as a tree of your own devising. Whereas, from what I saw, your plugin shows the project's files according to the existing directory layout (i.e. the 'tree' being defined by the file-system). Which is why I felt that 'Project-Tree' was appropriate for mine.
YMMV Martin :-)
On 12 December 2014 at 04:32, Jiří Techet techet@gmail.com wrote:
Hi,
I've just pushed quite a few changes to my GProject plugin (unfortunately in a single commit because I was making these changes while working on the tag manager and it was too painful to rebase multiple commits every time I changed the Geany API). If there are some problems, please let me know.
Before announcing the changes on the users mailing list, there's one more change I'd like to make - make the plugin name a little more descriptive so it's easier to find by users who are looking for a plugin which displays a file tree in the sidebar. For this reason I'd like to rename the plugin to ProjectTree.
Please let me know if you have a better idea for the plugin name or if you think renaming the plugin isn't a good idea.
Thanks,
Jiri _______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
On 14-12-11 12:32 PM, Jiří Techet wrote:
Hi,
I've just pushed quite a few changes to my GProject plugin (unfortunately in a single commit because I was making these changes while working on the tag manager and it was too painful to rebase multiple commits every time I changed the Geany API). If there are some problems, please let me know.
Before announcing the changes on the users mailing list, there's one more change I'd like to make - make the plugin name a little more descriptive so it's easier to find by users who are looking for a plugin which displays a file tree in the sidebar. For this reason I'd like to rename the plugin to ProjectTree.
Please let me know if you have a better idea for the plugin name or if you think renaming the plugin isn't a good idea.
"ProjectTree" only covers one part of the plugin. What about FilteredFileListAndAutoTagger? Or something like that, but shorter :)
P.S. I found a bug in GProject where it keeps adding more and more tabs to the project dialog. If the GitHub Issues gets turned on for Geany-Plugins I'll open a bug report, if it's not fixed yet.
Cheers, Matthew Brush
If people really love the name "ProjectTree" for the former GProject, I'd be happy enough (but for the pain of renaming a bunch of stuff...) to rename my plugin "ProjectOrganizer" or something that doesn't conflict.
All the Best Martin :-)
PS: Before I set off to write my own plugin, I looked carefully at the options out there, and GProject certainly does a lot. However, it didn't meet my basic requirement of being able to organize project files according to purpose - it (and others) wanted to always diagram files according to the file system layout (which is normally semi-predefined by a build tool).
On 14 December 2014 at 04:19, Matthew Brush mbrush@codebrainz.ca wrote:
On 14-12-11 12:32 PM, Jiří Techet wrote:
Hi,
I've just pushed quite a few changes to my GProject plugin (unfortunately in a single commit because I was making these changes while working on the tag manager and it was too painful to rebase multiple commits every time I changed the Geany API). If there are some problems, please let me know.
Before announcing the changes on the users mailing list, there's one more change I'd like to make - make the plugin name a little more descriptive so it's easier to find by users who are looking for a plugin which displays a file tree in the sidebar. For this reason I'd like to rename the plugin to ProjectTree.
Please let me know if you have a better idea for the plugin name or if you think renaming the plugin isn't a good idea.
"ProjectTree" only covers one part of the plugin. What about FilteredFileListAndAutoTagger? Or something like that, but shorter :)
P.S. I found a bug in GProject where it keeps adding more and more tabs to the project dialog. If the GitHub Issues gets turned on for Geany-Plugins I'll open a bug report, if it's not fixed yet.
Cheers, Matthew Brush
Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
On Sun, Dec 14, 2014 at 4:00 PM, Martin Andrews Martin.Andrews@redcatlabs.com wrote:
If people really love the name "ProjectTree" for the former GProject, I'd be happy enough (but for the pain of renaming a bunch of stuff...) to rename my plugin "ProjectOrganizer" or something that doesn't conflict.
ProjectOrganizer could actually be a nice name for my plugin as well since the plugin does some other things (so organizer = FilteredProjectFileTreeAndFileIndexerAndFileSearcherAndHeaderSourceSwapper). So if you like the ProjectTree name better for your plugin, just use it and I can go with the other.
All the Best Martin :-)
PS: Before I set off to write my own plugin, I looked carefully at the options out there, and GProject certainly does a lot. However, it didn't meet my basic requirement of being able to organize project files according to purpose - it (and others) wanted to always diagram files according to the file system layout (which is normally semi-predefined by a build tool).
This is something I did on purpose in my plugin because I made it primarily for big projects and it's almost impossible to manually organize thousands of files (and keep them organized while other team members add/remove/rename files). In my opinion, the file system is where the files should be organized properly and there shouldn't be any need to map one file tree to another.
Cheers,
Jiri
ProjectOrganizer could actually be a nice name for my plugin as well
Great!
This is something I did on purpose in my plugin because I made it primarily for big projects and it's almost impossible to manually organize thousands of files (and keep them organized while other team members add/remove/rename files). In my opinion, the file system is where the files should be organized properly and there shouldn't be any need to map one file tree to another.
Understood - and your plugin is super-helpful with big projects, etc.
I typically work on smaller codebases, and want to 'get oriented' as quickly as possible (and many of the files won't get put into the custom hierarchy - it's there for clarification, not completeness). For instance the project-tree plugin page itself (https://github.com/mdda/geany-project-tree) shows how the file directories effectively remove oneself a little from the purpose of the different files, whereas the 'collected' version makes more sense (to me at least).
Of course, there's nothing to stop someone from installing them both : Which is why I don't plan on expanding functionality much (though the hooks are there in the Python code if someone does want to).
All the Best - Martin :-)
On Mon, Dec 15, 2014 at 7:44 AM, Martin Andrews Martin.Andrews@redcatlabs.com wrote:
ProjectOrganizer could actually be a nice name for my plugin as well
Great!
Good, I have created a pull request here renaming GProject to ProjectOrganizer:
https://github.com/geany/geany-plugins/pull/178
I hope I changed all that should have been changed and haven't forgotten about anything. Regarding *.po files, I just replaced the old paths in them with new paths using sed but haven't done anything else. Is it OK to merge or do you see any problems?
Cheers,
Jiri
On 17/12/14 16:09, Jiří Techet wrote:
On Mon, Dec 15, 2014 at 7:44 AM, Martin Andrews Martin.Andrews@redcatlabs.com wrote:
ProjectOrganizer could actually be a nice name for my plugin as well
Great!
Good, I have created a pull request here renaming GProject to ProjectOrganizer:
https://github.com/geany/geany-plugins/pull/178
I hope I changed all that should have been changed and haven't forgotten about anything. Regarding *.po files, I just replaced the old paths in them with new paths using sed but haven't done anything else. Is it OK to merge or do you see any problems?
To me it looks fine after a quick look. I'd say just merge it and let's check what's missing then, if anything at all.
Regards, Enrico
On Thu, Dec 18, 2014 at 12:22 PM, Enrico Tröger enrico.troeger@uvena.de wrote:
On 17/12/14 16:09, Jiří Techet wrote:
On Mon, Dec 15, 2014 at 7:44 AM, Martin Andrews Martin.Andrews@redcatlabs.com wrote:
ProjectOrganizer could actually be a nice name for my plugin as well
Great!
Good, I have created a pull request here renaming GProject to ProjectOrganizer:
https://github.com/geany/geany-plugins/pull/178
I hope I changed all that should have been changed and haven't forgotten about anything. Regarding *.po files, I just replaced the old paths in them with new paths using sed but haven't done anything else. Is it OK to merge or do you see any problems?
To me it looks fine after a quick look. I'd say just merge it and let's check what's missing then, if anything at all.
Done, thanks.
Jiri
On Sat, Dec 13, 2014 at 9:19 PM, Matthew Brush mbrush@codebrainz.ca wrote:
On 14-12-11 12:32 PM, Jiří Techet wrote:
Hi,
I've just pushed quite a few changes to my GProject plugin (unfortunately in a single commit because I was making these changes while working on the tag manager and it was too painful to rebase multiple commits every time I changed the Geany API). If there are some problems, please let me know.
Before announcing the changes on the users mailing list, there's one more change I'd like to make - make the plugin name a little more descriptive so it's easier to find by users who are looking for a plugin which displays a file tree in the sidebar. For this reason I'd like to rename the plugin to ProjectTree.
Please let me know if you have a better idea for the plugin name or if you think renaming the plugin isn't a good idea.
"ProjectTree" only covers one part of the plugin. What about FilteredFileListAndAutoTagger? Or something like that, but shorter :)
Yeah, sounds really great :-). In fact, it should be FilteredProjectFileTreeAndFileIndexerAndFileSearcherAndHeaderSourceSwapper, in short FPFTAFIAFSAHSS - unfortunately the first is absurdly long and the second isn't very descriptive.
I wanted to use the ProjectTree name because one of the questions at Prague Linux Days was something like "I like Geany but I miss the project file tree in the sidebar" and my plugin is an answer to this (I think quite common) question.
P.S. I found a bug in GProject where it keeps adding more and more tabs to the project dialog. If the GitHub Issues gets turned on for Geany-Plugins I'll open a bug report, if it's not fixed yet.
Ugh, I'm not aware of this one - how can I reproduce it? (Maybe try the latest version from geany-plugins first, there have been many changes.)
Cheers,
Jiri