> Lorenzo Fiorini
> Inviato: sabato 24 aprile 2010 7.38
> A: Harbour Project Main Developer List.
> Oggetto: Re: [Harbour] Re: someone uses hbqt for "business" 
> applications ?
> 
> On Fri, Apr 23, 2010 at 8:34 PM, Pritpal Bedi 
> <bediprit...@hotmail.com> wrote:
> 
> I've nothing against hbqt.
> The discussion is about using it to create business apps and I pointed
> one problem: many here have a lot of C5x CUI code to convert and hbqt
> does not help.

I'm part of this people.
hbQt could be the best choice due to his multiplatform, rich and well
documented implementation, but the approach is very critical whan applied to
existing Clipper code.

> 
> > This is the main problem of
> > every GUI library. We tend to forget the basic differences of
> > CONSOLE and GUI way of programming flow - program controlled vs
> > user controlled. We can mimic the CUI calls to present the interface
> > but we _cannot_ mimic the CUI like behavior, viz., ReadModal().
> 
> Here I disagree.
> 
> I have a Fivewin version of my apps since 1998 and I'm still selling
> it. It has been relatively easy to reach the point where menus, forms
> and tbrowses are "shared" between the CUI and GUI. Clearly it required
> some classes, some PP and also some changes in the FW classes code but
> since FW has SAY/GET and TCBROWSE classes it was not so hard.
>
> Result: I can build the same app as CUI or GUI simply defining a
> __DOS__ or a __WIN__ macro at build time.
> 
> The main point is that FiveWin was "planned" as a convertion tool for
> C5x code while hbqt is a direct wrapper of C++ classes.
> 
> IMHO hbqt needs a "compatibility layer" towards C5x UI components (
> and it can't be XBP for the reasons I already explained many times
> before ).

You are right.
I agree with the "compatibility layer" as I used something similar to wrap
hwGUI objects to my Clipper framework and worked fine.
But I ask you for a reference to the thread about the XBP inconsistency in
this approach, or a summary of your thought about.
I'm very interested in use xBase Parts and, because I yet made a
compatibility layer for xBase++, I would know what part of the layer could
be critical in this approach whit Harbour.
TIA.
Maurizio

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to