Hi Edward, Good question, as I'm currently re-writing a good part of the updating and refreshing logic since the addition of the 'direct tree browsing' mode. (ar-jan's great suggestion) ...and the ad-hoc addition of the documents panel, and the @ buttons panel - which refresh at every single simple operations ... (meaning the last 2-3 weeks of features additions now require some refactoring to make everything only refresh when really needed, which i'm working on)
I'm also making sure to remove all unneeded python functions that can be replaced by leoCommand concept you brought forward. About your question, the thing is for that specific point you're mentioning : vscode's tree only know about whats visible. so unfolding and going right would require a call anyways. So not that big of an improvements. (The big improvement will be that it wont refresh everything after i'm done with the current issues.) But the tree-navigation and node moving will also be greatly improved when I implement the 'murmurhash' ids to replace the actual 'incremented number' ids, which for refreshes of every nodes when the tree refreshes. (issue #74) <https://github.com/boltex/leointeg/issues/74> Félix p.s. I'm thinking a 'real compiled extension' release is not to far ahead, maybe still a good 2-3 months of work overall to orchestrate and finish all the remaining issues :) On Monday, August 3, 2020 at 12:13:03 PM UTC-4, Edward K. Ream wrote: > > Would writing methods like p.moveToNext in typescript help leoInteg in any > way? > > Would doing so help reduce traffic with leobridgeserver.py? > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/b86ccf1b-46f6-4b45-9d9e-cc049e42060bo%40googlegroups.com.
