although sending the whole tree structure after calls have been resolved (when idle) to remove the need to call the python side when only browsing without changing the structure, would be an improvement in speed (for future improvements after main features are done)
Félix On Wednesday, August 5, 2020 at 1:31:21 PM UTC-4, Edward K. Ream wrote: > > > > On Mon, Aug 3, 2020 at 6:12 PM Félix <[email protected] <javascript:>> > wrote: > > 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> >> > > Thanks for this. It's good to know that porting Leo's core to ts won't be > necessary :-) > > 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/6b373eef-888d-45b6-b3c7-2ec24037909do%40googlegroups.com.
