THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net


S U M M A R Y


DIARY: December 28, 2002 00:24 AM Saturday; Rod Welch

Gary needs menu option to test running SDS tasks externally.

1...Summary/Objective
2...Start Windows Apps from Withing SDS
3...Memory Solution Accomplishing SDS Tasks with Other Tools
4...0504051 Menu Call for External Test Macro


..............
Click here to comment!

CONTACTS 
0201 - Dynamic Alternatives
020101 - Mr. Garold L. Johnson

SUBJECTS
Test Menu to Run SDS Tasks Externally
Memory Run SDS Functions Externally
Development Planning for Next Generation SDS
Gary Provides Requirements for Menu Call With Options to Execute an E
Memory Solution Run SDS Tasks Externally to Avoid Memory Problems
External Tasks for SDS to Avoid Memory Problems
Requirements for Menu Call With Options to Execute an External Progra

1709 -
1709 -    ..
1710 - Summary/Objective
1711 -
171101 - Follow up ref SDS 2 0000.
171102 -
171103 - Gary requests support for testing an idea to process SDS record
171104 - functions outside of Medit that is limited to 640K.  He needs a menu
171105 - call that generates a file listing diagnostics for the current record.
171106 - Prepred menu option at the bottom of the Tools menu in an SDS record
171107 - that tries to provide what Gary seems to be asking for by generating a
171108 - file with...
171110 -      ..
171111 -     Filename on disk in c: sd 10 stufq
171112 -
171113 -        With contents...   User ID
171114 -                           Path and filename of current SDS record
171115 -                           Line number of cursor
171116 -                           Column number of cursor
171117 -                           stufg1 for returning stuff
171119 -  ..
171120 - This starts what may be a promising approach to solving some of the
171121 - memory problems.  On 021016 Gary proposed launching other progrmas
171122 - using dose /c start. ref SDS 1 UZ6G
171124 -  ..
171125 - On 021125 Gary proposed developing SDS support tools with other
171126 - software languages and calling them as external standalong software
171127 - modules, similar to Supersort. ref SDS 3 Y96M
171129 -  ..
171130 - Sent Gary email with link to this record, explaining I can send code
171131 - for this when the prior SDS update is cleared from the web server.
171132 -
171133 -     [On 021230 submitted updated SDS code with these changes.
171134 -     ref SDS 4 0001
171135 -
171136 -     [On 030103 Gary reports initial success. ref SDS 5 0001
171138 -      ..
171139 -     [On 030106 seem to have "start" working in Medit under W2K,
171140 -     ref SDS 6 EZ3N, and identify applications. ref SDS 6 FO5J
171142 -      ..
171143 -     [On 031022 developed feature using Start to launch other programs
171144 -     for opening files listed in SDS records. ref SDS 7 0001
171145 -
171146 -
171147 -
171148 -
171150 -  ..
1712 -
1713 -
1714 - Progress
1715 -
171501 - Start Windows Apps from Withing SDS
171502 - Memory Solution Accomplishing SDS Tasks with Other Tools
171503 -
171504 - Received ref DRT 1 0001 from Gary requesting support for developing
171505 - new features in SDS using external tools and importing work product in
171506 - a way that reduces demand on SDS memory.
171508 -  ..
171509 - This follows up Gary's letter on 021016 that proposed launching other
171510 - progrmas using dose /c start. ref SDS 1 UZ6G
171511 -
171512 -     [On 030103 Gary reports initial success. ref SDS 5 0001
171514 -  ..
171515 - If we can solve problem of using Windows Start command from within
171516 - Medit under W2K, reported on 021016, ref SDS 1 U1PT, a possible
171517 - initial solution might be to call another session of SDS to do things
171518 - like reports and subject index calls, because these often require a
171519 - lot of RAM and otherwise fragment RAM for the current session.  If we
171520 - could run an op in another memory session and then create links and or
171521 - incorporate content back to the current session, that would be a big
171522 - step.
171524 -      ..
171525 -     [On 030106 seem to have "start" working in Medit under W2K,
171526 -     ref SDS 6 EZ3N, and identify applications. ref SDS 6 FO5J
171528 -  ..
171529 - Specifically, Gary says today...
171530 -
171531 -   1.  I have verified that MSDOS can execute a Windows console program
171532 -       (with a long name) created by Delphi. ref DRT 1 0001
171534 -        ..
171535 -   2.  The test reads from c:\sd\10\stufq and writes to cd\sd\10\stufr
171536 -       and displays a window. This shows that the Console program can
171537 -       access windows visual functions! ref DRT 1 JL5N
171539 -        ..
171540 -   3.  The batch file used for the test waits for the test program to
171541 -       close and writes the output file. ref DRT 1 2M6I
171543 -        ..
171544 -       It can read command line arguments. ref DRT 1 MM6M
171546 -        ..
171547 -   4.  The upshot is that if you can construct a menu entry for testing
171548 -       and a macro, I can begin to test the possibility of getting SDS
171549 -       to use external features for its functions. ref DRT 1 VM7F
171551 -        ..
171552 -   5.  I would like to have:
171554 -      ..
171555 -     [On 021230 submitted updated SDS code with these changes.
171556 -     ref SDS 4 0001
171558 -             ..
171559 -         •  A Test entry on some SDS menu.
171560 -            ref DRT 1 OM7K
171562 -             ..
171563 -         •  Tied to a macro that executes a test program (named
171564 -            whatever) with the following arguments:
171565 -
171566 -            1.  The current User ID, ref DRT 1 4N8F
171568 -                 ..
171569 -            2.  The path to the current SDS record (in the working dir
171570 -                if not prior day). ref DRT 1 6N8K
171572 -                 ..
171573 -            3.  The cursor row in the file (not screen)
171575 -                 ..
171576 -            4.  The cursor column in the file (not screen)
171578 -                 ..
171579 -            5.  The name of a file to use for returning results
171581 -             ..
171582 -         •  The macro then displays the first line of the response file
171583 -            as a message. ref DRT 1 QQ9J
171585 -        ..
171586 -       That should allow me to test access to records for any use.
171588 -        ..
171589 -       By changing program names or adding parameters, we should be
171590 -       able to test all sorts of interactions before we consider
171591 -       replacing some of the SDS functions with external programs.
171592 -       ref DRT 1 GR9M
171594 -        ..
171595 -       The attached zip file has the test routines. Unzip into
171596 -       c:\sd\10, and run txt_bat.bat.
171597 -
171599 -  ..
171600 - Gary continues...
171601 -
171602 -       The batch file:
171603 -
171604 -         •  Replaces stufr with a line and types the file.
171605 -            ref DRT 1 1S4M
171607 -             ..
171608 -         •  Copies stuffs to stufq so that the test always uses the
171609 -            same file.
171611 -             ..
171612 -         •  Runs tst_long.exe which:
171613 -
171614 -            1.  Reads 10 lines from stufq, ref DRT 1 ZQ52
171616 -                 ..
171617 -            2.  Displays a window with the lines and wait for the
171618 -                button to be clicked. ref DRT 1 ZQ5L
171620 -                 ..
171621 -            3.  Write a line and the program parameters to stufr
171623 -             ..
171624 -         •  Types the stufr file to show that the batch file waited for
171625 -            the program to finish. ref DRT 1 NS6I
171627 -        ..
171628 -       This *should* be a start on the next step.
171630 -      ..
171631 -     [On 021230 submitted updated SDS code with these changes.
171632 -     ref SDS 4 0001
171633 -
171634 -
171636 -  ..
1717 -
1718 -
1719 - Analysis
1720 -
172001 - We can create a menu choice to execute a macro file that puts the
172002 - params Gary requests in point 5, per above. ref SDS 0 6J4A
172004 -  ..
172005 - Should these stack them up one line at a time so they are in a
172006 - consistent location?
172008 -  ..
172009 - Tried creating 02201 and put it in bottom of Tools menu.
172011 -  ..
172012 - Line 30, ref OF 1 604M, in 02201
172013 -
172014 -    markcur 10
172015 -
172016 -       Identify current record.
172017 -
172018 -    gfname
172019 -    macro 1180
172020 -
172021 -       Capture filename for the path and save to globals.
172022 -
172024 -  ..
172025 - Line 40, ref OF 1 X15K, in 02201
172026 -
172027 -    linecnt 1 0
172028 -    setcur 2 0
172029 -    addcnt 2 1
172030 -    setgbl 1 @1
172031 -    setgbl 2 @2
172032 -
172033 -       Get line number for the row, and get cursor column, and
172034 -       increment it for actual postion in the file.
172036 -        ..
172037 -       Make them globals to enter in target file.
172039 -  ..
172040 - Line 50, ref OF 1 PPSS, in 02201
172041 -
172042 -    e stufq
172043 -    macro 301
172044 -    macro 150
172045 -
172046 -       Open temp storage to pass parameters, and delete anything that
172047 -       might be left over from a prior pass.  Call standard profile to
172048 -       assign functions that we don't really need, but may come in
172049 -       handy, and adds lines.
172051 -     ..
172052 -    macro 92
172053 -    up
172054 -
172055 -       Enter User ID, we probably don't need this because it can be
172056 -       extracted from the filename, but will put it per request.
172058 -     ..
172059 -    loc_cur 0 1
172060 -    setcnt 86 1
172061 -    macro 1181
172062 -
172063 -       Enter path to current record, including filename.
172065 -     ..
172066 -    loc_cur 0 1
172067 -    getgbl 1 1
172068 -    getgbl 2 2
172069 -    inscnt 1 0
172070 -    up
172071 -    loc_cur 0 1
172072 -    inscnt 2 0
172073 -
172074 -       Enter row (line) and column of cursor position.
172075 -
172076 -
172078 -  ..
172079 - Line 80, ref OF 1 0563, in 02201
172080 -
172081 -    ins_text!stufg1!
172082 -    up
172083 -    immed 999d
172084 -
172085 -       Provide a return filename in local directory c: sd 10
172087 -     ..
172088 -    save
172089 -    ecur 10
172090 -    purge c:\sd\03\02201
172091 -
172092 -       Save the file to disk return to SDS and close the menu call.
172093 -
172094 -
172096 -  ..
172097 - 0504051  Menu Call for External Test Macro
172098 -
172099 - Line 320, ref OF 2 G63F, -label oxhrJ in 0504051 about 110 lines
172100 - below
172101 -
172102 -    ins_text "º External Test Macro for Start        º"
172103 -    loc_cur 0 80
172104 -    ins_text " @c:\sd\03\02201  "
172105 -    rel_cur 1 -56
172106 -
172107 -       Call external test macro per above.
172108 -
172109 -
172110 -
172111 -
172112 -
172113 -
172114 -
172115 -
172116 -
172117 -
172118 -
172119 -
172120 -
172121 -
172122 -
172123 -
172124 -
172125 -
172126 -
172127 -
172128 -
172129 -
1722 -
Distribution. . . . See "CONTACTS"