@jenter: You really shouldn't have bothered, but thanks anyway for taking the trouble to respond to my notes about my cursory look at CN (Cinta Notes).
Please note that I was categorically
not writing a
review per se, but merely sharing my very brief note-to-self by dropping it into the
"also-ran" discussion thread set up for that purpose.
Please understand that if my initial look at CN had identified something that might have been able to help meet my peculiar requirements for a PIM/KM (Personal Information Manager/Knowledge Manager), then I would have subjected CN to a thorough evaluation and review and would probably have documented full review notes (as I have done for other software, on this forum, some of which has been done by me as a Beta tester - e.g., for NoteFrog).
For my peculiar - and possibly somewhat demanding - requirements, you can see, for example, the data types that I consider as "information" that a PIM needs to be able to manage - refer
Microsoft OneNote - how to make it your 21st century Zettelkasten PIM and the discussion that follows.
So you are quite correct where you say:
...I just think that CN is simply not what you expected it to be.
I had indeed been expecting something different - something "more". I was actually quite excited when I read in your blog that you had implemented auto-tagging, but after doing a suck-it-and-see I was left disappointed, as the tagging and auto-tagging implementation was not as flexible (as I said) as it is in CHS - which, by the way, is a CMT (Clipboard Management Tool), not even a PIM.
You say to that:
...Would be interesting to hear what functionality is missing...
- so you presumably don't perceive what I was talking about, above, so I won't bore you further.
I presumed, from its state, that the tagging/auto-tagging was still in development (which is fine). However, having trialled/tested literally hundreds of PIMS of various types, I now rapidly drop them as soon as I find on initial trial that their AS-IS core functionality isn't of interest or potential use to me at that point.
In general, I consider that the CN product - AS-IS - is arguably more properly classified as being in Beta and in any event has some way to go yet before it meets my requirements to the extent that I would value it as being worth paying $40 or more to buy a licence.
I also consider that CN probably has lots of
potential, yet to be realised.
Thus, I would, to some extent, echo
@wraith808, who writes:
...I keep my eye on it to see if it ever will become a tool that fits my workflow.
- with the difference being that I would be comparing the product functionality to my
requirements and would change my requirements if the product helped me to discover new requirements or opened up new possibilities - e.g., as MS OneNote has done. This could end up with me experimenting amd changing whatever my "workflow" happened to be. That is, I would adapt my work patterns to use the PIM tool in as optimal a manner as possible, if it had the potential to benefit me in some way by doing that - again, e.g., as I have done with MS OneNote. I should perhaps stress here that, in giving MS OneNote as an example, I don't especially
like MS OneNote and I continue to fret over its limitations/constraints, as I see them, but so far have found nothing better, so am stuck with it whilst waiting for it to be improved and as I continue looking for something better.
To this end, I shall keep reading your blog with interest - which blog, by the way, I did
not describe as "stagnant". What I had written was regarding CN, that:
"...its development is so limited and so static that it's almost become stagnant abandonware."
- as I perceived (and as I indicated) that it's real progress seemed to have been incremental and slow. I wondered whether development effort had been diverted or had lost steam, for some reason (these things happen). As for meeting my peculiar requirements, CN has some fairly good matching functionality, but it would need to be a lot better (more useful to me) before I could see myself migrating to using it.
It is a disappointment
to me that it is not - AS-IS - in a state that I could use for such a migration.
