The support should allow:
- When folds are refreshed e.g. as a result of document reparsing there should be support for matching the
expanded/collapsed state to the new folds if they are within the same position bounds in the document.
- FoldManager.removeEmptyNotify() and FM.removeDamagedNotify(): the fold provider is likely not interested in this very
much. There should be an automatic handling of these methods.
I would add:
-simpler locking: to my knowledge, adding the folds into the hierarchy currently needs to run in AWT under 3 different
"locks" (document read lock, operation.getHierarchy().lock(), operation.openTransaction())
-allow "push" model