Choose tags via dropdown list

With a select field, how could you select multiple tags?

I think an AJAX solution would be better. The recognised tags could be auto-completed as you type.

see ajax bandbox, t:#5378

This would definitely need some JavaScript to make it usable. A drop-down with all available tags would be extremely long.

you might be able to work with with the KeywordSuggestPlugin that already has this functionality, but is missing some functionality available in TagsPlugin, see ticket #3816

This is implemented in #4201 for the KeywordSuggestPlugin.

It's great, invaluable addition to TagsPlugin, and a must-have as soon as users get accustomed to it.

So how about integration? TagsPlugin would benefit from this, and an initial, canonical set of tags might be a good thing to have for new projects too. Licenses match as well AFAIKS. Like with the date-picker addition coming in Trac 1.1dev lately, have more feature-complete plugins might be good. In fact we've discussed this a lot in the past.

What do you see against a merger? You invested quite some time to modernize the code recently, so I would certainly respect any point brought up from your side. Why KeywordSuggestPlugin should better stay on it's own, thoughts?

Replying to hasienda:

So how about integration?

Yes, I am all for it. In fact, you reminded me tonight, of outstanding issues with KeywordSuggestPlugin that I have let go on for far too long, so I have made an effort to fix those this evening.

TagsPlugin would benefit from this, and an initial, canonical set of tags might be a good thing to have for new projects too. Licenses match as well AFAIKS.

KeywordSuggestPlugin's license was clarified as 3-Clause BSD in #10037, so I also think that licenses should match.

Like with the date-picker addition coming in Trac 1.1dev lately, have more feature-complete plugins might be good. In fact we've discussed this a lot in the past.

Yes, definitely. Couple the UI functionality with the underlying plugin, and gets TagsPlugin even closer to being ready for eventual integration into the Trac core ;)

What do you see against a merger? You invested quite some time to modernize the code recently, so I would certainly respect any point brought up from your side. Why KeywordSuggestPlugin should better stay on it's own, thoughts?

No objections from me. I'd like to fix a few bugs, and then perhaps we should do a code review of KeywordSuggestPlugin. At that point, it could be moved over. In the meantime, don't hesitate to make changes directly to the KeywordSuggestPlugin codebase, whenever you see fit.

We might want to post to the trac-users mailing list the following question: Is anyone using KeywordSuggestPlugin without TagsPlugin? I suspect very few, and those few could still install the TagsPlugin egg and just enable the component that provides the keyword suggestion functionality.

Would you target this to Tags-0.7 or Tags-0.8?

Replying to rjollos:

Replying to hasienda:

So how about integration?

Yes, I am all for it. In fact, you reminded me tonight, of outstanding issues with KeywordSuggestPlugin that I have let go on for far too long, so I have made an effort to fix those this evening.

Thanks, great.

...

Would you target this to Tags-0.7 or Tags-0.8?

Definitely tags-0.8. This will be a major change, and current release stage is almost set by now.