CONTACTS 

SUBJECTS
Citations Create Link SDS to SDS, macro 985
Design Concept
Concept Design Objectives
Headings Should Have Link Anchors When
SDS Linking System
SDS Records, Change to New Link Format

1008 -    ..
1009 - Summary/Objective
1010 -
101001 - Follow up ref SDS 7 0000, ref SDS 5 0000.
101002 -
101003 - Added security/privacy so Users can prevent specified records from
101004 - being opened on the Internet data base. ref SDS 0 2394
101005 -
101006 - Changed code so anchors can be on blank lines above headings rather
101007 - than emebedded in the heading. This works better with Web browsers.
101008 - Modified code that makes new tasks so that automatic link anchors for
101009 - sub-record headings will be entered in the description of the heading
101010 - and not on the "Follow up" line below the heading line. Discovered and
101011 - fixed a prior mistake that had been hidden by circumstance.
101012 -
101013 - The changes made today caused the Medit compiler to report warning on
101014 - running out of segment space.
101015 -
101016 -     [On 980325 unplugged some stuff to eliminate compiler warning
101017 -     space problem. ref SDS 14 2136]
101018 -
101019 -
101020 -
1011 -
1012 -
1013 - Design Analysis
1014 -
101401 -  ..
101402 - Testing Shows Link Anchors Work Best on Headings for Web Browsers
101403 -
101404 - The past few days of testing have shown that link anchors for follow
101405 - up lines, work better if they are part of a segment heading, assuming
101406 - the link is within a few lines of the heading. ref SDS 11 1444
101407 -
101408 - Follow up linking for segment headings was created last year. Concepts
101409 - and objectives are at ref SDS 3 3157,
101410 -
101411 - Experience the past week using IE and Netscape Web browsers to test
101412 - the SDS HTML interface indicates that sales appearance and utility
101413 - support making this change. ref SDS 11 1444, supplementing work on
101414 - 980318. ref SDS 10 2295
101415 -
101416 - We have therefore begun putting anchors in headings, so that the
101417 - headings will appear on the Web browser screen for context on subject
101418 - content, when a link is accessed in the browser.
101419 -
101420 - SDS already positions anchor lines in the middle of the screen so we
101421 - can see the headings and context, but Web browsers are putting the
101422 - anchor lines at tos, so the headings are not visible, if the anchor is
101423 - on the line below the heading line.
101424 -
101425 - We can solve this by putting anchors in the headings.
101426 -
101427 - Anchors on headings that are not underlined, are okay.
101428 - ..
101429 - The problem is when a heading line has an anchor and is
101430 - underlined.  We could eliminate underlining headlines, since the
101431 - underlines are removed for publication on the Web because the lines
101432 - are distinctive enough with the current format of changing to a
101433 - proporational font and color red.
101434 -
101435 - In SDS, we can alternatively identify headings with color 3, but
101436 - underlines look better and are less distracting in creating text on
101437 - line.  In other words, the underlines seem easier to use, or are more
101438 - conducive to effective writing, which is a main purpose of the record.
101439 -
101440 - This may be a remnant of DOS and my imagination.
101441 -
101442 - No there is another reason for underlining of headings.
101443 -
101444 - Underlines are the flag that tell the make-new-task function to create
101445 - automatic links between major headings.  We do not use the color #3
101446 - function for this because it is designed to allow the user to randomly
101447 - tag something for inclusion in the record summary as a pointer to text
101448 - apart from the formal heading process.
101449 -
101450 - Another solution would be to move anchors entered below heading lines
101451 - to the heading lines during the HTML process executed by 070405.
101452 -
101453 - If anchors are on heading lines, we need to change the code in 004 so
101454 - they are used for the automatic link created in the Schedule follow up
101455 - record.
101456 -
101457 -
1015 -

SUBJECTS
Design Concept
Headings Should Have Link Anchors When
SDS Linking System
SDS Records, Change to New Link Format
Privacy, Security
Citations, Open SDS records references in

