Task #829
let the engine handle autocomplete
Status: | New | Start: | 04/08/2013 | |
Priority: | Normal | Due date: | ||
Assigned to: | Oliver Schneider | % Done: | 0% |
|
Category: | Frontend | |||
Target version: | - | |||
Complexity: | ||||
Votes: | 0 |
Description
currently autocomplete is a frontent-gnome feature that checks the current groupchat's nicklist.
for xmpp a proper autocomplete would also check the offline roster and the jids instead of nicknames (and contact supplied nicknames and whatnot)
History
Updated by Mirco Bauer 4253 days ago
This is a bad idea as it would need a round-trip to the engine. Or do you suggest to make them happen in the background and only update when the result was received?
Updated by Oliver Schneider 4253 days ago
no that'll be very odd, you're right, roundtrip sucks.
how about giving each chat model a list of autocomplete strings then?
even better: removing this from entry:// return if we don't support the current ChatView if (!(ChatViewManager.CurrentChatView is GroupChatView) && !(ChatViewManager.CurrentChatView is PersonChatView)) { return; }
and making it ask the current view (by a virtual function in chatview) for an autocompletion
Updated by Ondrej Hošek 4203 days ago
Can we consider this solved after my rewrite of the completion infrastructure?