Looking for a textmode ui ...
in [TCL]
|
Prev: Postgres
Next: Tcl_AsyncCreate and Wish
From: prefect on 11 Jan 2010 01:08 On Jan 9, 9:42 pm, Helmut Giese <hgi...(a)ratiosoft.com> wrote: > who in the wolrd wants this??? Well, somebody who is writing a Virtual Appliance Controller to do all required system configuration for a Linux-packaged appliance to run on e.g. a VMware (consider deploying a complete Web-Shop with some button clicks at home, or a DB complete with backup, oder a ...). This somebody would write the appliance controller as web-application- server, which does not help a lot when network is down or not applicable for some reason (like security). So options are: - write text mode client which appears to be tough. I hoped to be able to do that straightforward, but it turns out to be not too easy. Since dBase/Clipper/Harbour the world has forgotten about the console and dialog/whiptail are not really the answers to my problem I had to admit quite early in the project - setup a minimal X environment wasting quite alot of diskspace fiddling around with a minimal windowserver and either a Prism or a firefox in kiosk mode, pretty nice as it delivers a professional look from the first minute but for remote administration not too comfortable. textmode is a lot faster. But on a limited X environment I'd also have Tk. First option would be stylish: cover textmode, Tk and Web UI from the same application. Second is the easy way out. I'll have to think a lot about this. But in the end, it looks like taking up the X way out of the problem. Thanks anyway!
From: Uwe Klein on 11 Jan 2010 03:00 David Gravereaux wrote: > The term package in Tcllib doesn't work on windows. It's a real shame. > It doesn't work because the windows console isn't ansi capable. what did ansi.sys do ? uwe
From: David Gravereaux on 11 Jan 2010 04:50 Uwe Klein wrote: > David Gravereaux wrote: >> The term package in Tcllib doesn't work on windows. It's a real shame. >> It doesn't work because the windows console isn't ansi capable. > > what did ansi.sys do ? > > uwe That's DOS --
From: Uwe Klein on 11 Jan 2010 05:12 David Gravereaux wrote: > Uwe Klein wrote: > >>David Gravereaux wrote: >> >>>The term package in Tcllib doesn't work on windows. It's a real shame. >>> It doesn't work because the windows console isn't ansi capable. >> >>what did ansi.sys do ? >> >>uwe > > > That's DOS isn't that at the core of windows when you take off the shiny paneling ;-? uwe who took the "L" OS upgrade after win3.1 ;-)
From: David Gravereaux on 11 Jan 2010 05:39
Uwe Klein wrote: > David Gravereaux wrote: >> Uwe Klein wrote: >> >>> David Gravereaux wrote: >>> >>>> The term package in Tcllib doesn't work on windows. It's a real shame. >>>> It doesn't work because the windows console isn't ansi capable. >>> >>> what did ansi.sys do ? >>> >>> uwe >> >> >> That's DOS > > isn't that at the core of windows > when you take off the shiny paneling ;-? No, it isn't. DOS applications run within the ntvdm that then translate the opcodes to windows calls within kernel mode. Any windows console app needs to call the appropriate function to move the cursor, change text color, etc.. If you do write the sequences directly, all you'll get is the text of the sequence on the screen, not the action intended. To add ANSI support, one must parse the string for ANSI escape sequences and apply the actions oneself using the Console API. For example, if you pull out \e[1;31m from your text stream on the way to a Console for display, you'd read that to mean change the foreground color to bright red and do so with something like this: foreground = FOREGROUND_RED|FOREGROUND_INTENSITY; SetConsoleTextAttribute(ConOut, background|foreground); |