Hi Lars

I think you're agreeing with me and identifying a useful criterion for must-use-Worker.

But while it's not a platform problem, only a platform solution makes sense. Why should many editor projects develop similar use-worker-to-open strategies? Much better at the platform level where there might even be integration with changing project dependencies during a slow open.

    Regards

        Ed Willink

On 02/12/2014 21:07, Lars Vogel wrote:
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 <[email protected] <mailto:[email protected]>>:

    Hi

    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?

        Regards

            Ed Willink
    _______________________________________________
    cross-project-issues-dev mailing list
    [email protected]
    <mailto:[email protected]>
    To change your delivery options, retrieve your password, or
    unsubscribe from this list, visit
    https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


No virus found in this message.
Checked by AVG - www.avg.com <http://www.avg.com>
Version: 2015.0.5577 / Virus Database: 4235/8669 - Release Date: 12/02/14


_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to