Re: [orion-dev] HTML Outliner

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

> John J Barton <johnjbarton@xxxxxxxxxxxxxxx>

> Wouldn't it be easier and better UX to implement
this as folding 
> editor for HTML? 

Yes. I'm not a fan of code folding most of the time,
but for HTML this makes a lot of sense. Mark and I were talking about it
this morning, and were thinking the DOM provided by the outline service
could also be used to power editor folding. Different DOM attributes could
be used for cases where you don't want a fold point to match a tree in
the outline. I opened a bug for this one too:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=365769

> I think the challenge for the outliner is to detect and encode 
> common logical organizations of HTML. HTML is *not* a simple tree
to
> the dev. Some branches are much more important. Find the important
> branches and show them in the outliner.

Yes, my first attempt is a trivial mapping of the
HTML tree into the outline. McQ made the same point to me that some nodes
are more important than others. The trick is figuring out the important
stuff from the superfluous - I need to think about that more. There is
a risk if we try to be too smart with filtering we end up annoying users
- they are looking in the outline for an element they know is in the document,
but can't find it.

John