- General
-
Ideeën
+8
Planned
Search without expanding notes
Would it be too much work to implement a search that is smart enough to sift through closed nodes? Currently I can expand all nodes and use the normal web-page search on the TO window, however expanding the nodes is sluggish and if i forget to re-close them and Chrome restarts, it's all gone, I need to go to each one and collapse it, which is extremely annoying. To me the entire "undo expanding all nodes" feature feels a little like a hack. I believe it is only useful for save as html and for search. But it seems possible to implement both of these without relying to expanding nodes or by expanding them, do the job and then collapsing them both.
I realize this would be low priority, but please consider :)
Once again, thumbs up for the good work!
I realize this would be low priority, but please consider :)
Once again, thumbs up for the good work!
Antwoord
Antwoord
Planned
Of course it's a hack.
And of course a better search is very needed and planed.
As many other things... (the tags, for example)
Still this is not in a very low priority, many other new features depends from a better native search (through the TO interface). (to make, for example, the tags to work nicely there is needed a filtered search with auto-complete, so i can assure you that native search is planed and badly wanted)
And of course a better search is very needed and planed.
As many other things... (the tags, for example)
Still this is not in a very low priority, many other new features depends from a better native search (through the TO interface). (to make, for example, the tags to work nicely there is needed a filtered search with auto-complete, so i can assure you that native search is planed and badly wanted)
One more hack to live with all of this meantime - just do not collapse things ; )
Thanks! I have tried leaving everything expanded but for some reason this really slows down operations on the TO window, not really sure why, seems like Chrome is struggling with this enormous DOM tree, which is weird.
Can i ask what processor and how much ram is on your PC?
And how much nodes do you have (this can be viewed by collapsing the root node)
I have ~25000 visible nodes now and everything works fine. But i have really powerfull 6 core PC. There was times when limit was around 9000 nodes - after that everything was started to be really slow, slow drags, slow scroll, and was completely stop operate on a 15000 nodes boundary . But after some changes this problem goes away, this is fixed for several months already, and meantime i still not experience any sluggishness with my huge tree. I think that maybe new limit is around 60 000 visible nodes, yet not tested this yet.
Unfortunately Chrome require a lot of ram to support it. There is some ideas how to fix this, and i plan to do this, but meantime i am concentrated on other areas. Yet they might help with this also, as this other areas is a separate tree documents - in which the tree can be archived, or copied. So the main tree can be started from scratch.
When there was 9000 limit i regularly just save my tree in separate HTML file (please note that you need to expand all nodes before this). And then uninstall/install extension - this deletes all data so the tree can be started from scratch. New Year is a good time to do this : )
I plan to make this exported html to be readable in future versions, so it will be possible to import them back and make them again, editable (note that actually they contain very clean HTML, and so can easily be editied using any HTML editor if this is needed, also windows from them can be dragged back to the main tree)
And how much nodes do you have (this can be viewed by collapsing the root node)
I have ~25000 visible nodes now and everything works fine. But i have really powerfull 6 core PC. There was times when limit was around 9000 nodes - after that everything was started to be really slow, slow drags, slow scroll, and was completely stop operate on a 15000 nodes boundary . But after some changes this problem goes away, this is fixed for several months already, and meantime i still not experience any sluggishness with my huge tree. I think that maybe new limit is around 60 000 visible nodes, yet not tested this yet.
Unfortunately Chrome require a lot of ram to support it. There is some ideas how to fix this, and i plan to do this, but meantime i am concentrated on other areas. Yet they might help with this also, as this other areas is a separate tree documents - in which the tree can be archived, or copied. So the main tree can be started from scratch.
When there was 9000 limit i regularly just save my tree in separate HTML file (please note that you need to expand all nodes before this). And then uninstall/install extension - this deletes all data so the tree can be started from scratch. New Year is a good time to do this : )
I plan to make this exported html to be readable in future versions, so it will be possible to import them back and make them again, editable (note that actually they contain very clean HTML, and so can easily be editied using any HTML editor if this is needed, also windows from them can be dragged back to the main tree)
Customer support service by UserEcho
And of course a better search is very needed and planed.
As many other things... (the tags, for example)
Still this is not in a very low priority, many other new features depends from a better native search (through the TO interface). (to make, for example, the tags to work nicely there is needed a filtered search with auto-complete, so i can assure you that native search is planed and badly wanted)