How thin is D4GL client?

We are considering moving to D4GL to deploy both Windows and Web. How thin is the D4GL client? Does part of the D4GL code I write actually run on the client? or Does the D4GL client just handle the internal form display and internal structures need to display data? or Is the D4GL better likened to a X display where it really only paints pixels and relays mouse and keyboard input? TIA, TIM

> We are considering moving to D4GL to deploy both > Windows and Web. How thin is the D4GL client? > Very. We have not tried this, but you are even supposed to be able to use 386 PC's. The size of the executable (WTK.EXE) which runs on a Windows client is about 820K in version 3.0. > Does part of the D4GL code I write actually run on the client? > or > Does the D4GL client just handle the internal form display and > internal structures need to display data? > or > Is the D4GL better likened to a X display where it really only > paints pixels and relays mouse and keyboard input? > I believe the answer is somewhere between B and C. The D4GL code you write does not run on your client but it runs on your server (it is possible to setup a PC to act as both but you probably would not want to do this). The graphics server (WTK.EXE) which runs on the client processes TCL commands to create/manipulate graphical objects. I believe it is a little fatter than X in that it includes the communication middleware and a TCL interpreter...