#117672 - 2004-04-09 10:50 PM
Back to the future...
|
Stevie
Starting to like KiXtart
Registered: 2002-01-09
Posts: 199
|
With the prevalence of KiXforms and IE GUIs, do we really need the Console API functions Box, Color, etc.? Those functions effective break kix's stdout. IMHO, choosing between stdout and the console api stuff, I'll take stdout every time.
If I want to create a rich GUI experience via kix, I'm using kixforms, not prettifying a console box. Maybe I'm just out of the loop here but how many people actually use color, box, at, big, etc. to display real information to the user?
Having said that, what are the chances that Ruud will deprecate the console commands and go back to using stdout for console display?
_________________________
Stevie
|
Top
|
|
|
|
#117677 - 2004-04-13 08:34 PM
Re: Back to the future...
|
ShaneEP
MM club member
Registered: 2002-11-29
Posts: 2125
Loc: Tulsa, OK
|
No burden on me...Just not as pretty for the users...
Besides....Hopefully we will be going to SMS soon so scripting the patches will no longer be necessary.
|
Top
|
|
|
|
#117678 - 2004-04-14 10:19 AM
Re: Back to the future...
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
Quote:
But for the quick one-liner, would not having color and AT be a burden?
Probably not, but is there any really good reason to remove these features? The console will still need to be present to display simple text, so there is not likely to be much benefit from stripping out things like AT and COLOR.
Having IO redirection (both IN and OUT) would be a great feature, but there is no need to remove existing functionality to do it. A command line switch and/or SetOption() to switch output to "raw" mode should do the trick and keep KiXtart backwards compatible.
Another (better?) option would be to allow OPEN(), READ(), WRITE() to operate on standard in, standard out and standard error streams. In fact, the more I think about it the more I like this solution. These standard file descriptors could either be open when the script starts, or be opened by a special file name: Code:
; Open input, output and error pipes $fdSTDIN=FreeFileHandle() $=Open($fdSTDIN,"STDIN:",2) ; Standard input in read mode. $fdSTDOUT=FreeFileHandle() $=Open($fdSTDOUT,"STDOUT:",4) ; Standard output in write mode. $fdSTDERR=FreeFileHandle() If Open($fdSTDERR,"STDERR:",4) ; Standard error in write mode. ; No standard error stream - Windows9x maybe $fdSTDERR=$fdSTDOUT EndIf
RedirectOuput() could also be enhanced to accept a stream name in a similar way.
|
Top
|
|
|
|
#117679 - 2004-04-14 03:03 PM
Re: Back to the future...
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
It is interesting. I brought this up the other day with my Manager that I could hide the execution of KiXtart. He did not like that as "he could see the progress of the script." I did tell him if I introduce an error, KiXtart will still tell us that. This has also been a question I have asked ScriptLogic Tech Support as well. They say that they have to keep their Batch/Splash due to 9x clients. My response to that was we got rid of our 9x clients at least two years ago. I asked how about turning this on or off for a given install. They just did not seem to hot on that idea.
Kent
|
Top
|
|
|
|
#117682 - 2004-06-07 06:48 PM
Re: Back to the future...
|
PRandal
Fresh Scripter
Registered: 2002-07-17
Posts: 28
|
What's wrong with
Code:
$=SetOption("ASCII","ON") $=SetOption("WrapAtEOL","ON")
to direct screen output to stdout?
|
Top
|
|
|
|
#117684 - 2004-06-08 01:22 AM
Re: Back to the future...
|
PRandal
Fresh Scripter
Registered: 2002-07-17
Posts: 28
|
Oh, arrogance is bliss!
it.kix: Code:
$=SetOption("ASCII","ON") $=SetOption("WrapAtEOL","ON") "Hellooooo"
And then, invoke via Code:
kix32 it.kix > it.txt
It'll be useful to somebody. It was to me, in the real world.
Sighing deeply.
Phil
|
Top
|
|
|
|
Moderator: Lonkero, ShaneEP, Jochen, Radimus, Glenn Barnas, Allen, Ruud van Velsen, Mart
|
0 registered
and 718 anonymous users online.
|
|
|