Your comments
It would seem that I am jumping to false conclusions. I am sorry.
The first thing I noticed after the update was when I right-clicked in the Tabs Outliner window I did not see the "Save As..." option. This is something that I use regularly to move nodes between computers.
And then I saw this message at the top of the screen:
"Context menu, clipboard operations and keyboard shortcuts are not working in the Free Mode. To enable them you need to Upgrade to the Paid Mode.Below is a preview of what will be available after the Upgrade."
Based on the above message I assumed that the options listed below the message were disabled. I just tried to type Ctrl-S and I was able to save all my nodes as an HTML file. That is a relief. Sorry for the false alarm on that point.
How is the above referenced message that says, "Context menu, clipboard operations and keyboard shortcuts are not working" meant to be interpreted? Because it sounds to me like the features referenced by the message are non-functional.
Anyway, I am super glad to see that the development of Tabs Outliner is continuing! Is there a way for me to send you money without creating a Chromium-based profile?
I will post information about any issues I encounter with the new version.
Again, please accept my sincere apology for jumping to false conclusions. As I look more closely it does appear (as you mentioned) that there are some addition features included in this new version. Thank you!
Sincerely,
david
--
P.S.
I think you should consider deleting this thread since the title states something incorrect about Tabs Outliner and I wouldn't want anyone who doesn't read this thread to think that there are "BIG Problems" with Tabs Outliner.
When I first started using Tabs Outliner I wished it was able to remember tab history. In fact, I even held off moving my workflow to TO while I thoroughly investigated other solutions that would provide the benefits of TO and tab history.
Eventually the benefits of TO (even without tab history) compelled me to jump whole hog into using it. And now after using TO daily for quite some time, I suspect tab history (as it's typically been implemented) is something that we actually don't want.
The way I worked around not having tab history was to open every link that was interesting to me in a new node (tab). This provides for an ability to search through the history of all tabs whenever a node search is executed. Additionally it allows one to visually browse tab history -- including being able to browse tab history in context because new tabs can automatically open as child nodes. I don't know of any tab tool in any browser that can provide both of these features.
So basically you can have tab history in TO (and more) by simply changing how you open new tabs.
One of the cons of implementing tab history (as it's typically been implemented -- not searchable and not visually browsable) is that it will result in dead text. This is diametrically opposite of what we want. Search this page http://brainstormsw.com/outliner/competitor-comparison/ for "dead text" to understand that phrase.
Additionally, tab history will likely bloat the TO database for many people (saving undesired parts of tab history). This is a bad thing. We want TO to run as lean and thus as quick as possible.
Yes, we want a tab history. What we ideally want is a curated tab history. And we want a curated tab history without the effort that goes into curating. Since curating won't happen with zero effort, we want to find the sweet spot where we are applying the minimal effort possible that results in a curated tab history with much of the chaff winnowed.
Winnowing much of the chaff in a tab's history *is* possible with minimal effort with TO. I have achieved this. And this is coming from a tab hoarder who abhors spending time organizing and categorizing data. Someone who used to use Firefox with sometimes 800 tabs open and thousands of *unnamed/uncategorised* saved Session Manager sessions. Now I spend just a small amount of time quickly labeling, moving, and sometimes deleting nodes and node branches *before* saving the nodes. The result has been better searchability and visibility into my tab history than I've ever had with any other browser configuration.
I do imagine people have other workflows that might work better for them (probably the people who are better organizers than I am). To each their own. If tab history does make it into TO please make it possible to disable this feature.
Thanks,
david
Eventually the benefits of TO (even without tab history) compelled me to jump whole hog into using it. And now after using TO daily for quite some time, I suspect tab history (as it's typically been implemented) is something that we actually don't want.
The way I worked around not having tab history was to open every link that was interesting to me in a new node (tab). This provides for an ability to search through the history of all tabs whenever a node search is executed. Additionally it allows one to visually browse tab history -- including being able to browse tab history in context because new tabs can automatically open as child nodes. I don't know of any tab tool in any browser that can provide both of these features.
So basically you can have tab history in TO (and more) by simply changing how you open new tabs.
One of the cons of implementing tab history (as it's typically been implemented -- not searchable and not visually browsable) is that it will result in dead text. This is diametrically opposite of what we want. Search this page http://brainstormsw.com/outliner/competitor-comparison/ for "dead text" to understand that phrase.
Additionally, tab history will likely bloat the TO database for many people (saving undesired parts of tab history). This is a bad thing. We want TO to run as lean and thus as quick as possible.
Yes, we want a tab history. What we ideally want is a curated tab history. And we want a curated tab history without the effort that goes into curating. Since curating won't happen with zero effort, we want to find the sweet spot where we are applying the minimal effort possible that results in a curated tab history with much of the chaff winnowed.
Winnowing much of the chaff in a tab's history *is* possible with minimal effort with TO. I have achieved this. And this is coming from a tab hoarder who abhors spending time organizing and categorizing data. Someone who used to use Firefox with sometimes 800 tabs open and thousands of *unnamed/uncategorised* saved Session Manager sessions. Now I spend just a small amount of time quickly labeling, moving, and sometimes deleting nodes and node branches *before* saving the nodes. The result has been better searchability and visibility into my tab history than I've ever had with any other browser configuration.
I do imagine people have other workflows that might work better for them (probably the people who are better organizers than I am). To each their own. If tab history does make it into TO please make it possible to disable this feature.
Thanks,
david
That might work. Wouldn't know until I tried it.
I do think I might like your color choices (seems easier on my eyes) more than the current ones.
Ideally all fonts and colors would be user-configurable.
I do think I might like your color choices (seems easier on my eyes) more than the current ones.
Ideally all fonts and colors would be user-configurable.
Derin, thanks for taking a stab at improving the UI.
I'm not sure the thicker font would be an improvement for me. A high percentage of my nodes intentionally have long descriptions. A thicker font would likely mean less node text is displayed and I would be seeing less information (undesirable).
Also, truth be told, I think Vladyslav's limited development time is best spent in other areas. I sure wish this was a cooperative project on GitHub! Then anyone could work on the part of Tabs Outliner they were motivated to work on.
I'm not sure the thicker font would be an improvement for me. A high percentage of my nodes intentionally have long descriptions. A thicker font would likely mean less node text is displayed and I would be seeing less information (undesirable).
Also, truth be told, I think Vladyslav's limited development time is best spent in other areas. I sure wish this was a cooperative project on GitHub! Then anyone could work on the part of Tabs Outliner they were motivated to work on.
Vladyslav.volovyk wrote:
> 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).
That seems quite undesirable. Are you no longer planning on making TO capable of accessing multiple databases simultaneously?
> 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.
Sounds promising. How much financial support would you need to be able to devote more time to TO?
> It really will be much simple for you to just start from scratch.
Actually, it will be more complex for me.
> 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.
Unfortunately that is no substitute for a single database or multiple live databases integrated into the same interface.
Thank you very much for Tabs Outliner.
> 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).
That seems quite undesirable. Are you no longer planning on making TO capable of accessing multiple databases simultaneously?
> 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.
Sounds promising. How much financial support would you need to be able to devote more time to TO?
> It really will be much simple for you to just start from scratch.
Actually, it will be more complex for me.
> 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.
Unfortunately that is no substitute for a single database or multiple live databases integrated into the same interface.
Thank you very much for Tabs Outliner.
Vladyslav.volovyk wrote:
> If accidentally deleted such items can be always restored
> from Chrome by the "Recent closed windows/tabs list".
While this works for tab nodes it does not work for note nodes as far as I can tell. I have lost notes in the past when I accidentally clicked the delete icon.
Does the undo feature you are working on include being able to undo deleted note nodes?
Thank you very much for Tabs Outliner!
> If accidentally deleted such items can be always restored
> from Chrome by the "Recent closed windows/tabs list".
While this works for tab nodes it does not work for note nodes as far as I can tell. I have lost notes in the past when I accidentally clicked the delete icon.
Does the undo feature you are working on include being able to undo deleted note nodes?
Thank you very much for Tabs Outliner!
I've created a new thread to continue this conversation here: http://tabsoutliner.userecho.com/topic/468688-how-to-fund-tabs-outliners-development/
Vladyslav,
Sorry I haven't replied yet. I've had a few unexpected things come up. I'm planning on replying with ideas for generating money this coming week. BTW, do you have an idea of how much money you need to generate with Tabs Outliner in order to be able to continue with the development work? The answer to this question might help in creating a viable strategy to generate money.
-- david
Sorry I haven't replied yet. I've had a few unexpected things come up. I'm planning on replying with ideas for generating money this coming week. BTW, do you have an idea of how much money you need to generate with Tabs Outliner in order to be able to continue with the development work? The answer to this question might help in creating a viable strategy to generate money.
-- david
This single extension has resulted in me making Iron (Chrome) my primary browser. Firefox customized with more extensions than I recall, while still in use for things that I can't accomplish with Chrome, is almost never used for normal day-to-day browsing.
I never thought I would switch from Firefox.
I never thought I would switch from Firefox.
Customer support service by UserEcho
Vladyslav,
I want to give you money, and I am completely unwilling to create even a fake google account.
I very much dislike that Google, IMHO, violates people's privacy non-consensually. And I don't want to validate that business model by participating in it in any way, even anonymously.
What is your bitcoin address?
Thanks again for creating Tabs Outliner.
-- david