| --- | --- |
| Bugzilla Link | 349962 |
| Status | CLOSED FIXED |
| Importance | P3 normal |
| Reported | Jun 21, 2011 12:37 EDT |
| Modified | May 20, 2013 11:37 EDT |
| Version | 3.2.0 |
| Reporter | Ed Willink |
Description
The current CST/AST synchronization in the editors relies on the ability to compute identical monikers from non-identical tree structures. This is hard and flaky.
Some from of synchronisation is needed since edits replace substantial CS sections.
Although the CS objects change, the CS URIs do not so a map of CS URI to AST element can be maintained and used to drive AST refreshes. This could render monikers almost obsolete eliminating their non-trivial creation algorithm and the need to define an extensibility mechanism for it.
Just need careful design of the CST model to provide good ID attributes so that the CS URIs are relatively stable for reorderings.
| --- | --- | | Bugzilla Link | 349962 | | Status | CLOSED FIXED | | Importance | P3 normal | | Reported | Jun 21, 2011 12:37 EDT | | Modified | May 20, 2013 11:37 EDT | | Version | 3.2.0 | | Reporter | Ed Willink |
Description
The current CST/AST synchronization in the editors relies on the ability to compute identical monikers from non-identical tree structures. This is hard and flaky.
Some from of synchronisation is needed since edits replace substantial CS sections.
Although the CS objects change, the CS URIs do not so a map of CS URI to AST element can be maintained and used to drive AST refreshes. This could render monikers almost obsolete eliminating their non-trivial creation algorithm and the need to define an extensibility mechanism for it.
Just need careful design of the CST model to provide good ID attributes so that the CS URIs are relatively stable for reorderings.