Your comments
Thanks for your review. Interesting points. Hope future versions will improve on some of them. for example some of the mentioned by you issues is a nasty result of the bug with incorrect crashed windows detection on Chrome close, and of course it's planned to be fixed.
fa 10 anys
I think that the simplest solution is just to stop using the one click to activate option.
Note that changing sources inside the Chrome profile might lead to automatic reinstall (actually Chrome will first disable it and will ask if you want to repair it) of the extension and the bigger problem - clearing of all its local data, as the sources is signed and regularly checked by Chrome for changes (to prevent their updates by wireses i think).
Anyway, thanks for pointing me about this problem of the "one click" users. I think i will support some workaround for this use case in future
Note that changing sources inside the Chrome profile might lead to automatic reinstall (actually Chrome will first disable it and will ask if you want to repair it) of the extension and the bigger problem - clearing of all its local data, as the sources is signed and regularly checked by Chrome for changes (to prevent their updates by wireses i think).
Anyway, thanks for pointing me about this problem of the "one click" users. I think i will support some workaround for this use case in future
> Are you no longer planning on making TO capable of accessing multiple databases simultaneously?
The solution actually not in using several databases. TO with gigantic trees have several problems.
The solution actually not in using several databases. TO with gigantic trees have several problems.
One of them is RAM usage - this will be partially fixed soon (in a months I hope).
Another problem is long, often several seconds, saves, which block UI. This is also planned to be fixed and I even have the working prototype for more than a year already, but it's was a big rewrite and I will no be able to publish it very soon, without maybe additional several months of work.
> How much financial support would you need to be able to devote more time to TO?
Several thousand, to be able completely concentrate on it.
I hope soon to release paid version which will have some additional features for a small fee (keyboard support, online backup, some other small features). I hope that this will enable me to devote more time to this project. But things is going not as quick is I want...
If you can provide any loan (on parole : ) or want to invest in this project, please contact me directly through vladyslav.volovyk@gmail.com
Best Regards
Vladyslav
PS Regularly create backups through Ctrl-S is a good idea anyway, Chrome local storage is not very reliable. Also configuring an automatic backup of the whole Chrome profile and keeping its several older version is also very good idea (or at least the File System folder inside the Chrome profile directory)
> How much financial support would you need to be able to devote more time to TO?
Several thousand, to be able completely concentrate on it.
I hope soon to release paid version which will have some additional features for a small fee (keyboard support, online backup, some other small features). I hope that this will enable me to devote more time to this project. But things is going not as quick is I want...
If you can provide any loan (on parole : ) or want to invest in this project, please contact me directly through vladyslav.volovyk@gmail.com
Best Regards
Vladyslav
PS Regularly create backups through Ctrl-S is a good idea anyway, Chrome local storage is not very reliable. Also configuring an automatic backup of the whole Chrome profile and keeping its several older version is also very good idea (or at least the File System folder inside the Chrome profile directory)
I really recommend to just archive your tree in HTML (Ctrl-S, save as complete HTML) and start from scratch (by uninstalling and then install Tabs Outliner again).
I myself have 60 000 nodes and I understand you concerns. New version with much better performance and memory usage is on the way, but I cannot promise any exact date when it will be released. It really will be much simple for you to just start from scratch.
Note that the exported HTML is also editable by any external HTML editor. It's also possible that I will support importing such files back, in the new version.
I myself have 60 000 nodes and I understand you concerns. New version with much better performance and memory usage is on the way, but I cannot promise any exact date when it will be released. It really will be much simple for you to just start from scratch.
Note that the exported HTML is also editable by any external HTML editor. It's also possible that I will support importing such files back, in the new version.
I found that most likely such behaviour is a result of the fact that your Chrome have the "Enable fast tab/window close" flag enabled.
Go to
chrome://flags/
and disable the
Enable fast tab/window close
option
(it's not standard anyway and is under development)
Please report if this true/helps
Go to
chrome://flags/
and disable the
Enable fast tab/window close
option
(it's not standard anyway and is under development)
Please report if this true/helps
BTW, why just not leave all your old data in the GDoc - it's editable, and links can be opened : ))
I am now work on a Import\Export\Autobackup through Google Drive. Plan to release it in 2 months. Until that seems that procedure you describe will be an only option for you.
It will be possible though to write some extension that will allow more automatic import through drag & drop. Same way as i support drag and drop of hierarchies from files saved through Ctrl-S. But i dont plan to do so. You can try it yourself if you have the programming knowledge - check how data is transferred during Drag&Drop from such files, you need of course an a real OS for that.....
.
I am now work on a Import\Export\Autobackup through Google Drive. Plan to release it in 2 months. Until that seems that procedure you describe will be an only option for you.
It will be possible though to write some extension that will allow more automatic import through drag & drop. Same way as i support drag and drop of hierarchies from files saved through Ctrl-S. But i dont plan to do so. You can try it yourself if you have the programming knowledge - check how data is transferred during Drag&Drop from such files, you need of course an a real OS for that.....
.
And what happen on Chrome OS when you press Ctrl-S?
A small tip meantime - deleting items row by row is not very productive anyway. Much more handy just drag & drop all items you plan to delete in a pile on some node, than collapse the pile and delete all in one click.
Nodes can be quickly collapsed by clicking circle in the hovering menu.
But of course need something done about the fact that cursor does not reappear on a next row.
Actually i am sure that this is already fixed already in my private version of Tabs Outliner, which i am not released meantime, as it's have keyboard cursor management and cursor never disappear, even if the current node or hierarchy where it is placed deleted.
But it's unclear meantime when i will be ready to release this version. It will be most likely will be published as separate project, as it's have a lot of changes. Notification will be given in the original Tabs Outliner.
Yet i will check, maybe it can be easily fixed in the current version also.
Nodes can be quickly collapsed by clicking circle in the hovering menu.
But of course need something done about the fact that cursor does not reappear on a next row.
Actually i am sure that this is already fixed already in my private version of Tabs Outliner, which i am not released meantime, as it's have keyboard cursor management and cursor never disappear, even if the current node or hierarchy where it is placed deleted.
But it's unclear meantime when i will be ready to release this version. It will be most likely will be published as separate project, as it's have a lot of changes. Notification will be given in the original Tabs Outliner.
Yet i will check, maybe it can be easily fixed in the current version also.
Thanks for a screencast, very informative.
Unfortunately, looks like it's a Chrome or system issue.
I think from Chrome extension it's cannot be done much to react on mouse on inactive window, on windows & Ubuntu it's work ok.
As for not reapearing cursor (hovering menu) - i will investigate and most likely fix this issue. Agree, it's a pain.
Thanks again for a screen-cast, i see this problem for a first time.
Unfortunately, looks like it's a Chrome or system issue.
I think from Chrome extension it's cannot be done much to react on mouse on inactive window, on windows & Ubuntu it's work ok.
As for not reapearing cursor (hovering menu) - i will investigate and most likely fix this issue. Agree, it's a pain.
Thanks again for a screen-cast, i see this problem for a first time.
Customer support service by UserEcho
