\@titleaux{Unified Python Interactive Command Modules (ICM) and ICM-Players.} \bibstyle{plain} \@@addtocsec{htoc}{sec2}{-1}{\@print{Part I}\quad{}Overview{}} \@@addtocsec{htoc}{sec3}{0}{\@print{1}\quad{}Summary{}} \@@addtocsec{htoc}{sec4}{1}{\@print{1.1}\quad{}Benefits Of This Commands Oriented Approach{}} \@@addtocsec{htoc}{sec5}{1}{\@print{1.2}\quad{}Commands Are Abstract Expectations Complete{}} \@@addtocsec{htoc}{sec6}{1}{\@print{1.3}\quad{}ICM-Players: User Interfaces That Fulfill Command Expectations{}} \@@addtocsec{htoc}{sec7}{0}{\@print{2}\quad{}Precedence: Other Similar Approaches{}} \@@addtocsec{htoc}{sec8}{1}{\@print{2.1}\quad{}Automated Mapping Of Command-Line To Callables{}} \@@addtocsec{htoc}{sec9}{2}{\@print{2.1.1}\quad{}Automated Mapping Of Command-Line To Python Callables{}} \@@addtocsec{htoc}{sec10}{2}{\@print{2.1.2}\quad{}Elisp's Command and (interactive){}} \@@addtocsec{htoc}{sec11}{1}{\@print{2.2}\quad{}Automated Building Of Web Services Based On Collection Of Callables{}} \@@addtocsec{htoc}{sec12}{1}{\@print{2.3}\quad{}Generic UIs that Invoke The Command-Line Or The Web Service{}} \@@addtocsec{htoc}{sec13}{0}{\@print{3}\quad{}Specialized ICMs -- Libraries, Packages, Apps And Frameworks{}} \@@addtocsec{htoc}{sec14}{0}{\@print{4}\quad{}Related Documents{}} \citation{PLPC-180056} \citation{PLPC-180057} \citation{PLPC-180058} \@@addtocsec{htoc}{sec15}{0}{\@print{5}\quad{}About This Software And About This Document{}} \@@addtocsec{htoc}{sec16}{1}{\@print{5.1}\quad{}Part Of ByStar and BISOS{}} \@@addtocsec{htoc}{sec17}{1}{\@print{5.2}\quad{}About This Document (Presentation/Podcast){}} \@@addtocsec{htoc}{sec18}{0}{\@print{6}\quad{}Document Outline{}} \@@addtocsec{htoc}{sec19}{-1}{\@print{Part II}\quad{}Concepts And Terminology Of Unified Expectations-Complete Commands{}} \@@addtocsec{htoc}{sec20}{0}{\@print{7}\quad{}Concept Of Unified Commands{}} \@@addtocsec{htoc}{sec21}{1}{\@print{7.1}\quad{}Terminology Of Native vs Foreign, Local vs Remote, Interactive vs Non-Interactive{}} \@@addtocsec{htoc}{sec22}{1}{\@print{7.2}\quad{}Terminology Of Callables, Operations And Commands{}} \@@addtocsec{htoc}{sec23}{1}{\@print{7.3}\quad{}Commands Are Special Forms Of Operations{}} \@@addtocsec{htoc}{sec24}{1}{\@print{7.4}\quad{}Commands Are Aware Of Their Expectation -- Getopt (argc,argv) Command-Line Mapping{}} \@@addtocsec{htoc}{sec25}{1}{\@print{7.5}\quad{}Commands Can Emit Their Expectations{}} \@@addtocsec{htoc}{sec26}{1}{\@print{7.6}\quad{}Commands Are Capable Of Validating Their Expectations{}} \@@addtocsec{htoc}{sec27}{1}{\@print{7.7}\quad{}Native Invocations Vs Interactive Invocation -- Commands Can Be Invoked As Interactive Or As Non-Interactive{}} \@@addtocsec{htoc}{sec28}{0}{\@print{8}\quad{}Interactive Command Modules (ICMs) As Collections Of Related Commands{}} \@@addtocsec{htoc}{sec29}{1}{\@print{8.1}\quad{}Related And Common Parameters{}} \@@addtocsec{htoc}{sec30}{0}{\@print{9}\quad{}An Overview Of ICM Framework, Modules And Players{}} \newlabel{fig:icm-anatomy-7130}{{1}{X}} \@deflabeltype{fig:icm-anatomy-7130}{figure} \@@addtocsec{htoc}{sec31}{-1}{\@print{Part III}\quad{}The Model Of ICM-Players And ICM-Apps{}} \@@addtocsec{htoc}{sec32}{0}{\@print{10}\quad{}The Concept Of ICM-Players And ICM-Apps{}} \@@addtocsec{htoc}{sec33}{1}{\@print{10.1}\quad{}The Blee-ICM-Player (With Emacs and elisp){}} \@@addtocsec{htoc}{sec34}{1}{\@print{10.2}\quad{}Abstraction Of ICM-Apps{}} \@@addtocsec{htoc}{sec35}{-1}{\@print{Part IV}\quad{}ICM Specializations{}} \@@addtocsec{htoc}{sec36}{0}{\@print{11}\quad{}About BASH-ICMs{}} \@@addtocsec{htoc}{sec37}{0}{\@print{12}\quad{}ICM Groupings{}} \@@addtocsec{htoc}{sec38}{0}{\@print{13}\quad{}About ICM Libraries (Collections Of Reusable ICMs){}} \@@addtocsec{htoc}{sec39}{-1}{\@print{Part V}\quad{}Direct And Remote Operations -- Direct ICMs, Remote ICM Invokers, Remote ICM Performers{}} \@@addtocsec{htoc}{sec40}{0}{\@print{14}\quad{}A Unified Model For Python Invocations, Command-Line Invocations And Remote-Op Invocations{}} \@@addtocsec{htoc}{sec41}{0}{\@print{15}\quad{}Benefits And Powers Of The ICM Unified Model{}} \@@addtocsec{htoc}{sec42}{1}{\@print{15.1}\quad{}Direct Operations ICM (DO-ICM) Model{}} \@@addtocsec{htoc}{sec43}{0}{\@print{16}\quad{}An Overview Of Direct-Operations ICMs and ICM-Players{}} \newlabel{fig:icmDirectOverview}{{2}{X}} \@deflabeltype{fig:icmDirectOverview}{figure} \@@addtocsec{htoc}{sec44}{1}{\@print{16.1}\quad{}ICMs Can Be Converted To Web Services Performer{}} \@@addtocsec{htoc}{sec45}{0}{\@print{17}\quad{}An Overview Of Web Services ICM With Swagger Code Generators{}} \newlabel{fig:mmwsIcmSwagger}{{3}{X}} \@deflabeltype{fig:mmwsIcmSwagger}{figure} \@@addtocsec{htoc}{sec46}{-1}{\@print{Part VI}\quad{}Direct ICMs Command-Line Structure And Model{}} \@@addtocsec{htoc}{sec47}{0}{\@print{18}\quad{}Common Direct ICMs Command Syntax And Model -- Python And Bash Specific Features{}} \@@addtocsec{htoc}{sec48}{0}{\@print{19}\quad{}Python DO-ICM Features{}} \@@addtocsec{htoc}{sec49}{1}{\@print{19.1}\quad{}Frequently Invoked Menu Example{}} \@@addtocsec{htoc}{sec50}{1}{\@print{19.2}\quad{}Usage --help{}} \@@addtocsec{htoc}{sec51}{1}{\@print{19.3}\quad{}Logging{}} \@@addtocsec{htoc}{sec52}{1}{\@print{19.4}\quad{}Tracing And Debugging{}} \@@addtocsec{htoc}{sec53}{1}{\@print{19.5}\quad{}Plugins -- Loading Of Additional Python Code{}} \@@addtocsec{htoc}{sec54}{-1}{\@print{Part VII}\quad{}Python Native Command Invocations{}} \@@addtocsec{htoc}{sec55}{0}{\@print{20}\quad{}Python Method Invocations Of Commands{}} \@@addtocsec{htoc}{sec56}{-1}{\@print{Part VIII}\quad{}Remote Operation ICMs (RO-ICM)s -- ICM-Performers and ICM-Invokers{}} \@@addtocsec{htoc}{sec57}{0}{\@print{21}\quad{}ICM-Performers{}} \citation{PLPC-180056} \@@addtocsec{htoc}{sec58}{0}{\@print{22}\quad{}ICM-Invokers{}} \citation{PLPC-180057} \@@addtocsec{htoc}{sec59}{-1}{\@print{Part IX}\quad{}Common Foundations{}} \@@addtocsec{htoc}{sec60}{0}{\@print{23}\quad{}Wrappers And Streams{}} \@@addtocsec{htoc}{sec61}{-1}{\@print{Part X}\quad{}Overview Of The unisos.icm Package{}} \@@addtocsec{htoc}{sec62}{0}{\@print{24}\quad{}AST Analysis For class Cmnd Mapping{}} \@@addtocsec{htoc}{sec63}{-1}{\@print{Part XI}\quad{}Current Status And Next Steps{}} \@@addtocsec{htoc}{sec64}{0}{\@print{25}\quad{}Current Status{}} \@@addtocsec{htoc}{sec65}{0}{\@print{26}\quad{}Next Steps{}} \bibdata{/lcnt/outputs/all/plpcUrl,/usr/local/lib/bib/rfcs} \bibcite{PLPC-180057}{1} \bibcite{PLPC-180056}{2}