Eclipse Community Forums: Eclipse Platform » Incremental reconciling strategy synchronization

Help

Home

Home » Eclipse Projects » Eclipse Platform » Incremental reconciling strategy synchronization

Show: Today's Messages :: Show Polls :: Message Navigator

Incremental reconciling strategy synchronization [message #492085]

Sun, 18 October 2009 07:21

Christoph HÃ¶ger
Messages: 40
Registered: July 2009

Member

Hi,

I am working on my incremental lexer that should be run from an
incremental reconciler. The basic stuff just works, but the
synchronization is a real problem.
I never can be sure that the IDocument content is valid (that is, it
maps to the dirty region event) Is there any way to stop eclipse from
updating that content when I am lexing it?

regards

Christoph

Report message to a moderator

Re: Incremental reconciling strategy synchronization [message #492159 is a reply to message #492085]

Mon, 19 October 2009 04:00

Dani Megert
Messages: 3801
Registered: July 2009

Senior Member

Christoph Höger wrote:
> Hi,
>
> I am working on my incremental lexer that should be run from an
> incremental reconciler. The basic stuff just works, but the
> synchronization is a real problem.
> I never can be sure that the IDocument content is valid (that is, it
> maps to the dirty region event) Is there any way to stop eclipse from
> updating that content when I am lexing it?
No, and you shouldn't do this. The user should always be able to
continue typing. The reconciler automatically aborts the current run if
the document gets changed.

Dani
>
> regards
>
> Christoph

Report message to a moderator

Re: Incremental reconciling strategy synchronization [message #492418 is a reply to message #492085]

Tue, 20 October 2009 08:05

Ravi
Messages: 27
Registered: July 2009

Junior Member

It is highly undesirable to disable document updates because you have some work to do. Incremental reconciliation is tricky to implement and i suggest you try and look for alternate solutions unless its completely unavoidable. The reconciliation has a progress monitor which you can use to stop doing work for previous document updates if a fresh one arrives. However when you start incremental reconciliation for the fresh document change, you should ensure that you are working on the all the unprocessed document changes till then.

A better idea is to enqueue document changes in a queue and work on it -- thread pool concept.

Hope this helps,
Ravi.

Report message to a moderator

Previous Topic:	'branding' at run time
Next Topic:	How to disable renaming of a project programmatically.

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Jun 20 04:25:12 EDT 2013