How This Story Was Made

What pulls memory and energy to making a bridge story?
Perhaps it's those deals that just won't go away.
Perhaps it's a lesson learned that suggested that today I'm less stupid than yesterday I was.
Perhaps it's a standard breach or a new line on an old standard not shared explicitly with countless partners.
"There's the standard now. Obey it, contest, send back or ignore."
So often last the choice.

If vivid enough, perhaps writing it out gets it out of mind and might be something.
Sometimes each and every card is explicit.
Sometimes it's just the idea of a hand pattern.

Of late is the idea of developing a javascript function that interacts with an array to assign to such as "x"s in an input line the leftovers of spot cards not assigned.
It's somewhere in there. I can't remember where it is...which file as a subroutine.
Maybe it's mostly there somewhere and just needs to be explicitly remembered...like it's lurking in some dusty corner for keeping open the multi lane highway...I wish.

With the tools I have, some of which I've developed, I need an input line to start after a diagram.

        North

        S:a
        H:
        D:
        C:

West            East
S:              S:
H:b             H:
D:              D:c
C:              C:

        South
        S:
        H:
        D:
        C:d

(Internet Explorer and Javascript are necessary to continue and assumed)

One hand can be extrapolated(?) from the other 3, so from:
input("a...,.b..,..c.,...d")
results eventually automatically the idea
input("a...,.b..,..c.,...") is almost right...sort of right.

From this folder there is a file
entry.htm
that is fed from an data entry input file
entry.js
that must first be filled with input lines, such as the example above.
Instructions are within that file.

After that input is amended and saved, entry.htm is reloaded/refreshed.
Each deal number on that page is a link.
Click that link and you'll be sent, at least on my computer, to:
handTEMPLATE.htm#1z2231031330120300121100002223203112133332212130213001
which is basically just
handTEMPLATE.htm
that has been fed data via the page call that fills data containers that eventually formats the deal diagram.

There is an auction diagram just below the deal diagram.
Default values from within handTEMPLATE.htm are developed and presented via Javascript.
One can enter the auction that occurred!:
In the address bar of
handTEMPLATE.htm#1z2231031330120300121100002223203112133332212130213001
the cursor is placed after the "z" following the "#" sound:
1z2231031330120300121100002223203112133332212130213001
after a
1S P P P
auction becomes
1z1sppp2231031330120300121100002223203112133332212130213001

Hit keyboard’s "ENTER" (or failing that browser’s "REFRESH").
That calls
handTEMPLATE.htm#1z1sppp2231031330120300121100002223203112133332212130213001
The auction diagram below the deal diagram should reflect the input.
Clicking the "Show Code" button then develops "hard code" for cross-browser compliance.
That code is or should be highlighted.
Copy it.

Click the dynamically generated link below that form text box labelled
"to .htm file not yet there".
Paste what you've copied in as that page's source code.
Save and launch that page in IE.

Of course all work must be done respecting relative directory. (Suit symbols in an "images" folder, etc.)

Additional Notes:

Download, unzip and amend the rights free (except the images, get your own suit symbols) zip folder here.

If entering an entire evening's hands, there should be an auto-rotate function to make South declarer and resetting the compass directions and vulnerability differences, if any.
That will result in directions that conflict with originals if referencing hands via deal numbers.
An alternative is to also have, if deal 8 rotated clockwise 90 degrees, then instead of 1z1sppp2231031330120300121100002223203112133332212130213001
where the first number is "1", then of rotation options numbering 3: I= 1/4 rotation, II= 2/4 rotations and III for 3/4 rotations, perhaps best just prior the ‘z’.