Using OutliningNodeDefinition with non-nested nodes

Hi Martin,

There isn't a way to have us determine implicit node ends, however you can do it yourself.

If you look at our CodeOutliningRangeBased QuickStart, if you are doing like what we show in the JavascriptOutliningSource constructor, when you encounter a new node start or end that should also implicitly end another previous node, you can insert the previous node from its start offset through to the offset you are at, before starting to track the next node's ranges.

This document has n't a parser, well not directly that is. Its an include file. So my idea was to implement outlining based on lexer data, rather than using parse data with ASTs from other documents.

Well, i will try your solution maybe later (needs to cache AST trees, and parsing of other document on textchanges)

Hi Martin,

Based on the syntax you have above, I would think you could just parse it as-is and wouldn't need ASTs from other document.

:) If that would be the complete syntax yes. However the syntax is quite complex. But maybe a simple lookalike parser will do.

Fixed using a IParser (which doesnt parse;)) but hooks on the outlining. To keep it simple only implemented basic nested outlining (blocks can contain blocks e.g.), but for outlining purposes is that enough i think.