Old Man Learns to Code

  I only vaguely remember how my so-called "second" project for learning OOP evolved into my current "Xpander" project . I sure am glad though, that I found justification for doing it as an OOP project based on the idea that I will need different instances (a.k.a. different lookup dictionaries) for different situations  (a.k.a. different " contexts " ) . [QAAA =  ( Query Asked And Answered ) =  QA3 -->  here  and here ] In other words, (Abv = iow ?)   thank goodness I'm developing it as an OOP project. The project is too complex to not be an OOP project. [QA3 = here ]   ( Link to first image on the right is here ) Let me "step back" in time a bit. I used to write work-related macros in VBA for MS Word. My two most useful, hot key activated, macros were called "DoThis" and "ConvertThis" ( made up names here ). For the first macro, I would highlight a text string that was the name of yet another VBA macro and hit a hot ...

  Initial Draft ideas for  special Xpander cases The P4=(~)P3=(`) sequence: In this case consideration, the user types the following sequence ( each square bracketed [item] is a keystroke while curly bracket is multi-keys ): [space]  {script  name} [P4] [P3] [ script type ] { optional params k-v key name } [space] To do this, the users hits Shift with the left thumb and Tilde with index to invoke  [P4]    before letting go of Shift and hitting same Tilde key for generating at least a first  [P3]   ( there can be more P3's to follow )  {script name}  is one or more characters and specifies the name of a script to be run but does not include the registered file extension of the script ( e.g. the (dot).py extension ) Before the  {script name}  there can be a null, or a space or a line feed (LFCR) ( Note: The null case occurs when there is no space to the left of the  {script name} . it starts at slice index = 0 ...