On Wed, Feb 11, 2009 at 4:55 PM, Appert, Kevin <kevin.appert_at_lmco.com> wrote:
> By the way, along with the legacy, modularity and portability I'd like to
> add two thoughts about screens. I always liked having shadows that I could
> blink to or put up on a second screen. Also, programmers who were beginning
> to learn their craft (trade? practice?) would find that they needed to
> trim their idea to fit into 16 x 64 and I like to think it must have helped
> some. Of course in the old PolyForth source there was at least one idea
> that was left on the stack and picked up a few screens later.

I'm well aware of the arguments for (and against) screens, but I came
down firmly on the side of ASCII files, despite the fact that I also
have a revulsion for any definitions over about a dozen words long. My
choice mainly hinged on convenience; I change code a lot, and it grows
and shrinks. I was able to work with screens, but I found the process
to be less cumbersome with ASCII files. Apparently, there were others
that agreed with that, because SwiftX now uses ASCII files.

--
Howard Lee Harkness
Pro-Count, Inc.
214 269-1171
----------------------------------------------------------------------
swiftx_at_forth.com          The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
For list command help, send subject "help" to swiftx-request_at_forth.com
Message archives are located at http://www.forth.com/archive/swiftx
----------------------------------------------------------------------
This list is a forum for SwiftX users.  For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------