Hi,
me again :-). With other Geany developers we have been discussing the future of the GeanyPrj plugin. The problem is the original developer behind it has abandoned the project so it is unmaintained now. There are several things we could do:
1. Nothing - i.e. keep it in the plugins repository unmaintained.
2. Somebody volunteers to maintain it (anyone?).
3. The plugin will be removed from the geany-plugins repository.
I would like to discuss the option (3) - while I haven't used the plugin myself much, I think the main reason people were using it was you could see multiple projects in the sidebar (and have them indexed). This is however possible with my ProjectOrganizer plugin now (see the announcement) so the question is whether there is any other use for the plugin. Otherwise I believe ProjectOrganizer offers many more features and displays the project files better so at least from my point of view (which may be biased), I think ProjectOrganizer is more or less a superset of GeanyPrj. (One exception is that with ProjectOrganizer you have to create projects explicitly while with GeanyPrj there's just kind of implicit project specification by pointing it to the directory where you keep projects).
So my preferred choice is (3) but if someone still finds the plugin useful and uses it, we can keep the plugin in the repository.
Cheers,
Jiri
On 31 January 2015 at 02:18, Jiří Techet techet@gmail.com wrote:
Hi,
me again :-). With other Geany developers we have been discussing the future of the GeanyPrj plugin. The problem is the original developer behind it has abandoned the project so it is unmaintained now. There are several things we could do:
Nothing - i.e. keep it in the plugins repository unmaintained.
Somebody volunteers to maintain it (anyone?).
The plugin will be removed from the geany-plugins repository.
I would like to discuss the option (3) - while I haven't used the plugin myself much, I think the main reason people were using it was you could see multiple projects in the sidebar (and have them indexed). This is however possible with my ProjectOrganizer plugin now (see the announcement) so the question is whether there is any other use for the plugin. Otherwise I believe ProjectOrganizer offers many more features and displays the project files better so at least from my point of view (which may be biased), I think ProjectOrganizer is more or less a superset of GeanyPrj. (One exception is that with ProjectOrganizer you have to create projects explicitly while with GeanyPrj there's just kind of implicit project specification by pointing it to the directory where you keep projects).
So my preferred choice is (3) but if someone still finds the plugin useful and uses it, we can keep the plugin in the repository.
The general principle that seems to have been established in the past is that plugins should remain until they break, or some major problem is found with them and nobody wants to fix it.
In particular does 1) GeanyPrj write any project info and 2) does Project Organiser read that info. If 1) and not 2) then its particularly important to keep it as long as its working (as well as it always did) so old project files can be used.
Cheers Lex
Cheers,
Jiri
Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
The general principle that seems to have been established in the past is that plugins should remain until they break, or some major problem is found with them and nobody wants to fix it.
It doesn't break but just thanks to the fact I spent a significant amount of time adapting it to the new tag manager API (and in not a very nice way because if I did it properly, I'd have to rewrite half of the plugin) which is the kind of work I'd like to avoid in the future. And because the code is slightly messy and hard to follow, I can't promise I didn't break anything (well, it seemed buggy already before my patches).
In particular does 1) GeanyPrj write any project info and 2) does Project Organiser read that info. If 1) and not 2) then its particularly important to keep it as long as its working (as well as it always did) so old project files can be used.
1. yes, 2. no (no plans for that).
In general I have no trouble keeping it in the plugins project, it's just when we were talking about it with Frank and Matthew, they were inclined towards removing it but suggested to ask on the mailing list which is what I just did.
Cheers, Jiri
On 30/01/15 20:49, Lex Trotman wrote:
On 31 January 2015 at 02:18, Jiří Techet techet@gmail.com wrote:
Hi,
me again :-). With other Geany developers we have been discussing the future of the GeanyPrj plugin. The problem is the original developer behind it has abandoned the project so it is unmaintained now. There are several things we could do:
Nothing - i.e. keep it in the plugins repository unmaintained.
Somebody volunteers to maintain it (anyone?).
The plugin will be removed from the geany-plugins repository.
I would like to discuss the option (3) - while I haven't used the plugin myself much, I think the main reason people were using it was you could see multiple projects in the sidebar (and have them indexed). This is however possible with my ProjectOrganizer plugin now (see the announcement) so the question is whether there is any other use for the plugin. Otherwise I believe ProjectOrganizer offers many more features and displays the project files better so at least from my point of view (which may be biased), I think ProjectOrganizer is more or less a superset of GeanyPrj. (One exception is that with ProjectOrganizer you have to create projects explicitly while with GeanyPrj there's just kind of implicit project specification by pointing it to the directory where you keep projects).
So my preferred choice is (3) but if someone still finds the plugin useful and uses it, we can keep the plugin in the repository.
The general principle that seems to have been established in the past is that plugins should remain until they break, or some major problem is found with them and nobody wants to fix it.
True in general, though in this particular case I would vote for removing geanyprj because a) as Jiří said, ProjectOrganizer have mostly the same features and more b) having one less project plugin for Geany would reduce users' confusion and so also ease support of those
My vote: option 3
Regards, Enrico
Am 31.01.2015 um 14:36 schrieb Enrico Tröger:
On 30/01/15 20:49, Lex Trotman wrote:
On 31 January 2015 at 02:18, Jiří Techet techet@gmail.com wrote:
Hi,
me again :-). With other Geany developers we have been discussing the future of the GeanyPrj plugin. The problem is the original developer behind it has abandoned the project so it is unmaintained now. There are several things we could do:
Nothing - i.e. keep it in the plugins repository unmaintained.
Somebody volunteers to maintain it (anyone?).
The plugin will be removed from the geany-plugins repository.
I would like to discuss the option (3) - while I haven't used the plugin myself much, I think the main reason people were using it was you could see multiple projects in the sidebar (and have them indexed). This is however possible with my ProjectOrganizer plugin now (see the announcement) so the question is whether there is any other use for the plugin. Otherwise I believe ProjectOrganizer offers many more features and displays the project files better so at least from my point of view (which may be biased), I think ProjectOrganizer is more or less a superset of GeanyPrj. (One exception is that with ProjectOrganizer you have to create projects explicitly while with GeanyPrj there's just kind of implicit project specification by pointing it to the directory where you keep projects).
So my preferred choice is (3) but if someone still finds the plugin useful and uses it, we can keep the plugin in the repository.
The general principle that seems to have been established in the past is that plugins should remain until they break, or some major problem is found with them and nobody wants to fix it.
True in general, though in this particular case I would vote for removing geanyprj because a) as Jiří said, ProjectOrganizer have mostly the same features and more b) having one less project plugin for Geany would reduce users' confusion and so also ease support of those
My vote: option 3
+1
(for the same reasons.)
Cheers, Frank
On 15-01-31 05:36 AM, Enrico Tröger wrote:
On 30/01/15 20:49, Lex Trotman wrote:
On 31 January 2015 at 02:18, Jiří Techet techet@gmail.com wrote:
Hi,
me again :-). With other Geany developers we have been discussing the future of the GeanyPrj plugin. The problem is the original developer behind it has abandoned the project so it is unmaintained now. There are several things we could do:
Nothing - i.e. keep it in the plugins repository unmaintained.
Somebody volunteers to maintain it (anyone?).
The plugin will be removed from the geany-plugins repository.
I would like to discuss the option (3) - while I haven't used the plugin myself much, I think the main reason people were using it was you could see multiple projects in the sidebar (and have them indexed). This is however possible with my ProjectOrganizer plugin now (see the announcement) so the question is whether there is any other use for the plugin. Otherwise I believe ProjectOrganizer offers many more features and displays the project files better so at least from my point of view (which may be biased), I think ProjectOrganizer is more or less a superset of GeanyPrj. (One exception is that with ProjectOrganizer you have to create projects explicitly while with GeanyPrj there's just kind of implicit project specification by pointing it to the directory where you keep projects).
So my preferred choice is (3) but if someone still finds the plugin useful and uses it, we can keep the plugin in the repository.
The general principle that seems to have been established in the past is that plugins should remain until they break, or some major problem is found with them and nobody wants to fix it.
True in general, though in this particular case I would vote for removing geanyprj because a) as Jiří said, ProjectOrganizer have mostly the same features and more b) having one less project plugin for Geany would reduce users' confusion and so also ease support of those
+1. Same goes for all duplicate-purpose plugins, unless there's compelling reasons that make having both really useful or they are different enough. An example might be the debugging plugins.
My vote: option 3
Same here, though I've never used it (and I use ProjectOrganizer, so I'm probably biased too).
Cheers, Matthew Brush