THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
S U M M A R Y
DIARY: December 22, 2007 01:58 AM Saturday;
Received letter from Morris planning Windows SDS application.
2...Essential Features Priorities Requested for Program Development
3...Features Essential for Better Management Accomplished by SDS Functions
4...Efficient Usability Function Keys Complement SDS Menus Apply Features
5...Brain Power Balance Both Hands Efficient Usability
6...Responsive Efficient Usability Prominent Feature SDS
7...Function Keys Complement SDS Menus Efficient Usability Key SDS Feature
8...Prototype Demonstration SDS Aids Learning Knowledge Management
9...Knowledege Management Learn by Doing Use Prototype Demonstration
10...Plan Perform Report SDS Features Augment Intelligence Use Cases
11...People Process Time Use Cases for Chronlogy Context Connection
12...Features SDS Integrate Time Information People Document Management
13...Functions SDS Features Integrate Complementary Synergy Keyboard Mouse
....2...SDS Records Applied to Schedule and Diary
..........Reports & Memos
....3...Contact Management of People and Organizations
........Contact Index features...
..........Open record.................................... F2
..........Reports.................................... Alt F9
........Contact Records features
....4...Subject Index for Context Management
....5...File Access Directory Management
14...Doxygen Code Documentation Progress
15...Code Documentation Progress Considering Doxygen
16...Expanding SDS Records Stored on Disk Proven Solution
17...Large Collection Files SDS Manages Like Building Uses Nuts and Bolts
18...Memory Combining Work Product with Tool System Problematic
19...Multiple Views Applies MFC for Generic Object Model Like Microsoft
........Fixed Column Text Simpler Design Limits Fonts Formatting
20...Essential Features Reflect Experience Using SDS
........SDS Granular Structure of Time Addressability Indexing
........1...Records keyed by User and Timestamp, with internal outline
........5...Subject Index outline. Some way of referencing multiple
........6...Document system for dealing with external documents
........7...Contacts just because SDS has them. They can be a simple
....5...== Key Mappings == [Function Keys Provide Extensibility]
....6...== Storage Mechanism and Structure == Records Files on Disk
21...Wheels Reinvent for Productivity Saving Lives Time money
...10...== Don't Reinvent Unless There Is Benefit ==
Click here to comment!
1...What is the difference between links and "hyperlinks"?
2...What is a "hypertext" editor relative to SDS that constructs links as
3...Is there an example of MVC that indicates application to SDS?
4...What is the difference between "clean documentation" and SDS
Features Priorities Requested for SDS Function Keys Menus Program De
3203 - ..
3204 - Summary/Objective
320501 - Follow up ref SDS 32 0000, ref SDS 31 0000.
320503 - Morris requested a list of SDS features. ref SDS 0 PX5H Gary
320504 - explained SDS applies the granular structure of time with granular
320505 - addressability and indexing to control low levels of organiic
320506 - structure in the microcosm of complex daily work. ref SDS 0 PA6P The
320507 - most essential feature integrates functions that augment intelligence.
320508 - ref SDS 0 3V4H Efficient usability enables practical implementation
320509 - of Knowledge Management. ref SDS 0 FO94 Gary's response to Morris
320510 - calls for user definable profiles mapping keys. ref SDS 0 PA5P A
320511 - comprehensive list of functions supports SDS features. ref SDS 0 6P9J
320512 - Morris was able to find Doxygen for code documentation suggested by
320513 - Gary. ref SDS 0 TM5V Need review of SDS support for engineering
320514 - managemen. ref SDS 0 Y29I Design approach of everything in memory
320515 - under review along with handing records as a collection of files.
320516 - ref SDS 0 TM6U Morris planning support for "multiple Views" using
320517 - Microsoft MFC technology. ref SDS 0 TN3S Support by other software
320518 - operating on SDS work produce may be limited using XML. ref SDS 0 TN5P
320519 - Gary proposes not reinventing the wheels of Knowledge Management.
320520 - Technology and design changes should strengthen timely, accurate
320521 - intelligence support, and rely on proven methods that cannot be
320522 - readily improved. ref SDS 0 PB7P
320527 - ..
3208 - Progress
320901 - Essential Features Priorities Requested for Program Development
320902 - Features Essential for Better Management Accomplished by SDS Functions
320903 - Efficient Usability Function Keys Complement SDS Menus Apply Features
320905 - Received ref DRT 1 0001 dated 071220 from Morris responding to Gary's
320906 - letter dated 071219. ref SDS 32 X15I
320908 - ..
320909 - Morris letter used a subject of "open standards and open source,"
320910 - which is not related to the purpose of the letter, and followed the
320911 - practice in Gary's letter. ref SDS 32 X06H
320913 - ..
320914 - Morris says on 071220...
320916 - 1. Do we have a list of the essential features. When I ask Rod
320917 - for a feature list, with priorities, he wants to show me the
320918 - program. We should discuss the function key ideas. They can
320919 - be implemented, but tend to interact with the standard windows
320920 - accelerator keys. (Windows gets a first grab on the
320921 - keystrokes, and then passes the ones that aren't "Hot" down to
320922 - the application. I cannot tell the difference between a menu
320923 - mouse activation, or a hot key activation). ref DRT 1 0001
320925 - ..
320926 - Seeing the program run and experience using the program provides
320927 - understanding of essential features, reported on 070907. ref SDS 26
320928 - VG3T and further in the same record. ref SDS 26 1998
320930 - [On 080206 lack of experience with SDS causes long
320931 - experience using Microsoft and other information software
320932 - to form paradigms that inocculate people against being
320933 - convinced about requirements for flexible structure that
320934 - enables Knowledge Management.
320936 - ..
320937 - SDS record "features" were discussed during the meeting with Morris on
320938 - 071212, ref SDS 31 KO4F, citing a case study on 070126 explaining
320939 - complexity of features that causes people to give up. ref SDS 21 QH8L
320940 - Flexible structure using granularity of time and line numbers was
320941 - discussed at that time. ref SDS 31 RE5M A few days ago on 071220 Jack
320942 - Park submitted a letter demonstrating utility of line numbers in SDS
320943 - for precision access. ref SDS 33 RH6L
320945 - ..
320946 - Challenges maintaining focus to develop Knowlege Management were
320947 - reviewed on 071106. ref SDS 29 OS6M Advantage of relying on current
320948 - design to guide program development of Windows version was also
320949 - presented on 071106, ref SDS 29 UJ8N, because software engineering
320950 - depends on experience for understanding scope of work. ref SDS 29 FH6L
320952 - ..
320953 - Morris prepared a list of SDS features ("major systems") in a letter
320954 - submitted on 950221. ref SDS 5 MT9F On 070823 Gary submitted a letter
320955 - updating Morris' list, ref SDS 24 J04M, both cited in the record on
320956 - 070907. ref SDS 26 645L
320958 - ..
320959 - Explanation of SDS records was reviewed on 071212. ref SDS 31 KO4F On
320960 - 071219 Gary discussed SDS features again. ref SDS 32 UH4K
320962 - ..
320963 - On 960406 Morris reported that everybody has difficulty finding
320964 - critical details on the computer. ref SDS 7 4249 On 021108 Microsoft
320965 - project to improve ability to find things on the computer. ref SDS 16
320966 - EF5I On 070126 search becoming holy grail computer productivity to
320967 - find information piling up on computers because everything is filed
320968 - miscellaneous. ref SDS 21 B35L
320970 - ..
320971 - [...below, SDS functions are listed that execute essential
320972 - feature, per above. ref SDS 0 6P9J
320974 - ..
320975 - [...below Gary reported having previously submitted a list
320976 - of features. ref SDS 0 LX8M
320978 - ..
320979 - [On 080104 Morris discussed difficulty understanding SDS
320980 - scope and design; asks why SDS improves productivity, and
320981 - cites support for memory and diligence using good
320982 - management practices consistently. ref SDS 34 EM9F
320984 - ..
320985 - [On 080127 letter to Morris Jones cites question today on
320986 - reasons for SDS support for Knowledge Mangement, which has
320987 - not been accomplished by other technologies; recommends
320988 - reviewing record on 960304 reporting Vannevar Bush vision
320989 - for using computers to perform electronic records
320990 - management that sets a good agenda for advancing from
320991 - information to Knowledge Management. ref SDS 36 ON3X
320993 - ..
320994 - [On 080206 Morris proposes using keyword search engine to
320995 - streamline SDS development for Windows application,
320996 - ref SDS 38 RT4J; search engines are very popular, and there
320997 - is no showing of market demand for current SDS Subject
320998 - Index system, which is hard to develop with Java
320999 - programming tools that are easy to use. ref SDS 38 CV9N
321001 - ..
321002 - [On 080318 people cannot find correspondence stored on
321003 - computers in Microsoft Outlook directories, and in time to
321004 - get things done, ref SDS 39 GZ7J, even using search and
321005 - computer indexing technologies. ref SDS 39 0R6G
321007 - ..
321008 - [On 080831 difficulty remembering the record of personal
321009 - and organizational memory cited by Jack Park re-submitting
321010 - information forgotten in the record. ref SDS 41 H68I
321012 - ..
321013 - "Essential features" listed by "priorities" depends on context. On
321014 - 071212 Morris was working to understand the vision of SDS. ref SDS 31
321015 - ST3J POIMS explains the vision of SDS to enable intelligence support,
321016 - and describes key elements, ref SDS 31 Z48H, as follows...
321018 - 1. people, processes, time................ ref OF 3 015M
321019 - 2. plan, perform, report.................. ref OF 6 6649
321020 - 3. past, present, future.................. ref OF 6 1112
321021 - 4. chronology, context, connection........ ref OF 6 8555
321022 - 5. 8-steps Communication Metrics.......... ref OF 6 685K
321024 - ..
321025 - The most essential SDS feature is a 3-layer architecture integrating 7
321026 - elements of flexible strucutre appled through writing with chronology,
321027 - context, and connection that make efficiencies of electronic records
321028 - management in the paperless office model productive, reviewed on
321029 - 890523. ref SDS 1 P13O Harmony integrating people, process, and time,
321030 - explained in POIMS, ref OF 3 7222, leverages innate cognition to
321031 - think, remember, and communicate, explained in POIMS. ref OF 7 3742
321032 - Complementarity of chronology, context, and connections also explained
321033 - in POIMS. ref OF 6 8555, optimizes synergy from the plan, perform,
321034 - report intelligence process, sometimes called the scientific method,
321035 - explained in POIMS, ref OF 6 6649, also reviewed on 890523.
321036 - ref SDS 1 LV59
321039 - ..
321040 - Brain Power Balance Both Hands Efficient Usability
321041 - Responsive Efficient Usability Prominent Feature SDS
321042 - Function Keys Complement SDS Menus Efficient Usability Key SDS Feature
321044 - Function keys, mouse and keyboard provide efficient usability applying
321045 - left and right brain power that increase focus, speed, and accuracy
321046 - performing daily work, explained in POIMS, ref OF 6 6M5H, and
321047 - discussed with Gary on 020924. ref SDS 15 EL8F "Enter" on the
321048 - keyboard, for example, has many intutitive applications based on
321049 - situational awareness, explained on 990530. ref SDS 10 2R6R
321051 - [...below Gary explains requirements for user profiles
321052 - mapping keys. ref SDS 0 PA5P
321054 - ..
321055 - SDS design for efficient usability was discussed with Morris and Gary
321056 - on 071113 in connection with considering XML editor to replace
321057 - DOS-based Medit editor. ref SDS 30 446N During the meeting a few
321058 - weeks ago on 071212 Morris seemed to indicate that XML editing tools
321059 - can be created with efficient usability. ref SDS 31 OO3L
321062 - ..
321063 - Prototype Demonstration SDS Aids Learning Knowledge Management
321064 - Knowledege Management Learn by Doing Use Prototype Demonstration
321066 - Morris seems to object in his letter today to efforts demonstrating
321067 - SDS features, ref SDS 0 3V35 This occurred most recently showing the
321068 - Subject Index on 071212. ref SDS 31 ZJ3H
321070 - ..
321071 - Understanding SDS "features" requires using SDS, shown by experience
321072 - on 910520. ref SDS 2 NY4G On 920215 Morris noted that SDS features
321073 - are counterintuitive, ref SDS 4 5820, and so difficult to grasp from a
321074 - list, noted earlier on 910529. ref SDS 3 9989 Complementary,
321075 - integrated tasks yield efficient usability, noted by Mike Poremba on
321076 - 020531, ref SDS 14 5M3G, and by Morris earlier on 910520. ref SDS 2
321077 - HV51 Ergonomics of keyboard, function keys, and mouse benefit from
321078 - right and left brain synergy, reviewed on 001206, ref SDS 12 PK4H, and
321079 - citing research on 990121. ref SDS 8 CO6I Efficient usability makes
321080 - doing Knowledge Management fun, like playing a piano, so that
321081 - everything is in the right place at the right time, explained in
321082 - POIMS. ref OF 6 6M5H
321084 - ..
321085 - Case study showing Jack Park's analysis of SDS, primarily for the
321086 - OHS/DKR project at SRI during 2000 shows that the best way to learn
321087 - Knowledge Management is by using SDS to do Knowledge Management.
321088 - ref SDS 33 M53N The first step is to "study what works" by seeing
321089 - demonstrations of features using the prototype program.
Plan Perform Report Essential SDS Features Augment Intelligence Func
500401 - ..
500402 - Plan Perform Report SDS Features Augment Intelligence Use Cases
500403 - People Process Time Use Cases for Chronlogy Context Connection
500404 - Features SDS Integrate Time Information People Document Management
500405 - Functions SDS Features Integrate Complementary Synergy Keyboard Mouse
500407 - SDS features (responding to Morris' letter today, per above,
500408 - ref SDS 0 PX5H) were listed on 070907, ref SDS 26 1998, and have
500409 - common editing tools for applying unique functions listed in program
500410 - menus for accomplishing all the work that arises from SDS use cases...
500412 - [...below, Gary sent another letter listing SDS essential
500413 - features again. ref SDS 0 LX8M
500415 - ..
500416 - [On 080108 submitted this listing to Morris with link from
500417 - letter to SDS development team. ref SDS 35 WX5R
500419 - ..
500420 - [On 080128 letter to Morris on scheduling a meeting to
500421 - review progress citing the letter today sumbitting SDS
500422 - functions. ref SDS 37 M35R
500424 - ..
500425 - [On 080606 Morris asked for SDS use cases again. ref SDS 40
500426 - 9Z4H
500428 - ..
500429 - 1. Schedule Feature
500431 - ..
500432 - File Menu
500434 - ..
500435 - File access
500437 - Complements Windows file management with tools for
500438 - managing SDS and external files in particular ways.
500440 - ..
500441 - Quit/close/exit record........................ ESC
500443 - ..
500444 - Save........................................... F2
500446 - Writes Schedule file to the disk and updates data
500447 - bases, including Schedule analysis and adjustments.
500449 - ..
500450 - Next Screen............................... Ctrl F6
500452 - Switches through the edit chain; Ctrl F6 may be common
500453 - with Windows, since this function is used in other
500454 - programs as well.
500456 - ..
500457 - Transfer Directory Clear
500459 - One way to empty directory of files waiting to be
500460 - transferred to the Internet; used if someone changes
500461 - their mind about uploading stuff. Morris has some
500462 - familiarity with this application from work on 060614.
500463 - ref SDS 20 OU47
500465 - ..
500466 - Add 6 months to Calendar
500468 - The Schedule automatically extends, however, if
500469 - someone needs to schedule for 2 years out, then the
500470 - schedule calendar needs to be extended to include the
500471 - needed date.
500473 - ..
500474 - Reduce Calendar
500476 - ..
500477 - Backup Interim
500479 - SDS is automatically backed up once a day on startup.
500480 - This functions lets people do additional interim backups
500481 - at will.
500483 - ..
500484 - Edit Menu
500486 - Scroll file up 10 lines (half screen)........... F9
500487 - Scroll file down 10 lines (half screen)........ F10
500488 - Split line at cursor........................ Alt F5
500489 - Join lines.................................. Alt F6
500490 - Justify paragraph........................... Alt F9
500491 - Delete line................................. Alt F8
500492 - Move line mark.................................. F4
500493 - Move line target................................ F5
500495 - ..
500496 - Contacts
500498 - Enter part of a name for a person or organization and
500499 - press Enter to open alphabetical index of individuals or
500500 - organizations beginning at the string specified in the
500501 - Contacts menu. Contact index features are explained
500502 - below. ref SDS 0 6J40
500504 - ..
500505 - Add record organization
500506 - Add record individuals
500508 - Click on either to create a new record for a person or
500509 - an organization, which may further list the person.
500511 - ..
500512 - Subjects
500514 - Open Subject Index for Context Management ops. ref SDS 0
500515 - XL8N
500517 - Manage
500519 - New task....................................... F1
500521 - Creates new task in the Schedule.
500523 - ..
500524 - Time........................................... F7
500526 - Enters current time or clears time field, which user
500527 - can edit.
500529 - ..
500530 - Diary/Schedule set status...................... F8
500532 - Adds a dot to a task in the Schedule that tells the
500533 - system to treat the task as either a scheduled or a
500534 - performed task.
500536 - ..
500537 - Highlight................................ Shift F9
500539 - Colors a task in the schedule for highlighting.
500541 - ..
500542 - Delete......................................Alt F8
500544 - Remove a task from the Schedule and any associated
500545 - disk in the Schedule directory.
500547 - ..
500548 - Open........................................ Enter
500550 - Open the record for a schedule or diary task listed in
500551 - the Schedule, also, works with double click.
500553 - ..
500554 - Executive Services
500556 - Called with click or Enter in the menu; opens services
500557 - for Executive Services that gives someone access to
500558 - another user's Schedule and Diary records.
500560 - ..
500561 - Action Items
500563 - Called with click or Enter in the menu; constructs
500564 - list of all action items for past 90 days.
500566 - Alternatively, action items can be assembled by
500567 - subject, including organization and individual using
500568 - the Report system with the Subject Index.
500570 - ..
500571 - Action Items are also listed in Schedule Analysis and
500572 - Adjustments.
500575 - ..
500576 - Documents
500578 - Called with click or Enter in the menu; opens report
500579 - to assemble documents based on various criteria.
500581 - ..
500582 - 2. SDS Records Applied to Schedule and Diary
500584 - ..
500585 - File Menu
500587 - File access................................. F1 F3
500589 - Same function as in Schedule. ref SDS 0 U042
500591 - ..
500592 - Quit/close/exit record........................ ESC
500594 - ..
500595 - Save........................................... F2
500597 - Writes the record to the disk similar to the Schedule,
500598 - ref SDS 0 M64V, and performs 30 additional features
500599 - listed on 031203. ref SDS 17 JV8G, e.g., adds anchors as
500600 - needed, and verifies uniqueness, maintains control
500601 - fields, updates indexes, updates changes to outlining
500602 - structures, updates line numbers, etc. F2 to save an
500603 - SDS record performs thousands of Knowledge Management
500604 - tasks that people don't do because it is a lot of hard
500605 - work.
500607 - ..
500608 - Save HTML for Internet
500610 - Also click above Quit=ESC on Command Line, converts SDS
500611 - record into HTML for display in a browser; places copy
500612 - in directory structure for viewing on local computer,
500613 - and places copy in directory for transfer to the
500614 - Internet when executed by the user.
500616 - ..
500617 - Display on local computer provides record of Internet
500618 - inventory, and is an alternate view for recognizing
500619 - errors and omissions that are typically overlookd in
500620 - proof reading.
500622 - ..
500623 - Maintain HTML Files
500625 - Also click above Profile Level indicator on Command
500626 - Line, displays all files pending transfer to Internet.
500628 - ..
500629 - Transfer HTML Files to Internet
500631 - Also click above black spaces between Quit=ESC and
500632 - Schedule/Diary on Command Line; launches op to FTP
500633 - files in Transfer directory to the Internet and deletes
500634 - files from Transfer directory.
500636 - ..
500637 - Document Segment
500639 - Opens screen similar to File Access but to construct
500640 - smaller segments of large document files, which work
500641 - safely within Medit memory limitations, a form of
500642 - "virtual memory" that may not be needed if new version
500643 - solves memory problem.
500645 - ..
500646 - Next Screen............................... Ctrl F6
500648 - Switches through the edit chain, per explanation above.
500649 - ref SDS 0 M651
500651 - ..
500652 - Transfer Directory Clear
500654 - See explanation for Schedule. ref SDS 0 M65X
500656 - ..
500657 - Line Numbers............................. Shift F7
500659 - Turns Medit line numbers on and off.
500661 - ..
500662 - Cancel Commands........................... Ctrl F5
500664 - Clears any pending commands, like pending links, copy,
500665 - move, etc.
500667 - ..
500668 - Function key list
500670 - Opens list of current function key assignments
500672 - ..
500673 - Backup Interim
500675 - See explanation above. ref SDS 0 AG32
500677 - ..
500678 - Edit Menu
500680 - Profile function key assignments............... F1
500681 - Scroll file up 10 lines (half screen).......... F9
500682 - Scroll file down 10 lines (half screen)....... F10
500683 - Scroll file left.............................. F7
500684 - Scroll file right............................. F8
500685 - Search and change open menu..................F1 F4
500686 - Replicate current line..........................F6
500687 - Replicate multiple lines..................Shift F6
500688 - Split line at cursor....................... Alt F5
500689 - Join lines................................. Alt F6
500690 - Justify paragraph.......................... Alt F9
500691 - Add lines..................................Alt F10
500692 - Delete line................................ Alt F8
500693 - Copy line mark................................. F4
500694 - Move line mark.............................Ctrl F4
500695 - ..
500696 - Target copy, move, link........................ F5
500697 - Mark for return............................ Alt F1
500698 - Return to mark 1..........................Shift F1
500699 - Mark for return............................ Alt F2
500700 - Return to mark 2..........................Shift F2
500701 - Mark for return and empty cut and paste.... Alt F3
500702 - Return to mark 3..........................Shift F2
500703 - Remove pending copy, move, links...........Ctrl F5
500704 - Headings underline....................... F1 F1 F5
500705 - Anchors custom assignments............... F1 F1 F3
500706 - Indent paragraph to common margin........ F1 F1 F7
500707 - Indent para maintain margins............. F1 F1 F8
500709 - ..
500710 - Contacts
500712 - Same as for Schedule. ref SDS 0 JE5G
500714 - Contacts are typically posted in a set format in SDS
500715 - records by selecting usually from an alphabetical index
500716 - list, but also directly from Contact records into the
500717 - Contacts field at the top of SDS records, and below the
500718 - record description.
500720 - ..
500721 - Similar methods are used but for different parts of a
500722 - Contact record to post document log fields, explained
500723 - below. ref SDS 0 FT4N
500726 - ..
500727 - Diary............................................ F3
500729 - Menu bar
500731 - Type over "Diary" in menu a date and press Enter to get
500732 - list of diary records for the date. Type a date with a
500733 - range to get list of diary records from the specified
500734 - date for the number of days ahead. Simply type a
500735 - number and this is interpreted as a range to list diary
500736 - records. Type any of these forms with a word string to
500737 - select diary records that have string in the record
500738 - description. Include a user ID to select records for
500739 - another user.
500741 - ..
500742 - Diary list past 60 days........................ F3
500744 - ..
500745 - Titles Off
500747 - Removes fixed lines at top of screen that maintains
500748 - visibility of record identity, so that record
500749 - description can be edited for archived diary record.
500750 - For current diary records, description can only be
500751 - changed by closing the record and making the change in
500752 - the Schedule, then open the record again.
500754 - ..
500755 - Delete record
500757 - Removes record from the disk; pressing before closing
500758 - the screen will restore the record.
500760 - ..
500761 - Time stamp shallow outline line number...... F1 F8
500763 - Enters time in line number field to show when certain
500764 - parts of the record occurred throughout the day.
500766 - ..
500767 - Also enters "Progress" shallow outline description for
500768 - the first level of narrative that is separated from the
500769 - Summary/Objective.
500771 - ..
500772 - Document Analysis
500774 - Opens menu similar to File Access to identify a file
500775 - that will be read into the SDS record for analysis with
500776 - outline structure pre-assigned; uses baseline filename
500777 - c: sd 10 x.txt, which provides a convenient way to
500778 - bring email into SDS records.
500780 - ..
500781 - Diagnostics Communication Metrics
500783 - Computes and displays following information units for
500784 - Communication Metrics on current record...
500786 - 1. Date
500787 - 2. Time
500788 - 3. Hours of work
500789 - 4. Contacts
500790 - 5. Words
500791 - 6. Subjects
500792 - 7. Segments between Control Fields
500793 - 8. Links
500794 - 9. Actions
500795 - 10. Headings
500797 - ..
500798 - Confidential/Privacy status
500800 - Marks record confidential that prevents publication on
500801 - the Internet or transfer to others for routine sharing
500802 - of records.
500804 - ..
500805 - References Maintain
500807 - References of SDS records, correspondence and other
500808 - files are automatically maintained in sort order with
500809 - "save" function. This function deletes any entries in
500810 - Reference fields that are not used for links in the
500811 - record.
500814 - ..
500815 - Subjects
500817 - Same as for Schedule. ref SDS 0 MK6F; Open Subject Index
500818 - for Context Management ops. ref SDS 0 XL8N
500820 - Dictionary definitions
500821 - Strings words acronyms................... F1 F1 F6
500823 - Capture current character string and look for account
500824 - in the Subject Index; if not present, construct an
500825 - account in Subject Index for explaining/defining the
500826 - string, and enable hierarchial structure for managing
500827 - activity reported in SDS records associated the word
500828 - or acronym.
500830 - ..
500831 - Manage
500833 - Links create and open....................... Enter
500835 - Double click works similarly to create or
500836 - open links depending on whether a record
500837 - or file has been "marked for linking" with
500838 - F5 or F3 has been used to open the Diary
500839 - listing, or a report has been called to
500840 - open diary records or document files of
500841 - some kind.
500843 - ..
500844 - Text replicate with links...................... F3
500846 - Similar to cut and paste, except pressing F3 with
500847 - cursor in line number field captures consecutive lines
500848 - of text, i.e., a paragraph, and further captures any
500849 - sources for links to SDS records embedded in the
500850 - paragraph.
500852 - ..
500853 - If there is no text entered where F3 is called with the
500854 - cursor in the line number field, and if text has been
500855 - previously captured, then that captured text is entered
500856 - at the current location. All links are updated with
500857 - references required added to the SDS record Reference
500858 - field.
500860 - ..
500861 - This feature is mostly used to populate forward links
500862 - that typically occur in multiple locations, and so
500863 - maintains consistent representation for uniform
500864 - understanding, and without taking any appreciable time.
500866 - ..
500867 - Schedule new task..................... F1 Shift F1
500869 - Uses current SDS record to create a new SDS record
500870 - linked back to the current record and enters a new task
500871 - in the Schedule.
500873 - ..
500874 - Summary
500876 - Click on menu to construct summary of all headlines for
500877 - navigating to specific locations in SDS record.
500879 - ..
500880 - Subjects
500882 - Click on menu to construct summary of all subjects
500883 - descriptions in the record for navigating to specific
500884 - locations.
500886 - ..
500887 - Control Fields create....................... F1 F6
500889 - Constructs record segments according to user's
500890 - determination, i.e., one paragraph, several, etc.,
500891 - that all pertain to the same subject.
500893 - ..
500894 - Subjects list descriptions.................. Enter
500896 - Double click or press Enter with cursor on Control
500897 - Field description line and beyond the "Subject/File"
500898 - field, and code opens every account listed in the
500899 - Control Field and lists every description that is not a
500900 - duplication, i.e., "multiple view."
500902 - ..
500903 - Subject descriptions conform................ Enter
500905 - All descriptions for multiple views of all accounts in
500906 - a Control Field are conformed to the description of the
500907 - account in the Control Field where the cursor is
500908 - positioned, unless the first description is different;
500909 - then a report is issued showing variances.
500911 - ..
500912 - Subject descriptions force conform.......... Enter
500914 - Same as for the above explanation, except there are no
500915 - exceptions.
500917 - ..
500918 - Subject accounts construct and
500919 - assign automatically........................ Enter
500921 - ..
500922 - Subject Accounts Replicate.................... F3
500924 - F3 executed with cursor on a character for a subject
500925 - account captures the entire set of Subject accounts for
500926 - the Control Field.
500928 - ..
500929 - F3 executed with cursor on a space (character 32) for a
500930 - subject account appends content captured from another
500931 - Control Field to the current Control Field.
500933 - ..
500934 - Actions
500936 - Click on menu to construct summary of all action items
500937 - identified in the record for navigating to specific
500938 - locations.
500940 - ..
500941 - Highlight................................ Shift F9
500943 - Scrolls through alternate highlight options...
500945 - a. Headlines
500946 - b. Bold the line no functionality
500947 - c. Action item for user
500948 - d. Action item for others tracked by user
500949 - e. Action item performed
500951 - ..
500952 - Reports & Memos
500954 - Subjects, Contacts, References.............. F1 F9
500956 - Place cursor on a Subject account in a Control Field or
500957 - a Function account, and call F1 F9 to get a screen to
500958 - specify criteria for getting report of SDS records that
500959 - meet the criteria beginning with the subject or
500960 - function.
500962 - ..
500963 - Similar for Contacts listed at the top of an SDS
500964 - record.
500966 - ..
500967 - References work the same to report on SDS records where
500968 - a particular docuemnt has been used, considered, etc.
500970 - ..
500971 - Keywords
500973 - Open a screen to enter a specification to search SDS
500974 - records for particular word strings.
500976 - ..
500977 - Documents
500979 - Spell Check
500981 - Launches program to spell check current record.
500983 - ..
500984 - Docment Log management...................... F1 F5
500986 - Creates format for document log structure to fill out
500987 - identifying formal correspondence and other files,
500988 - including publications. Scrolls through choices of...
500990 - DRT Documents Received Today
500991 - DRP Documents Received Prior
500992 - DIT Documents Issued Today
500993 - DIP Documents Issued Prior
500994 - Other Files
500996 - ..
500997 - User fills out the document log format by...
500999 - ..
501000 - Primary document log ID fields............. F5
501002 - F5 pressed on a Control Field line determines the
501003 - portion of the Subject Field account that comprises
501004 - a directory structure for primary document ID,
501005 - often a project account, and this portion is
501006 - entered in the Document Log primary account
501007 - structure. The code opens the Subject Index and
501008 - extracts the description from the Subject Index and
501009 - enters this in the description field of the
501010 - Document Log primary account field. The code
501011 - further extracts the complete subject account code
501012 - string and enters in the appropriate secondary
501013 - document log field.
501015 - ..
501016 - Secondary Document Log fields
501018 - F8 twice shifts the screen to expose sender and user
501019 - Contact fields in secondary Document Log data
501020 - structures. Contacts menu is used to select the
501021 - "From" field using procedures shown above.
501022 - ref SDS 0 065R
501025 - ..
501026 - Subjects assign to documents................... F5
501028 - F5 marks a line in Reference field for Document Log
501029 - template and then, when F5 is pressed again in a
501030 - Control Field, the code opens the Subject Index to the
501031 - account in the Control Field and finds the account in
501032 - the Index, then enters the description in the Document
501033 - Log along wtih the account identification.
501035 - ..
501036 - Report
501038 - Opens a screen for the user to specify criteria to get
501039 - a list of documents meeting the criteria. The user can
501040 - then open the documents from the report or open the SDS
501041 - records where the document was received into the record
501042 - to track activity in connection with the document.
501044 - ..
501045 - Foundational Documents SDS
501047 - Enters a list of all SDS foundational documents, e.g.,
501048 - POIMS, NWO, Typical Day Scenario, for quick reference
501049 - to link work reported to ideas in the documents, and
501050 - further to work on the documents.
501052 - ..
501053 - Tools
501055 - Draw lines and boxes..................... F1 F1 F2
501057 - Supplemental Function key profile assigning keys
501058 - for creating rudimentary lines and boxes in SDS
501059 - records.
501061 - ..
501062 - Function Key list
501064 - ..
501065 - Update Function Key list
501067 - ..
501068 - ASCII Char Values
501070 - Shows numerical values for ascii characters.
501072 - ..
501073 - Counters
501075 - Displays current values for all SDS counters
501077 - ..
501078 - Macro code display.......................... Enter
501080 - Press Enter or double click on a program macro,
501081 - e.g., "macro 80" shown in an Medit file, and the
501082 - program looks up the macro in an index, and opens
501083 - the file where the macro code is constructed and
501084 - finds the -entry for that macro.
501086 - ..
501087 - Make SDS End User version
501089 - Converts macro code to run everything on the C
501090 - drive, compiles the program and assembles
501091 - everything for an End user which omits features
501092 - available for development.
501094 - ..
501095 - 3. Contact Management of People and Organizations
501097 - Data structures for Contacts are set out in the record on
501098 - 071106. ref SDS 29 2J8H
501100 - ..
501101 - Organizational data structures are listed on 071106.
501102 - ref SDS 29 0R4H
501104 - ..
501105 - Contact Index features...
501107 - ..
501108 - Indexes for Contacts are opened from SDS records as explained
501109 - in for the Schedule system. ref SDS 0 JE5G
501111 - Enter....................................... Enter
501113 - Enters a reference with fixed format to the individual
501114 - or organization and individual listed in the Contact
501115 - Index into the Contacts field for the SDS record
501116 - where the user opend the Contact Index.
501118 - ..
501119 - Open record.................................... F2
501121 - Opens Contact record for the individual or
501122 - organization listed in the Index, and at the location
501123 - in the organization record where the individual is
501124 - defined, as listed in the Index.
501126 - ..
501127 - User can also move the cursor right at least 2
501128 - columns and press Enter to open the record rather
501129 - than load it to an SDS record.
501131 - ..
501132 - Delete record
501134 - Removes the Contact record, updates the Index, and
501135 - removes entries from repetitive dates data base.
501137 - ..
501138 - Reports.................................... Alt F9
501140 - Selects a Contact record account and enters in a
501141 - screen to specify criteria for getting a report on SDS
501142 - records where the Contact in the Index has been
501143 - entered.
501145 - ..
501146 - Contact Records features
501148 - File
501150 - Quit close record......................... ESC
501152 - Save....................................... F2
501154 - Write record to disk, update alphabetical index
501155 - files; update multiple indexes for organizational
501156 - contact records with all alternate names, and for
501157 - all individuals in an organizational contact record
501158 - which the user designates for indexing.
501160 - ..
501161 - Update repetitive date indexes.
501163 - ..
501164 - Edit menu
501166 - Same essential commands for SDS records. ref SDS 0
501167 - PRTT
501169 - ..
501170 - Report
501172 - Opens screen to select criteria for doing a report on
501173 - SDS records where the Contact and the idividual
501174 - selected in the Contact record is referenced, same as
501175 - Alt F9 in the Contact index, per above. ref SDS 0 TW78
501177 - ..
501178 - Load
501180 - Enter a reference to the Contact Record for the person
501181 - where the cursor is positioned in the Contact record
501182 - into the SDS record Contacts field.
501184 - ..
501185 - Letterhead
501187 - When "letterhead" is clicked in a Contact record menu
501188 - the program selects fields to construct a letterhead
501189 - for correspondece from the contact, including the
501190 - salutation, and complimentary close; this is entered
501191 - into a document log support macro, so that when the
501192 - user creates the record of a document issued or
501193 - received using the document log features in an SDS
501194 - record, per above, ref SDS 0 FT60,
501196 - ..
501197 - 4. Subject Index for Context Management
501199 - File
501201 - Save........................................... F2
501203 - Writes current index screen to the disk.
501205 - ..
501206 - Quit/close Subject Index...................... ESC
501208 - ..
501209 - Files for subject account................... F1 F5
501211 - Construct list of files on the disk organized at the
501212 - current account level, e.g., a project, or
501213 - sub-account.
501215 - ..
501216 - Next Screen............................... Ctrl F6
501218 - Switches through the edit chain, per explanation above,
501219 - ref SDS 0 M651, except this uses record indentification
501220 - data stored in a transfer file to open the originating
501221 - SDS record and in a separate block of memory using
501222 - Windows Start command.
501224 - ..
501225 - Delete current index
501227 - Executed only through the menu, and entails a
501228 - verification step to reduce the chance of accidentally
501229 - deleting an index that is needed. Moves the index to
501230 - the prior level.
501232 - ..
501233 - Cancel Commands........................... Ctrl F5
501235 - Clears any pending commands, like pending links, copy,
501236 - move, etc.
501238 - ..
501239 - Edit
501241 - Similar to SDS records. ref SDS 0 PRTT
501243 - ..
501244 - Segment Indexes
501246 - Constructs new account segment to reduce burden on main
501247 - memory of large indexes. Click and the current index
501248 - is segmented at the cursor.
501250 - ..
501251 - List Directory content
501253 - Lists all subject index files at the current directory
501254 - level to asses when files are too bid and need to be
501255 - further segmented.
501257 - ..
501258 - Subjects
501260 - Sort
501262 - Sorts an index level to find instances of sub-levels
501263 - for Context Management including assignment to SDS
501264 - records, calling a report.
501266 - ..
501267 - Find account description...
501269 - At any index level, a description can be located by
501270 - typing over any convenient account description in lower
501271 - case letters the beginning of a keyword and pressing
501272 - Enter. The current index is closed and its complete
501273 - list is searched in an alternative sorted listing with
501274 - binary methods.
501276 - ..
501277 - Alternatively, F4 applied on any account will use the
501278 - account string from the beginning to the cursor
501279 - location to find all similarly defined accounts using
501280 - the same binary methods.
501282 - ..
501283 - If nothing is found the user is positioned at the top
501284 - an alphabetical list. The user can scroll this list
501285 - manually, close the list, or enter another
501286 - specification and look again.
501288 - ..
501289 - If there is a hit the line is positioned in the middle
501290 - of the screen showing an alphabetical list of
501291 - everything above and below the target string, so the
501292 - User can see all related strings.
501294 - ..
501295 - Next level.................................. F1 F2
501297 - Scrolls to a deeper level in the hierarchy.
501299 - ..
501300 - If there is no deeper level, a menu is presented that
501301 - permits constructing a deeper level, or cancelling and
501302 - returning the prior level.
501304 - ..
501305 - Dougle click or press Enter with Cursor beyond the
501306 - first 10 characters of an account description also
501307 - accomplishes F1 F1 functionality.
501310 - ..
501311 - Prior level................................. F1 F3
501313 - Scrolls back to the higher level.
501315 - ..
501316 - Sorted index restore actual index........... F1 F3
501318 - When an index is sorted to find an account description
501319 - the actual index can then be restored at the account of
501320 - located description for processing by pressing F1 F3.
501321 - This allows editing, creating a new level, what ever
501322 - might be needed for Context Management.
501324 - ..
501325 - Conform changes to account..................... F5
501327 - Typcially subject accounts comprise 10 - 30 alternate
501328 - descriptions. Changes to an account are replicated
501329 - with F5 so that all the multiple views of the account
501330 - need not be manually updated.
501332 - ..
501333 - Sort account descriptions...................... F5
501335 - Tapped twice causes all of the alternate descriptions
501336 - of an account to be sorted for finding a particular
501337 - form. F1 F3 then restors the actual index at the
501338 - located account description, per above. ref SDS 0 FW78
501340 - ..
501341 - New Accounts................................... F6
501343 - Tapped once this creates another line to create
501344 - multiple descriptions (views) of the account.
501346 - ..
501347 - Tapped twice at the bottom of of an account and within
501348 - a second startes a new account and increments the
501349 - template account with a blank description.
501351 - ..
501352 - Capture account descriptions................... F3
501354 - Captures account descriptions in a temporary file for
501355 - replication to other contextual frames.
501357 - ..
501358 - Replicate account descriptions............Shift F3
501360 - Adds descriptions captured with F3 to descriptions that
501361 - already exist for another contextual frame.
501363 - ..
501364 - Replication replace descriptions......... F1 F1 F3
501366 - Removes all descriptions for an account and replaces
501367 - with content captured with F3 from another account.
501369 - ..
501370 - Account assign to SDS record................ Enter
501372 - Double click or press Enter with the cursor on the
501373 - first 10 characters of an account description closes
501374 - the Subject Index and posts the subject account to the
501375 - subject account part of the Control Field where the
501376 - cursor was positioned when the subject index was
501377 - opened.
501379 - ..
501380 - Account look up in SDS record............... Enter
501382 - Double click or press Enter with cursor within first 15
501383 - columns of left margin, Subject Index is closed and a
501384 - serach is performed to find the first entry of the
501385 - subject account where the cursor was positioned when
501386 - the operation was launched in the Subject Index.
501387 - Pressing Shift F4 srolls to find all instances of the
501388 - account in the SDS record.
501390 - ..
501391 - Report...................................... Enter
501393 - Alternativley............................ F1 F9
501395 - Double click or press Enter with cursor within 10
501396 - columns of the beginning of the account description
501397 - closes the Subject Index and a screen is opened for
501398 - selecting criteria to report on all SDS records where
501399 - the subject account occurs.
501401 - ..
501402 - New Account Template
501404 - Select only from the menu to create new accounts and
501405 - sub accounts in the Subject Index, as explained on
501406 - 071010. ref SDS 28 1573
501408 - ..
501409 - 5. File Access Directory Management
501411 - Execute specification.......................... Enter
501413 - If a file is listed and exists, the file is opened, if it
501414 - is a directory level, the files at that level are listed,
501415 - similar to Subject Index. ref SDS 0 AR40
501417 - ..
501418 - Disk drive........................................ F3
501420 - Scroll through drive letters on the disk.
501422 - ..
501423 - Maintain file management.......................... F2
501425 - Launches operation to compare files on the disk with
501426 - inventory and explanation of files for a particular
501427 - matter, e.g., SDS program macros.
Documentation SDS Development Windows Application Code Progress Doxy
640401 - ..
640402 - Doxygen Code Documentation Progress
640403 - Code Documentation Progress Considering Doxygen
640406 - Morris continues...
640408 - 6. I got to the Doxygen site. It was marked as mal ware, and has
640409 - now been unmarked. (Leave it to the people out there…). I
640410 - have downloaded the tool, and the markup is quite simple. I
640411 - still need to compile it under cygwin and see if I can get it
640412 - to work with some code. I'm not sure what documentation will
640413 - result, but it is better than nothing. I really hate code
640414 - markups that add so much junk you can't read or find the code…
640415 - (Sore point from past experiences…), ref DRT 1 UH6O
640417 - ..
640418 - Morris discussed using SDS for engineering management that includes
640419 - documenting the work, on 990524. ref SDS 9 0876
640421 - [...below, Gary provides additional source support.
640422 - ref SDS 0 PB5S
640424 - ..
640425 - Documentation of SDS development has worked well in SDS the past 20
640426 - years shown by case study on 000824, ref SDS 11 0001, for example
640427 - on...
640429 - Subject index standard accounts
640430 - to make records management
640431 - fast, easy, effective.............. 071010, ref SDS 28 0001
640433 - ..
640434 - Linking fix problems............... 070616, ref SDS 23 0001
640436 - ..
640437 - Outlining improved................. 070526, ref SDS 22 SN5L
640439 - ..
640440 - Subject index controlled and
640441 - forced replication reduced from
640442 - hours to 1 secont.................. 060222, ref SDS 19 0001
640444 - [On 080206 Morris explained resistance to using SDS for
640445 - understanding SDS use cases that improve productivity of
640446 - engineering management, innnovation, and development.
640447 - ref SDS 38 RR67
Everything Memory Morris Agrees Problematic Large Collection Files S
890401 - ..
890402 - Expanding SDS Records Stored on Disk Proven Solution
890403 - Large Collection Files SDS Manages Like Building Uses Nuts and Bolts
890404 - Memory Combining Work Product with Tool System Problematic
890406 - Follow up ref SDS 31 W889.
890408 - Morris continues...
890410 - 7. I agree that everything in memory may be a problem, but unless
890411 - we go back to a large collection of files, then you have to
890412 - handle the case of expanding records and how to place them on
890413 - the disk. Perhaps the file system, or an embedded Zip file
890414 - would be the best. A caching scheme can be implemented with a
890415 - base class, but every pointer has to be checked and
890416 - de-referenced through the class, and that will slow things down
890417 - quite a bit. ref DRT 1 UH77
890419 - ..
890420 - Morris responds to Gary's letter on 071219. ref SDS 32 TN5L
890422 - [...below, Gary explains granular structure of SDS records
890423 - based on time that complements granular addressability and
890424 - granular indexing for command and control of low levels of
890425 - detail. ref SDS 0 PA6P
890427 - ..
890428 - [...below, Gary explains background using separate files
890429 - for SDS records the past 20 years. ref SDS 0 PA6S
890431 - ..
890432 - SDS design was discussed during the meeting on 071212 that reviewed
890433 - benefits proven by experience. ref SDS 31 ST65
890435 - [On 080104 Morris considering use of Java data objects for
890436 - SDS development of Windows application. ref SDS 34 OM6G
890438 - ..
890439 - SDS technology organizes collections of files similar to a library,
890440 - filing cabinet that contains letters, memos, specifications, books,
890441 - movies. In the same way that an automobile is a large collection of
890442 - integrated tools for efficient travel, and a building is a large
890443 - collection of nuts and bolts, and beams, floors, and walls for
890444 - efficient use of space, SDS provides structure and order for an
890445 - efficient Knowledge Space with everything in the right place at the
890446 - right time noted by Morris on 010425. ref SDS 13 EP7F Organizing
890447 - complexity into predictable order underlies the power of knowledge
890448 - explained by the locality principle, reviewed on 040312. ref SDS 18
890449 - YH4G
890451 - ..
890452 - SDS has been placing records on the disk for 20 years. This seems
890453 - like a proven solution.
890455 - [...below, Gary suggests not reinventing the "wheels" of
890456 - Knowledge Management already invented by SDS. ref SDS 0
890457 - PB7P
890459 - ..
890460 - Morris indicated in a call that search will be improved by placing
890461 - everything in memory. Findings things in SDS is already very fast
890462 - using the Subject Index, complemented by conventional keyword search.
Multiple Views Applies MFC for Generic Object Model Like Microsoft S
A10401 - ..
A10402 - Multiple Views Applies MFC for Generic Object Model Like Microsoft
A10405 - Morris continues...
A10407 - 8. MFC puts you in a document/View model somewhat close to MVC.
A10408 - The messaging can replace the controller, or the view can
A10409 - activate the controller. At the moment, I am implementing the
A10410 - model in the document container. (Which supports multiple
A10411 - views). The Views cause the model to be changed, and that is
A10412 - reflected to the other views through the document container.
A10413 - The controller layer (If you can call it that) is invoked by
A10414 - the Views to act on the data. (Hope this is close to what you
A10415 - wanted). ref DRT 1 UH86
A10417 - ..
A10418 - 9. I am contemplating a generic "object" model similar to the one
A10419 - MS uses in MFC. This allows anything to contain lists of
A10420 - anything. Every "thing" will be derived from an object, and
A10421 - the object will identify what it contains. There are some
A10422 - silly concepts to consider. Should we allow a phone number to
A10423 - contain a billing code, contact list, etc. For now, I think we
A10424 - go for the generic, and depend on the user to organize
A10425 - information rationally. ref DRT 1 UH96
Fixed Column Text Simpler Design Enables Processing Other Programs L
AP0401 - ..
AP0402 - Fixed Column Text Simpler Design Limits Fonts Formatting
AP0404 - Follow up ref SDS 31 GI9I.
AP0406 - Morris concludes...
AP0408 - 10. The use of other tools may be limited if we move to XML as a
AP0409 - common storage format for the records. If you want fixed
AP0410 - column text, things can be simpler to play with outside the
AP0411 - program, but other limits come into play. (Fonts, formatting,
AP0412 - etc).
AP0414 - [...below Gary notes requirements for SDS records stored as
AP0415 - files on the disk to enable processing with stand-alone
AP0416 - tools. ref SDS 0 PB4S
Essential Features Reflect Experience Using SS Hypertext Editor Con
BI04 - 1435
BI0501 - ..
BI0502 - Essential Features Reflect Experience Using SDS
BI0505 - ..
BI0506 - Received ref DRT 2 0001 from Gary responding to Morris's letter this
BI0507 - morning asking about essential features. ref SDS 0 PX5H
BI0509 - ..
BI0510 - Gary says...
BI0512 - 1. == Features List ==
BI0514 - I believe that the features list I sent when we started is
BI0515 - essentially complete for a start. However, I will go over it
BI0516 - and insure that it represents a reasonable feature set.
BI0517 - ref DRT 2 0001
BI0519 - ..
BI0520 - Gary responds to Morris' request on 071220, which was received this
BI0521 - morning, per above, ref SDS 0 3V35, noting Gary submitted SDS features
BI0522 - in his letter on 070823 and reported on 070907. ref SDS 26 645L
BI0524 - ..
BI0525 - On 070904 Gary explained essential features of Knowledge Management
BI0526 - are easy to list. Integrating features into a working environment
BI0527 - with complementary commands for efficient usability requires skill and
BI0528 - perseverence. ref SDS 25 DV6R Imparting faith that drives a paradigm
BI0529 - shift from the drudge of diligence working hard into the fun of
BI0530 - working intelligently long enough for people to discover the power of
BI0531 - knowledge requires a enabling forces to line up through relentless
BI0532 - pressure showing people a new way of working. ref SDS 25 DV7P
BI0534 - ..
BI0535 - Explanation of SDS records was reviewed on 071212. ref SDS 31 KO4F On
BI0536 - 071219 Gary discussed SDS features again. ref SDS 32 UH4K The record
BI0537 - today lists SDS functions that execute essential feature, per above.
BI0538 - ref SDS 0 6P9J
BI0541 - ..
BI0542 - SDS Granular Structure of Time Addressability Indexing
BI0544 - Gary's letter to Morris continues...
BI0546 - 2. An essential minimum is:
BI0548 - ..
BI0549 - 1. Records keyed by User and Timestamp, with internal outline
BI0550 - structure and internal anchors at the paragraph level.
BI0551 - ref DRT 2 6T5M
BI0553 - a. Schedule records for dates in the future. These can be
BI0554 - moved and copied to other dates in the future.
BI0556 - ..
BI0557 - b. Diary records for dates in the past. These cannot be
BI0558 - moved (may relax later). They can be used as a
BI0559 - template for a schedule record, which automatically
BI0560 - links to the originating record. Diary records need to
BI0561 - be publishable as (X)HTML with references converted to
BI0562 - hyperlinks. ref DRT 2 6T6U
BI0564 - ..
BI0565 - Gary explains granular structure of SDS based on time, adding to
BI0566 - discussion during the meeting on 071212, ref SDS 31 KO4F, and to
BI0567 - Gary's letter received on 071219. ref SDS 32 UH4K Granular elements
BI0568 - of time complement granular addressability and indexing that help
BI0569 - people control lower levels in the microcosm of organic structure
BI0570 - essential for "Knowledge Space" to augment human intelligence,
BI0571 - explained in POIMS. ref OF 6 1232 The power of the microcosm was
BI0572 - reviewed at Intel on 950927. ref SDS 6 5412
BI0574 - ..
BI0575 - Gary clarifies SDS record identification below. ref SDS 0 PB7P
BI0577 - ..
BI0578 - Gary's letter to Morris continues...
BI0580 - 2. Date ordered index of titles with date range selection in
BI0581 - the past (Diary Index). ref DRT 2 6T7Q
BI0583 - ..
BI0584 - 3. Date ordered index of schedule records into the future
BI0585 - (Schedule), ref DRT 2 6T7U
BI0587 - ..
BI0588 - 4. Hyperlinks at the paragraph level between any 2 records in
BI0589 - the system and between users on the same system.
BI0590 - ref DRT 2 6T7X
BI0592 - ..
BI0593 - What is the difference between links and "hyperlinks"?
BI0595 - ..
BI0596 - Gary's letter to Morris continues...
BI0598 - 5. Subject Index outline. Some way of referencing multiple
BI0599 - subjects from control segments within records. ref DRT 2
BI0600 - 6T8R
BI0602 - ..
BI0603 - 6. Document system for dealing with external documents
BI0604 - containing paragraph level anchors. ref DRT 2 6T8V
BI0606 - ..
BI0607 - 7. Contacts just because SDS has them. They can be a simple
BI0608 - as necessary to start. ref DRT 2 6T9P
BI0610 - ..
BI0611 - 3. The first 5 items are essential in order to be able to claim
BI0612 - that it even remotely resembles SDS. ref DRT 2 6T9U
BI0614 - ..
BI0615 - Managing people, organizations, and documents are essential to SDS
BI0616 - support for comprehensive management.
BI0618 - ..
BI0619 - Since everything cannot be done at once, deferring contacts and
BI0620 - documents is a reasonable priority.
BI0622 - ..
BI0623 - Gary's letter to Morris continues...
BI0625 - 4. Consider that the initial system is a hypertext editor
BI0626 - supporting timestamped documents and interconnection. Add a
BI0627 - Subject Outline and the ability to tie records to multiple
BI0628 - subjects, retrieve by subject search, etc, and I think you have
BI0629 - a good starting point. Once we get that, we can discuss why it
BI0630 - isn't (quite) SDS. ref DRT 2 6T9Z
BI0632 - ..
BI0633 - What is a "hypertext" editor relative to SDS that constructs links as
BI0634 - needed?
BI0636 - ..
BI0637 - Gary's letter to Morris continues...
BI0639 - 5. == Key Mappings == [Function Keys Provide Extensibility]
BI0641 - I would suggest that key mappings be modifiable and loadable as
BI0642 - profiles if that is reasonable. Knowing the Windows Hot Key
BI0643 - issues, not all mappings may be possible. Also, we have
BI0644 - available all the multiple combinations and the alphabetic
BI0645 - portion of the keyboard as well. If we can make it possible to
BI0646 - amend any decisions later, key mappings would be a good one to
BI0647 - make modifiable. Allowing key modifiers so as to permit F1 F1
BI0648 - F6 and similar chords would semm to be necessary if we are to
BI0649 - achieve anything close to what SDS supports today. We can do
BI0650 - better as we work with it and think about it. ref DRT 2 A14H
BI0652 - ..
BI0653 - Gary's proposal to maintain user profiles that assign keys aligns with
BI0654 - requirements for efficient usability, discussed above. ref SDS 0 FO94
BI0657 - ..
BI0658 - 6. == Storage Mechanism and Structure == Records Files on Disk
BI0660 - So far as disk storage is concerned, I would settle for the
BI0661 - simplest thing that could possibly work. Having each SDS
BI0662 - record be a disk file has worked for a couple of decades and
BI0663 - makes sense to me. ref DRT 2 6T58
BI0665 - ..
BI0666 - Gary responds to Morris' letter today discussing SDS efficiently
BI0667 - manages a collection of files rather than keeping everyting in memory.
BI0668 - ref SDS 0 TM6U
BI0670 - [...below, Gary suggests not reinventing the "wheels" of
BI0671 - Knowledge Management already invented by SDS. ref SDS 0
BI0672 - PB7P
BI0674 - ..
BI0675 - Gary's letter to Morris continues...
BI0677 - I would use 4-digit years and insure that each record type has
BI0678 - a distinct extension. ref DRT 2 I26G
BI0680 - ..
BI0681 - Using extensions should be analysed for requirements and
BI0682 - applications.
BI0684 - ..
BI0685 - Gary's letter to Morris continues...
BI0687 - At the point in the structure where a "record" begins, an ID
BI0688 - that can convert to a path coupled with flags to determine
BI0689 - whether the record is in memory, has been modified, etc. plus a
BI0690 - "record parser" to read the record into the object model, and I
BI0691 - think we are home. ref DRT 2 136K
BI0693 - ..
BI0694 - With an index file containing a list of timestamps with titles
BI0695 - (the Diary index) we have enough information to load to start.
BI0696 - I don't know how big that file is, but it is easy to find out.
BI0697 - I think SDS maintains one already, so we can just look at the
BI0698 - size. Add a date index into the file even the title index can
BI0699 - be buffered. I wouldn't attempt a general caching scheme
BI0700 - beyond the record as it has all the problems you claim for it.
BI0701 - The ability to sweep the records in memory and dump the Least
BI0702 - Recently Used for some definition would likely be adequate.
BI0703 - ref DRT 2 G43G
BI0705 - ..
BI0706 - 7. As we have discussed, there is some merit in using files as
BI0707 - they are accessible with standalone tools. If we develop some
BI0708 - new storage mechanism, we will have to handle incremental
BI0709 - backup and transfer as well rather than using a simple batch
BI0710 - file and a zip program. ref DRT 2 6U38
BI0712 - ..
BI0713 - Morris comments on limitations using stand-alone tools to process SDS
BI0714 - records, per above. ref SDS 0 TN5P
BI0717 - ..
BI0718 - 8. == MVC ==
BI0720 - My interest in MVC is simply to try to modularize the code so
BI0721 - that we minimize interactions as we change interfaces, object
BI0722 - model, storage structures, etc. Is the current SDS is any
BI0723 - indication, this could have a lifetime well up in the decades,
BI0724 - so eas of maintenance and understanding are vital, IMO.
BI0725 - ref DRT 2 6U46
BI0727 - ..
BI0728 - Is there an example of MVC that indicates application to SDS?
BI0730 - ..
BI0731 - Gary's letter to Morris continues...
BI0733 - 9. == Object Model ==
BI0735 - Having some sort of object model makes sense. Given a
BI0736 - constraint mechanism for what can be contained in what, we
BI0737 - should be able to establish workable rules. I agree that for
BI0738 - the moment, let anything contain anything and expect that the
BI0739 - user won't try anything stupid. We probably need to allow
BI0740 - rules that specify that contained elements are references
BI0741 - rather than copies. I expect that contacts have their own
BI0742 - storage and are referenced with the records. I also expect
BI0743 - that records are not nested but are interlinked. ref DRT 2 6U55
Default Null Subject Account for Blank Record
BJ0401 - ..
BJ0402 - Wheels Reinvent for Productivity Saving Lives Time money
BJ0405 - 10. == Don't Reinvent Unless There Is Benefit ==
BJ0407 - Trying too hard to rethink the general SDS structure is
BJ0408 - counter-productinve in my opinion. We don't have to be a slave
BJ0409 - to it, but opting for unlimited generality is also overkill
BJ0410 - unless the resulting elegance buys us something. An SDS record
BJ0411 - has a unique identifier of <User ID> YYYY-MM-DD HH:MM:SS -- A
BJ0412 - user ID and a 1-second resolution timestamp. The current
BJ0413 - system has only 2-digit years. We eventually wnat to represent
BJ0414 - dates BC. This identifier can be turned into a filepath in any
BJ0415 - way that makes sense. SDS makes the time into the file name
BJ0416 - and uses each of the other fields in the identifier as a path.
BJ0417 - I see no problem with this as a starting point unless you
BJ0418 - really intend to read the entire thing into memory at once --
BJ0419 - an idea that doesn't thrill me. ref DRT 2 6U69
BJ0421 - ..
BJ0422 - Gary concurs with Morris' comments earlier today on making SDS records
BJ0423 - separate files, per above. ref SDS 0 TM6U This follows up the meeting
BJ0424 - on 071212 discussing design of SDS records. ref SDS 31 0593
BJ0426 - ..
BJ0427 - Gary's analysis of SDS as having invented an effective "wheel" for
BJ0428 - Knowledge Management, Communciation Metrics, and intelligence support,
BJ0429 - shown by scope in NWO, ref OF 13 A56M, and so should be "reinvented"
BJ0430 - slowly, aligns with Jack Park's discussion on 070913, ref SDS 27 YN4H,
BJ0431 - applied for the record on 071106 ref SDS 29 OS6M, and considered again
BJ0432 - on 071113. ref SDS 30 W889
BJ0434 - ..
BJ0435 - Gary's letter to Morris continues...
BJ0437 - 11. Recognize that is is possible to have records for more than 1
BJ0438 - user on a single machine and to link to a record for another
BJ0439 - user. Rod and I do this all the time. Given that reading all
BJ0440 - the records for all users into memory is not likely to be good
BJ0441 - idea, there is a need to reference a record not currently in
BJ0442 - memory and access it. Since that mechanism is necessary, why
BJ0443 - build additional mechanisms unless we need them. ref DRT 2 6U7F
BJ0445 - ..
BJ0446 - 12. While a lot of SDS is the result of constraints placed on the
BJ0447 - development environment, not all of the result need be
BJ0448 - discarded automatically. Separating record types (Diary,
BJ0449 - Contacts, Documents, etc.) makes sense. If I were using an
BJ0450 - RDBMS for storage the tablew would be separate. ref DRT 2 6U8E
BJ0452 - ..
BJ0453 - 13. The general notion of having an list of externally referenced
BJ0454 - "things" in the record and using that to generate links is a
BJ0455 - good idea even though it came out of the necessity of having
BJ0456 - external links within the record be visible in the text.
BJ0457 - ref DRT 2 6U8D
BJ0459 - ..
BJ0460 - 14. And so it goes. I would suggest giving consideration to each
BJ0461 - SDS element and asking whether the current form is useful
BJ0462 - rather than accidental before I tried to dream up something
BJ0463 - else. Where there are existing concepts and code, by all means
BJ0464 - use them. I am all for what makes sense, but concluding that
BJ0465 - whatever SDS does needs to be changed just because SDS is
BJ0466 - contrainted by its DOS roots is too broad a stroke. ref DRT 2
BJ0467 - 6U9A
BJ0469 - ..
BJ0470 - 15. == Doxygen Examples ==
BJ0472 - See............... ref DRT 2 6U4H
BJ0474 - http://www.stack.nl/~dimitri/doxygen/results.html
BJ0476 - [...above Morris reported accessing Doxygen.
BJ0477 - ref SDS 0 TM5V
BJ0479 - ..
BJ0480 - 16. Particularly
BJ0482 - http://xerces.apache.org/xerces-c/apiDocs/classes.html
BJ0484 - ..
BJ0485 - 17. I don't think that the markup clutters the code much as a lot
BJ0486 - of the information is taken from the code structure. If it is
BJ0487 - too cluttering, ref DRT 2 6U5H, then consider DocJet at
BJ0489 - http://www.talltree.com/home.php4
BJ0491 - ..
BJ0492 - It allows really clean documentation for certain. ref DRT 2
BJ0493 - Z86H
BJ0495 - ..
BJ0496 - What is the difference between "clean documentation" and SDS
BJ0497 - documentation for engineering management discussed above? ref SDS 0
BJ0498 - Y29I
BJ0500 - ..
BJ0501 - Gary's letter to Morris continues...
BJ0503 - 18. == Awaiting First Cut Conceptual Design ==
BJ0505 - Once we have a first cut at a conceptual design, we can discuss
BJ0506 - what makes sense in terms of specific mechanisms, tools and
BJ0507 - existing code. ref DRT 2 6U5G
BJ0509 - ..
BJ0510 - [On 080104 Morris considers switching to Java for
BJ0511 - programming XML design of SDS Windows application; expects
BJ0512 - to have initial screens in a few weeks. ref SDS 34 OM6Y