56
General Software Discussion / Re: RightNote Revisited / Review (in lieu of a RN forum)
« on: June 05, 2014, 06:21 AM »
Greetings, donleone.
Wow! If ever some application had some ace ambassador, that was RN getting you as its spokesman! Of course, I'm musing about how you got together all this info, with no forum and a very low-key helpfile (to say the least); if by chance you're the developer himself, well, kudos, you defend your program brilliantly, and, very obviously, you are right to do so, since from your explanations, it's much, much better than it appears.
Thank you so much for your multiple (and obviously very needed) clarifications, and I fully acknowledge, from what you say, that the tagging limitations do not appear to be of relevance anymore, since more than 500 identical tabs would to be cut into several "siblings tags" anyway. I uphold my observation that the tag gui is catastrophic, though, not only visually, but from the "how to search for tag combos" pov, too; I deduct from what you explain that the tag feature does NOT have some specific search in-built, but that, if several items are tagged "tag_a" and "tag_b", you simply do a regular quick search for "tag_a tag_b", like for would do for every search term present in the text.
Thank you so much for your explanations on the "pages" concept, so "pages" is simply a synonym for "tree", several such trees, each with its specific tree format, being possible in ONE db file; in fact, that reminds me not only my developments of "several trees in one db" in the outlinerswforum over there, some months ago (and the big difference of RN trees vs. the concept I explained there, see below), but especially, several both UR and MI users asking for different sub-tree FORMATS within the same db = very big tree, in their respective outlining applic; doing several trees within the same db instead obviously is a viable and much more elegant solution to this appearantly rather common prob.
Now I understand better why RN, which (as I see now) belongs to the "big shots" in its category, has no clones yet, since in the db structure you describe, clones would be more difficult to implement than in the traditional "1 tree - 1 db" setup, and that seems to be the difference between RN today and my developments over there:
If I understand well what you say, one item, in RN of today, can be in one tree, but not in several trees (yet), no more than it can be placed in different sub-trees of the same tree (of course, since that would be cloning), and thus, whilst several trees are possible, in RN, within the same db, it is not possible (yet) to create "contextual variants" (or whatever you might call those structures), i.e. to have items in more than one context, and by this building independent data repositories but accessing (and then SELECTING and REGROUPING) already-available "raw" data.
( cf. my thread https://www.donationcoder.com/forum/index.php?topic=37993.0 here )
So what we have got, is:
- UR and MI (and others) which offer clones (i.e. multiple instances of (= internally references to) an identical item, and which is a "big step in the right direction"
- RN which offers multiple trees within the same db,
and it hits everyone in the eye that the perfect outliner would combine these two features (and it is evident that you need complete cloning first to realize this, i.e. any clone must "update" any possible children/grandchildren which may be added either anywhere, or, even more elaborate but perfect = the ultimate solution, which might have been added in some "source", some "primal" tree, but not, or just by way of dialogs popping up (= not by general option once and for all!), within trees that should be considered not as "partial descendants" from the original ones, but as "partial siblings"; here again, my example of legal dispositions, in some "source", and then different "cases" where you will need diffent subsets of these dispositions only; technically, such subsets could be realized the following way, even "cross-wise", replicating from one such "sibling tree" to another one:
Any cloning does a "complete cloning", i.e. sets a value in the respective dataset to any new descendants being replicated "here" (i.e. any clone would have its own settings), but then, those specific clone settings, individual for every one clone, would maintain additional "deletion" info, causing that any "add-on", elsewhere, of that replicated sub-structure, to an item here in THIS instance of that sub-structure, will NOT be added here, IF the sub-parent item in question has been deleted here OR has been "marked as sterile" (while having been left there to contain alternative descendants): Thus, "updating" of any clone wherever would be automatic, but would encounter individual barriers in each replication, and this "infertile items" would not only not be updated for new descendants added elsewhere, but their own descendants would not be replicated in the "sibling" replicating structures:
Thus, an ideal cloning concept would clone "over" different trees, AND allow for these clones becoming perfectly individualized over time (as would do primitive copies), AND get "allowed updates" (= context changes, item add-ons, item deletes), but just within the limits individually set: Just imagine "identical" twin siblings which are then heavily changed, "individualized" by their respective lifes and in different towns, even countries, and new family contexts, but which often attend the same familiy meetings (and get identical new info there, often replacing old info instead), but which often one sibling wants to incorporate into his knowledge, whilst the other sibling refuses such "new info", be them add-ons, be them corrections, and having "voids", "blank spaces" in his mind instead, or having new info of his own (instead, or additionally), but which he won't share with his sibling, and even if they grow very much apart, there is always the possibility that one day, they both get their respective share of the inheritance of their parents when those die - ok, in my IM concept they wouldn't die, in normal circumstances, but up to then, the above allegory is quite faithful, and even for the "death"/deletion of "original parents", some "taking over" proceedings should be implemented (and processed from within dialog windows, individually).
Sorry for diverting, but as we see, RN is just short of becoming something really great, at the condition that further development will be based upon its current strengths, so some guidance could not do any harm. ;-)
As for the multiple tagging features in RN, as said I don't grasp them yet at this moment, and some better help file descriptions, AND some remodeling of the taggingrelated part of the gui would both be more than welcome. ;-)
Wow! If ever some application had some ace ambassador, that was RN getting you as its spokesman! Of course, I'm musing about how you got together all this info, with no forum and a very low-key helpfile (to say the least); if by chance you're the developer himself, well, kudos, you defend your program brilliantly, and, very obviously, you are right to do so, since from your explanations, it's much, much better than it appears.
Thank you so much for your multiple (and obviously very needed) clarifications, and I fully acknowledge, from what you say, that the tagging limitations do not appear to be of relevance anymore, since more than 500 identical tabs would to be cut into several "siblings tags" anyway. I uphold my observation that the tag gui is catastrophic, though, not only visually, but from the "how to search for tag combos" pov, too; I deduct from what you explain that the tag feature does NOT have some specific search in-built, but that, if several items are tagged "tag_a" and "tag_b", you simply do a regular quick search for "tag_a tag_b", like for would do for every search term present in the text.
Thank you so much for your explanations on the "pages" concept, so "pages" is simply a synonym for "tree", several such trees, each with its specific tree format, being possible in ONE db file; in fact, that reminds me not only my developments of "several trees in one db" in the outlinerswforum over there, some months ago (and the big difference of RN trees vs. the concept I explained there, see below), but especially, several both UR and MI users asking for different sub-tree FORMATS within the same db = very big tree, in their respective outlining applic; doing several trees within the same db instead obviously is a viable and much more elegant solution to this appearantly rather common prob.
Now I understand better why RN, which (as I see now) belongs to the "big shots" in its category, has no clones yet, since in the db structure you describe, clones would be more difficult to implement than in the traditional "1 tree - 1 db" setup, and that seems to be the difference between RN today and my developments over there:
If I understand well what you say, one item, in RN of today, can be in one tree, but not in several trees (yet), no more than it can be placed in different sub-trees of the same tree (of course, since that would be cloning), and thus, whilst several trees are possible, in RN, within the same db, it is not possible (yet) to create "contextual variants" (or whatever you might call those structures), i.e. to have items in more than one context, and by this building independent data repositories but accessing (and then SELECTING and REGROUPING) already-available "raw" data.
( cf. my thread https://www.donationcoder.com/forum/index.php?topic=37993.0 here )
So what we have got, is:
- UR and MI (and others) which offer clones (i.e. multiple instances of (= internally references to) an identical item, and which is a "big step in the right direction"
- RN which offers multiple trees within the same db,
and it hits everyone in the eye that the perfect outliner would combine these two features (and it is evident that you need complete cloning first to realize this, i.e. any clone must "update" any possible children/grandchildren which may be added either anywhere, or, even more elaborate but perfect = the ultimate solution, which might have been added in some "source", some "primal" tree, but not, or just by way of dialogs popping up (= not by general option once and for all!), within trees that should be considered not as "partial descendants" from the original ones, but as "partial siblings"; here again, my example of legal dispositions, in some "source", and then different "cases" where you will need diffent subsets of these dispositions only; technically, such subsets could be realized the following way, even "cross-wise", replicating from one such "sibling tree" to another one:
Any cloning does a "complete cloning", i.e. sets a value in the respective dataset to any new descendants being replicated "here" (i.e. any clone would have its own settings), but then, those specific clone settings, individual for every one clone, would maintain additional "deletion" info, causing that any "add-on", elsewhere, of that replicated sub-structure, to an item here in THIS instance of that sub-structure, will NOT be added here, IF the sub-parent item in question has been deleted here OR has been "marked as sterile" (while having been left there to contain alternative descendants): Thus, "updating" of any clone wherever would be automatic, but would encounter individual barriers in each replication, and this "infertile items" would not only not be updated for new descendants added elsewhere, but their own descendants would not be replicated in the "sibling" replicating structures:
Thus, an ideal cloning concept would clone "over" different trees, AND allow for these clones becoming perfectly individualized over time (as would do primitive copies), AND get "allowed updates" (= context changes, item add-ons, item deletes), but just within the limits individually set: Just imagine "identical" twin siblings which are then heavily changed, "individualized" by their respective lifes and in different towns, even countries, and new family contexts, but which often attend the same familiy meetings (and get identical new info there, often replacing old info instead), but which often one sibling wants to incorporate into his knowledge, whilst the other sibling refuses such "new info", be them add-ons, be them corrections, and having "voids", "blank spaces" in his mind instead, or having new info of his own (instead, or additionally), but which he won't share with his sibling, and even if they grow very much apart, there is always the possibility that one day, they both get their respective share of the inheritance of their parents when those die - ok, in my IM concept they wouldn't die, in normal circumstances, but up to then, the above allegory is quite faithful, and even for the "death"/deletion of "original parents", some "taking over" proceedings should be implemented (and processed from within dialog windows, individually).
Sorry for diverting, but as we see, RN is just short of becoming something really great, at the condition that further development will be based upon its current strengths, so some guidance could not do any harm. ;-)
As for the multiple tagging features in RN, as said I don't grasp them yet at this moment, and some better help file descriptions, AND some remodeling of the taggingrelated part of the gui would both be more than welcome. ;-)