Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Open Editor timeouts

Hi Ed,

If an editor accesses the Internet I think it should use a worker thread to get the editor content. I have not seen reports for platform editor freezes, AFAIK the platform editors do not access the Internet for their content. 

I would think this is not a platform problem, an editor is IMHO responsible to get his data model and I'm unware of special support in the platform for asynchronous editor loading.

Best regards, Lars

2014-12-01 18:34 GMT+01:00 Ed Willink <ed@xxxxxxxxxxxxx>:

The Code Recommender's reports highlight a cross-project phenomenon that is difficult to allocate to a particular project.

If an editor is slow to open, the current opening strategy on the UI thread can lead to a UI freeze.

For platform editors, the 2s timeout may just be adequate, so, not a platform problem.

Bug 453590 causes the basic Ecore Editor to timeout if a user gives a stupid URI causing Internet failures.

By the time we get to Xtext and worse still my OCL Xtext editors, there is ample scope for opening to take more than 2 seconds.

I'm getting irritated by the number of UI freeeze duplicates and could attempt to override the platform/Xtext editor strategies to put up a loading welcome page while a worker thread does the necessary.

But I feel that provision of such a strategy is really a platform job rather than my job three levels of abstraction further on.

Is anyone else seeing this as a problem?


        Ed Willink
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top