J. Niemi and Jim Andrews.
Lataa lähdekoodi (42 kt). Suomennos englannista Terhi Hannula ja Marko
Niemi. Ohjelmointi Marko Niemi ja Jim Andrews.
Suomenkielinen versio löytyy myös Nokturnosta
From: Jim Andrews
Sent: November 22, 2006 11:44 PM
To: Marko J. Niemi; Dan Waber; Geof Huth; Lionel Kearns
of First Screening? In particular,
I'm wondering if you had to look at the code itself, or if you just eyeballed
the emulated version carefully, or made a movie of it
so as to examine it in stop-frame, or what. Because it's so bang
on. How'd you do it?
Also, I gather there were a couple of iterations in
How did that go?
From: Marko Niemi
Sent: November 23, 2006 1:41 PM
To: Jim Andrews; Dan Waber; Geof Huth; Lionel Kearns
Hi Jim and others,
the original BASIC code as possible; for instance, the 'Print(vtab, htab,
PRINT "<TEXT>"' lines in BASIC (VTAB and HTAB define the
is at (0,0) whereas in BASIC it's at (1,1)).
SPEED variables have their equivalents
in 'pause()' arrays (SPEED=255 is
the fastest tempo in BASIC and SPEED=0 probably the slowest, whereas in
the 'Home()' function clears the screen the same way as the HOME command
But then there were parts in the BASIC code, that don't have their
most notable example being the flushing/flickering effect at the bottom
line in the 'SELF-REFLEXIVE 2' piece for inctance. That was translated
simply by swapping the 'THE BOTTOM LINE IS WHERE CHANGE IS' line and an
empty line in rapid succession. In the 'CONSTRUCTION ONE' piece, the
flickering effect at the bottom line seemed to vary a bit from reading to
by choosing at random the moments when the TOWER word flashes at the
it was pretty much about tweaking and tweaking tempos of each piece and
line/word/letter in each piece, and watching the emulator version and the
emulator version as possible.