Messages - peter.s [ switch to compact view ]

Pages: prev1 ... 16 17 18 19 20 [21] 22 23 24next
General Software Discussion / Re: RightNote version 3.0.0 released
« on: January 27, 2014, 09:40 AM »
Hello, tomos,

Illic and illac - well, I once attended a German "Gymnasium", and there I got the "Big Latinum", but that was ages ago, and my tries to differenciate the two, before using those terms here, by web search, was unsuccessful; they seem to be more or less synonyms, but perhaps not in all possible cases, so I'd be thankful for an expert to inform us of the minute differences in use of both (I suppose it's a "case" thing).

As for "viable tag M", "M" being "management", in all my posts (as "IM" is "information M" and "IMS" being "IM system"), but here, I just wanted to express that of course, a VERY basic condition for ANY tagging system should be to be able to (easily) combine tags not only in applicating them, but then again, when constituting any "collections" / "items' sub-groups" by combining them. (I'm even quite sure that in SOME way or another, that might be able in RN 3, but then, I asked for HOW to do this, explicitely in outlinersw forum, and, implicitely, here, but without getting any answer, and even IF it's possible in RN, it certainly is absolutely awful.)

Re clones: There's an "official" term for it used by some author, but which I quickly forgot; my today's synonym search for "clone" didn't bring it even (but brought "mimeo" which I kind of like). Again, the real prob doesn't lie in the term, but in its application:

Most outliners, once you clone an item, will NOT distinguish anymore between the "original" and the "clones", whilst conceptually, there should be an (updatable) difference, and which I call "natural parent" and "adoptive parent" - name it as you like, but it's evident any item in a tree hierarchy should have a "natural/main context", and then, perhaps multiple, "additional contexts" - and be it only for avoidance-of-recursion reasons: btw, I mentioned this problem within a discussion of InfoQube in the outlinerswforum, where the developer of IQ, Pierre Paul Landry, suberbly said (I'm citing from memory), "IQ allows for recursion"... when in fact, recursion is a PROBLEM of IM, and which has to be avoided/contained, and certainly not a feature of IM (development illac ;-) ).

General Software Discussion / Re: RightNote version 3.0.0 released
« on: January 26, 2014, 01:27 PM »
tomos, it will - but that' not the prob.

SOME people here mix up "keywords" / additional tags within an otherwise hierarchical data repository, and a tagging system (treed or not, and where such a contextual data hierarchy simply is not there) - these are two different worlds, conceptually. All about trees and tags in the outlinersoftware forum (whilst my very first musings about the difference in paradigm was here, in a discussion with Paul, some year ago).

So some current Surfulater users might be in for a shock if they really try to switch to NextGen (and if Neville does away with the non-tag tree indeed). For the casual reader who's not willing to delve into details: Just consider that today's tagging systems do not allow for "manual sort" of the items to be found in some tag tree subtree, whilst in outliners you do manually sort siblings in order to give them more "meaning", more "accessability", in a word/term, "natural order for current context", and of course, for some 20 or 30 such siblings, and for serious / efficient work, that's an important criterion for your data repository.

