>Except when UNIX people refer to "console", it's almost always as the
>keyboard and screen physically attached to the computer and never as
>where a process gets its input and output. So you never want to do
>anything specific to a "console". This terminology is more commonly
>(and incorrectly) used on Windows to refer to the character-based
>input/output from DOS applications. But MetaCard support for this on
>Win32 an issue there because of the forced graphical/console
>dichotomy.
Scott,
being UI-crazed myself I don't mind if you leave out "console". If it's
really just a Unix feature, I understand that it's not documented in a way
so people of other platforms understand it. If "stdin" and "stdout" are
commonly used terms in Unix, that's of course the better choice.
>So is CGI, and compatibility with the terminology used for that is far
>more important than trying to "disguise" it by giving it non-matching
>"user friendly" names. Allowing the full names sounds like a good
>idea, though.
Since the app I'm working on is a text-only screen-centric program, not a
CGI, should I invent my own syntax instead of using stdin/stdout, to make
sure I don't water down CGI terminology, or should I stick with this? I
don't want to hurt xTalk in any way by introducing duplicate syntax, but
mis-using existing stuff for different uses might be even worse.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