1709 -
170901 -  ..
170902 - Option to Turn Access Off to Web Page Link for Privacy/Security
170903 -
170904 - We have developed Alt F10 on the record description as a way to avoid
170905 - having an entire record published on the Web site. ref SDS 8 2480
170906 -
170907 - Today we add a feature to suppress access to a linked record. ref SDS
170908 - 0 6313  This was initially considered on 980315. ref SDS 9 0903
170909 -
170910 - Using Sds instead of SDS will permit access to a link in SDS, but will
170911 - not be converted to a link for Web pages.
170912 -
170913 -     Actually decided to unplug this for now, because Medit is
170914 -     returning a compiler warning.
170915 -
170916 -     No decided to keep it and instead unplugged the few remaining
170917 -     Schedule task tense conversions in 000005. ref OF 2 6069
170918 -
170919 -
170920 -
170921 -
1710 -

SUBJECTS
Citations Create Link SDS to SDS, macro 985
Position Opened Rcd with Anchor Near TOS

1905 -
190501 -  ..
190502 - 000006 - Avoid Justifying Link Anchor Lines on Headings
190503 -
190504 - Follow up ref SDS 7 0990, ref SDS 5 2353.
190505 -
190506 - In order to put link anchors on headings that are underlined, we need
190507 - to change the code so when a link is created the line is not justified
190508 - because that jumbles up the thing.  See analysis above. ref SDS 0 1664
190509 -
190510 - Line 1795, ref OF 3 4820 -label sdsJs added code to look for a line
190511 - under the current line, which would signify an underlined heading.
190512 -
190513 - In that case the line will not be justified.
190514 -
190515 -        [On 980325 unplugged some stuff to eliminate compiler warning
190516 -        space problem. ref SDS 14 2136]
190517 -
190518 -
190519 -  ..
190520 - 000006 - Open Record with Link Anchor Line Near TOS
190521 -
190522 - Since we are now linking mainly on the segment header, I want to shift
190523 - the data up the screen a few lines so the actual substance of the link
190524 - is in the center of the screen, and there is more context for the eye
190525 - to absorb.
190526 -
190527 - Line 1600, ref OF 3 4072, -label setupQ move the stuff up 3 lines.
190528 -
190529 -     [On 980501 moved this code to 0121, and moved the target position
190530 -     to tos, instead of putting in in the middle as was done previously
190531 -     for context. ref SDS 15 2685]
190532 -
190533 -
190534 -
1906 -

SUBJECTS
Citations Create Link SDS to SDS, macro 985
Flag SDS Records Private, No Web
SDS Linking System
Privacy/Security
Privacy Security Restricted Links HTML

2308 -
230801 -  ..
230802 - 000006 - Added Access for Sds in Link Spec
230803 -
230804 - Follow up ref SDS 8 2480.
230805 -
230806 - Line 1400, ref OF 3 5618, -label rTyp added a conditional so we can
230807 - open an SDS citation, if the string is
230808 -
230809 -                        Sds
230810 -
230811 -     ...per analysis on 980315, ref SDS 9 0903.
230812 -
230813 -     This supports privacy/security by enabling authors to suppress
230814 -     access to a Web page from a linked source record.  The code in
230815 -     070405 will not recorgize SDS and so will not convert the link.
230816 -     Since SDS will now open it, we have an alternative that lets the
230817 -     originator of content control source access on the Web, while
230818 -     maintaining access in the SDS program.
230819 -
230820 -
230821 -
230822 -
2309 -

SUBJECTS
New Task or Link records
Planning, Concept

