CCH: In an effort to 'guify' FAS4XHB.EXE, I wanted to retain the procedural approach (i.e no events-driven stuff)
I was advised by Ron Pinkas not to use gtwvw but to take a look at WVT & WVG
I found this interesting article by Clipper... Clipper...Contributor, Pritpal bedi of Harbour Project.
Response by Pritpal Bedi to a post dated 20th Nov 2007
entitled Gtwvt + Wvtgui = Gtwvg : xHarbour => Harbour
If used as pure console "NOTHING".
If used with GUI extensions, very appealing Windows screens without
sacrificing the Clipper syntax.
To have a bird's eyeview what we can achieve with GTWVG, visit:
http://www.vouchcac.com/ScreenShots/ScreenShots.htm
Though these screens are fairly old, the latest ones have toolbars etc too,
but even then you can have a fairly good overview. To just emphasize, this
lib does not change the way you write code, instead, provide mechanism to
enhance your code to give a GUI look.
This is one of my appln converted to GTWVG (Harbour) GTWVT+WVTGUI
(xHarbour).
Additionally GTWVG has a nice set of Wvt*Classes() which employ the common
event loop. You can create high performance dialogs with multiple Tbrowe,
Reads, Bitmaps, Buttons, i.e. all GUI elements you can think of.
More, you can open multiple pure Windows dialogs MODELESS or MODEL from
within your Clipper syntax.
I suggest you to experiment with xharbour/contrib/wvtgui/tests/wvtgui.prg to
learn more about these features. In future I will write a comprehensive
documentation.
If group agrees and someone more gifted developer join hands, these graphic
elements can be embedded with base GT to avoid additional code to be written
by the developer.
Based on GTWVG I am working on another libarry GTWVM ( Multiple Console
Terminal Driver ) just like in XBase++. There you can open multiple consoles
in an application containing its own GT and GUI elements and having its own
processing loop independant of others. It requires deep changes into GT core
code, which at the minimum needs a unique identifier for each GT command. I
have achieved a little bit but seems it is a long way to go, and perhaps, at
my own I cannot do everything. If group decided I can show a prototype of
what I am trying to achieve.
Hope you must be clear about the differences of GTWVT and GTWVG.
Regards
Pritpal Bedi, INDIA-USA
since 3 June 1996.
I use just a couple of WVT functions in my xHarbour app, works fine, but now I'm trying to make the same EXE have access to DLLs, and HbMake won't create the EXE.
ReplyDeleteIf I set only the WVT functions, HBMake creates the EXE normally, but it is not able to access DLLs via Hb_LibDo().
Now, if I try to use WVT together with the access to DLLs, HbMake refuses to create the EXE, pointing all WVT functions as "unresolved external"... ??
I use Xh 1.0.0 + BCC55. Also tried the last xH version, but I get the same problem.
Eolo (Brazil)