Future of code assistants

[Sven Brauch]

Hey all,

with an eye on RR 126763, how do you imagine the future of the
assistants? To me it is clear after some testing that the current way of
having it in the completion, while having some some advantages, will not
work out well just like that.

There's two options: either revert to the old behaviour; or keep it in
the completion list, but that requires solving of some issues from my
point of view: having it open up interfers with navigation through the
code, so one would need to think of a way to prevent that. Also to allow
sensible automatic invocation, I think we'd need to decouple opening the
upper completion popup from the normal completion list (which would make
sense for other situations like calltips anyways btw).

Maybe another idea to making it work with the completion list would be
to make the upper part of the completion popup not keyboard-navigatable
(and thus not catching the up/down arrow keys), and instead using the
Alt+1 etc. shortcuts if applicable. The keyboard navigation in this
widget never made sense for the use cases so far anyways.

What do you think? I'm actually quite undecided. At least for rename and
add include, I like the workflow with the completion list better than
the old workflow though.

Greetings,
Sven

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160118/360feb70/attachment.sig>