What outliners should be able to do (on inherent features and interoparability)

Posted by Fredy
Aug 12, 2012 at 11:03 AM

What about an internal macro function?

So, it becomes evident that what’s needed, in the very first place, when you “hold your basic program simple”, is an internal macro function. Here, we’ve got another variety of the “what, that’s all after 30 years of personal computing?” phenomenon: 30 years ago (or perhaps “only” 27, 26 years ago), many programs came invariably WITH such internal macro functions, whilst MOST programs today, cheap or expensive, come WITHOUT such a function: This appears to be extremely crazy on first sight, but refer to what I said on the subject of the “users accept almost everything today” vs. “developers think, given the users they got, that it’s good enough as it is” interdependence, and you see clearly now: Developers just decided that given the fact that most users are debrained (? décervelés), the programming of a macro functionality was pearls before sw***.

On the other hand, MS is one of the very few devopers that supply their sw’s with such macro functionality, and see what their market share is!

Thus, not only that “alternative view” (see above and below) seems to be an absolute MUST-HAVE of any acceptable outliner, but built-in macro-functionality is another one - admit you’d never thought of that, in this context! On a traditional “wish list” for such programs, it would have been on 30th or 60th position, “for specialists”, when in fact, such functionality, in the very first place, could do away with many such wishes on such a wish list, from position (about) 5 to (sign for endless): just a little bit of scripting, and your wish is fulfilled! (And the above-mentioned problems with external scripts would not occur with internal ones if - IF - the macro function is programmed as it should be.)