Twoje komentarze
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)
One more hack to live with all of this meantime - just do not collapse things ; )
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)
Please read carefully my comment - it has the warning in all CAPS, i am not talking in it about reinstalling. But about just disabling/enabling. Do not uninstall - this will really delete everything.
I make some changes recently, the memory usage goes down a bit.
Yet the problem is still be real.
I feel that the complete fix is possible and i plan to investigate this problem and completely fix in a few months. Most likely this will require to implement some sort of pagination, and a brand new search. A big task.... but very needed and it's planed.
I make some changes recently, the memory usage goes down a bit.
Yet the problem is still be real.
I feel that the complete fix is possible and i plan to investigate this problem and completely fix in a few months. Most likely this will require to implement some sort of pagination, and a brand new search. A big task.... but very needed and it's planed.
I myself using it already, but just too much small nasty things need to be finished before presenting all of this to the general public, or even to the more wider circle of beta testers. There is very big differences between "just make it work" and to "make a product".
Original plan was to finally publish it this year, still hope to do so....
Original plan was to finally publish it this year, still hope to do so....
Except if the tab in TO already contain some note it will be saved automatically on close.
Also if the tab's window contain custom title, notes inside or placed anywhere above the root, then when the window will be closed from Chrome (by window close button) all its tabs will be also saved.
Also if the tab's window contain custom title, notes inside or placed anywhere above the root, then when the window will be closed from Chrome (by window close button) all its tabs will be also saved.
Currently not.
But it's planed and next version will have several different ways to do so.
But it's planed and next version will have several different ways to do so.
Something like this is planed. There will be possibility to add tags, icons, custom colors for tabs. Any such custom "something" will prevent a tab from deletion on close.
As this now works with Google Docs tabs created from the main toolbar.
well. There is already new version in a lab and it's have keyboard shortcuts.
I hope to release it this year.
but it just use arrows for moving between lines. In future maybe need to add an ability to configure shortcuts.... meantime they will be hardcoded.
Customer support service by UserEcho
Through it's not understandable how to implement this without using the bookmarks. If anybody know this it will be cool to hear.