leap forward

[ofirgall]

Why can't we leap both ways?

[ggandor]

It was simpler to implement :) (I threw the original gist together literally in an hour or less.)

[CharlesChiuGit]

Hope this feature is still been working on!
I really like leap and with the power of syntax tree, leap would be more powerful!

[jul-o]

Would something like that be a good result?

I added children leaping to my local clone of the project, but I am not sure I like it too much, as there is a lot of visual clutter as a result. Maybe some sort of filtering might be good (or maybe only picking the first child recursively, along with the current node's siblings might be a good idea).

Also, I used a simple DFS to scan the children, and as a result, deep nodes of the first child are prioritized over the second child, and so on. I would rather have a BFS, but I do not really have the time to figure that ou right now.

If the project is open to PRs, and my implementation seems good to you, please let me know. It would be my pleasure to submit that feature, along with an optional parameter that enables forward leaping.

[CharlesChiuGit]

Would something like that be a good result?

I added children leaping to my local clone of the project, but I am not sure I like it too much, as there is a lot of visual clutter as a result. Maybe some sort of filtering might be good (or maybe only picking the first child recursively, along with the current node's siblings might be a good idea).

Also, I used a simple DFS to scan the children, and as a result, deep nodes of the first child are prioritized over the second child, and so on. I would rather have a BFS, but I do not really have the time to figure that ou right now.

If the project is open to PRs, and my implementation seems good to you, please let me know. It would be my pleasure to submit that feature, along with an optional parameter that enables forward leaping.

That looks cool!

[adamsitar]

so what happened to the leap forward feature?