And yes, for SOME, very specific data collections, tags are best (here again, details in

But tag trees try to overcome the above-mentioned endless-keywords-lists probs, but try to apply the tagging concept to stuff that had better be put into a tree, with clones. Here again, for the casual reader: Tags are best for traditional db items, i.e. stuff that sometimes is considered in "collections", to compare, but which is treated "one-by-one"; whilst "tree stuff" is data that has to be "combined" to be useful, be it combinations of items(' partial content) in order to create additional items, or be it "just" for your "consideration", and your decision-making: Here, as I have developed illic, the "manually sorted context" of the tree concept (whilst subject to necessary amendmend, I perfectly acknowledge that (keyword here: in current realizations, no variants in sorting for different contexts, let alone subgroups / easy combination variants)) should be preferred.

Current RightNote neither has clones, nor has it viable tag M, so it's not good for anything, considering its bug make it doesn't even have working Boolean search. But there certainly will be a version 4, much better than the current one.

IM is about making available anything possibly relevant info in an optimized way, and without the (academic or corporate) user going crazy in the process, i.e. complexity reduction, yes, but not to the point of leaving relevant things out; and in tagging systems for academic stuff, it's the poverty of the tool that then triggers unnecessary manual, additional work "on arrival" - dont mix up neatness and primitiveness. Join me illac, and let's see if we can find some improvement of either concept together.

General Software Discussion / Re: RightNote version 3.0.0 released
« on: January 25, 2014, 07:47 AM »
"Well, I'll add some RightNote love, to balance out the negative views."

Add love where you want if there's a chance for it to be returned to you, but don't call facts "views".


The tutorial above mentions the "autoexec section" two times, but it's very important to clearly identify that section, in order to not run into probs since AHK "allows" for very sloppy programming/scripting, i.e. it doesn't notify that when loading the script, but you'll have to work it out afterwards, often without knowing where the error might lie.

So, first you'll have the auto execute section (aes) "à proprement parler", i.e. the one you THINK is the aes.

Then you do the menus (if you have any), which also belong to the aes. (Here, it's very important to list the sub-menus BEFORE the respective parent menus, in order for AHK to "find" them. This is worth mentioning since logic and "script beauty" would ask otherwise.)

Menu example:

Menu, File Managers, add, &SC 25, speedcommander25
Menu, File Managers, add, &TC, totalcommander
; and so on

This is then the real end of the aes (or that is what you think).

Then you do the labels, example:

   run, "C:\Programme\SpeedProject\SpeedCommander 25\SpeedCommander.exe"

So this is the very first element of the "persistent" (= continuously running) part of your script
( see above:
; #Persistent : not necessary here since this script is persistent anyway because it contains hotkey assignments
) - or so you think.

Similar with key assignment and such, as for example

a:: send, Some Text to appear in the currently active applic

Now, the AHK help says,

"The Top of the Script (the Auto-execute Section)
After the script has been loaded, it begins executing at the top line, continuing until a Return, Exit, hotkey/hotstring label, or the physical end of the script is encountered (whichever comes first). This top portion of the script is referred to as the auto-execute section."

Now, with VERY careful reading, you could indeed deduct from this that the above label is NOT included in what the help file says here, but it's exactly such "you must read it oh so carefully up to the finest details" AHK "help" file style that makes the fortune of paid macro tool developers; I did never grasp that detail in two years of AHK with thousands of lines in my scripts, and it wasn't at the moment that very first program was NOT loaded automatically anymore from the little and highly recommendable tool

"Startup Control Panel 2.8 by Mike Lin"

that I became aware of my having done something wrong, since any (first or re-) loading of my main AHK script loaded that very program, again and again, anyway. I then "out-commented" that very first label, and now, the second label was executed for every script loading, and here I grasped my error...

I have to say that I had put all my key assignments BELOW my labels; if I had it done the other way round, the problem would not have arisen.

Now, you will do this, in order to avoid any such fuss:

- Have your "real" autoexecute section

- Then, have your possible menus (which you want to be available anytime)

- Then, in any case (with menus or not before), insert these lines into your script:

; End of autoexec section (return) (or any other comment to remind you)

- then, do labels, key assignments, etc., etc., in every which order you want

Some very important details ain't obvious in AHK; it's important to list them in any intro. Sorry for sharing this one so late.

General Software Discussion / Re: RightNote version 3.0.0 released
« on: January 25, 2014, 07:04 AM »
I'm not flooding the web with RightNote "hate", but since RN is described here, I'll have my word.

Switching from Ultra Recall to RightNote (as J-Mac has done) seems a little bit excentric.

Some details have been given by J-Mac above, and here's some other stuff:

Of course that false dichotomy was for fun (both elements), but Rael should do something about the issues with his very uneven prog, and fast.

Pages: prev1 ... 16 17 18 19 20 [21] 22 23 24next
Go to full version