Just got this prog and am very excited about possibilities of use.
I plan to use it to hold quite a lot of data for my (secret) application. I could end up with hundreds of text bites to pick from. The folder structure will keep things organised and my app has a natural logical structure so the order of selections are built in.
But I could have like 14 folders and within them another 12 and then within them 15 text options (radio buttons) and then below some of them another 12 or so entries.
Basically this program lets me add layers of unique detail that periodically would be reused. So I can grow my info base to meet my needs as they emerge. I simply would enter new content as needed but keep it for future reference. My database structure is a given (using a simple naming convention etc.) So it is easy for me to find the elements I need.
Sooo, how much data can I put into this program? Potentially it could grow to around 20000 discrete chunks of text. I presume at this time memory is the biggest constraint.
Feature request: be able to copy trees.
(My application has a lot of similar content, so copying portions of the tree and creating my core structure would be greatly simplified by being able to cut and paste tree elements.)
Concern about feature requests. Some of those I have seen look very demanding to create.
I would suggest focusing on improving structural efficiencies like;
one click saves,
right click on text opens corresponding tree element making it easier to find text and edit it (could use ctrl-click),
find words in text bites or in tree descriptors,
tree sort options (could be too complex at this time, though)
Basically let's aim to get the interface humming - with consideration for future development options.
The right click "refresh text now" feature is a good example of enhancing usage efficiencies and it is always something that will be used. That's the sort of feature to target at this time ... in my profoundly humble opinion!
Anyway I'm in love with this thing,
Great work Mouser,