Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jdt-dev] Introducing a slow jdt completion computer

Great thanks Mickael,

I was thinking if i can use this
How to make use of this inside the JDT Editor. I think this is used
for Generic Editors right ? since this is part of jface text i was
assuming i might be able to use is for JDT Editor as well. What do you


On Mon, Jul 1, 2019 at 1:21 PM Mickael Istria <mistria@xxxxxxxxxx> wrote:
> Hello Gayan,
> Currently, there is a set of limitations that basically prevent JDT Editor from being able to decently deal with "slow" content-assist processors, however high is the value they ship. You probably saw this with the Chain Completion proposal ticket: it's valuable, but because it's complex, it's sometimes slow and it triggers some too long UI Freeze and sometimes reach the internal timeout in JDT, leading to the annoying pop-up.
> While several of us are working to improve that state (by introducing some non-UI Thread operations JDT could use, then make JDT completions not required to run in the UI Thread to not block users, then try to run providers in parallel for faster overall results, then try to get rid of the pop-up in favor of some more integrated UIs to better handle case of long incomplete content assist processors...), it's not an easy task to change JDT without breaking it...
> Please follow and related tickets. Bug 531061 is currently the next bug to fix in JDT before we can continue improvement to support slow content assist processors.
> Cheers,
> _______________________________________________
> jdt-dev mailing list
> jdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top