Open nilshoerrmann opened 13 years ago
I was just thinking the same thing today! I spend much time every time searching for the correct node, and with a lot of data this can sometimes be a bit tricky.
It would be nice if the nodes were collapsed by default or something, or collapse all/expand all buttons.
Neat idea, the concern of course is ensuring it works with large(r) datasets than usual, if either of you would like to implement it as a proof of concept we can test it with varying XML sizes to see how viable it is :)
Would the collapsed status persist between page loads? Would be immensely helpful if so.
The old devkits used to use JS to do the syntax highlighting and it made them really slow. So if any extra JS is added to this page it's got to perform really well.
This would be a great feature. I'm always scrolling down past /data/params
to see my data sources, so being able to collapse this across refreshes would be neat.
What about containing each node's content in a containing element, and using JavaScript only to add/remove a class or data-attribute to it, with CSS handling whether it's shown or hidden? CSS transitions could be used to smoothly fold up or down.
It would be nice if this devkit added an option to collapse XML nodes. It should be possible to hide and show child nodes using .nextUntil().