2505 -
250501 -  ..
250502 - 004 - Use Heading Line for Link Anchor Automatic Follow Ups
250503 -
250504 - Follow up ref SDS 6 2955.
250505 -
250506 - Linking sub-headings was created last year. ref SDS 3 8940
250507 -
250508 - Until today, the code would enter automatic link anchors to new
250509 - records for each heading on the line below the heading line if there
250510 - is one. Today, I am changing this so link anchors are now above the
250511 - heading line as part of the heading description.
250512 -
250513 - Line 890, ref OF 1 0613, -label lnkthm, created this new segment of
250514 - code today, per ref SDS 0 3603
250515 - ..
250516 - Line 1125, ref OF 1 2150, -label xx98 this is a code loop the
250517 - scrolls the file up to find the heading underline and then putting an
250518 - anchor on the line below. It then justifies the para.  Today, we will
250519 - change this process.
250520 -
250521 - We will instead, put the anchor on the top heading description line
250522 - above the heading and will not justify.  So if there is one heading
250523 - description the anchor will be inserted in front of it, and if there
250524 - are 3 heading description lines, then the anchor will be inserted in
250525 - front of the first one, so that when the citation is called, all
250526 - heading lines will be visible.
250527 -
250528 -     [On 980501 changed this code just a bit to put the anchor on a
250529 -     blank line above all of the heading description lines, instead of
250530 -     putting it in front of the description line. ref SDS 15 2426]
250531 -
250532 - We can unplug code that investigates for outline text below a heading
250533 - line, since now the link is on the heading and not not the Follow up
250534 - line below it.
250535 -
250536 - Line 1170, ref OF 1 1620, -label linkk this is where the anchor
250537 - string is created.
250538 -
250539 - Line 1185, ref OF 1 5004, -label yy77, this is the standard link
250540 - process that splits the line enters the anchor and justifies the para
250541 - to put it back together.  We do not want to justify these headings,
250542 - because it jumbles the heading line.
250543 -
250544 - Line 1235, ref OF 1 2029, -label adjFU this is where follow ups are
250545 - posted.  Not sure how it works on this matter just yet.
250546 -
250547 - Line 1270, ref OF 1 1365, -label adjFU this is were Follow Up is
250548 - revised to get the anchor string for the old record that will be
250549 - removed to make a new record.  Added code to do an up for headings,
250550 - actually this may be all we need.
250551 -
250552 -        I will never understand what is going on here (but take heart,
250553 -        prior work was useful today to fix a mistake). ref SDS 0 1328
250554 -
250555 -
250556 -
250557 -
2506 -

SUBJECTS
Convert 0 Links to SDS Ref Links

2604 -
260401 -  ..
260402 - 004  Fixed Error in Converting Current "0" Links
260403 -
260404 - Line 970, ref OF 1 1958, -label lpSDS0 the code here seems messed up.
260405 -
260406 - It is supposed to convert local links to trans-record links, but it
260407 - does not seem to be working correctly.
260408 -     ..
260409 -     The problem turned out to be that I changed a series of
260410 -     counters in 004 which are mainly used about line 1030, ref OF 1
260411 -     4885, -label curLin, for the reasons at ref SDS 6 2955.
260412 -
260413 -     It appears I made a mistake and did not change the code for
260414 -     counter 80 in one code string.  For some reason the live code in
260415 -     sd 03 004 was not updated when I made this change last November,
260416 -     and so it seems to have been working all along, even though the
260417 -     development code has this mistake.
260418 -
260419 -     This evening when making the change at ref SDS 0 3793 in the
260420 -     development code, the process of converting it to live code
260421 -     brought the error into the live code.
260422 -
260423 -         Basically, I previously made two mistakes, and the second one
260424 -         prevented the first from impacting performance, which masked
260425 -         the error.
260426 -
260427 -         This evening, the prior error became manifest because of
260428 -         unrelated activity.
260429 -
260430 -     Since I had copied the development code to the live code on CPU08
260431 -     which is the main work computer, I had to get the prior code from
260432 -     CPU 09.  Careful checking indicated that only counter 80 seems to
260433 -     have been erroneously overlooked.  I checked the other numbers and
260434 -     cannot find any evident error.
260435 -
260436 -
260437 -
260438 -
260439 -