| Summary: | project options plugins - rename second CTags frontend selection | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Bernd Pol <bernd.pol> |
| Component: | CTags | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | git master | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Bernd Pol
2004-04-01 23:55:32 UTC
Well.. the idea was to either retire the old one or trash the new one, depending on reaction. It's just that I've gotten close to zero feedback in either direction so far. :) I use them both, depending on context. I like the fast jump of the older one and found the extra contextual info of the look-up quite valuable at times. Is there any technical means not to keep both of them? The "fast jump" dialog of the old one can be trivially implemented with the new backend if someone wants that. The new backend is faster, smarter and lighter on memory. There is no need for both of them. This is indeed very confusing. having 2 parts with the same description in the plugins list will confuse the user, as there is little to indicate how they differ. The RMB context menu is also cluttered by having entries from both these plugins. Are there plans to scrap ctags plugin (and add the "trivial" fast jump feature in ctags2) before the 3.1 release? KDE has been in feature freeze for several weeks now, so no, it won't happen for 3.1. The first CTAGS plugin is now gone in HEAD. This makes this BR rather moot. |