Hi agree for xhgtk in contrib I Hope that HBGTK follow t WvgParts class modal (GTWVG) compatible with Xbase++XbpParts and implement also a GT If Following the same class structure the make the code portable. New()|Init() / Create() / Configure() / Destroy().
In this area also QT seem interesting but is not present any wrapper library afaik 2009/3/12 Viktor Szakáts <harbour...@syenar.hu>: > FWIW, IMO it would also be very nice to see xhgtk integrated > under the Harbour contrib tree. > For sure this is much more a decision from the xhgtk authors, > than us, but it would be nice, and probably the best choice > towards portable GUI. > xhgtk has a big bunch of 3rd party dependencies, but probably > even this could be solved using existing Harbour techniques. > As for xhb compatibility, it probably can be solved using > conditional code and the GNU Make system now is pretty much > universal, maybe some helper script can be added for xhb > users. > Just thoughts. > Brgds, > Viktor > > On Sun, Dec 7, 2008 at 10:15 PM, Bill Smith <hb...@sbcglobal.net> wrote: >> >> Thank You Lorenzo, you are absolutely correct, simplicity == elegance >> is critical. This is not only the case for today, but down the road >> when changes and incompatibilities could make tracking what library and >> what combination of instructions or options or commented instructions in >> source might be needed to compile a harbour .prg file nothing short of >> the spaghetti that once plagued procedural programming. >> >> Right now, a ? "hello, world" program build from "hbmk hello" at best >> yields a blank screen in a terminal window on both SuSE Linux and >> Windows XP. >> >> Bill >> >> >> >> On Sun, 2008-12-07 at 21:30 +0100, Lorenzo Fiorini wrote: >> > On Sun, Dec 7, 2008 at 4:54 PM, Przemyslaw Czerpak <dru...@acn.waw.pl> >> > wrote: >> > >> > > BTW do you want to integrate XHGTK with Harbour contrib? >> > > Don't you think it will be better to keep it as separate >> > > project and only add some integration tools. >> > >> > You're right but as we've seen lately it's not easy for a newbie to >> > get it built and this gets even worst if you plan to have ti for Lin, >> > Win and OSX. >> > >> > There are many build.sh, makefiles, envvar to set and a newbie is >> > always in front of many different options. >> > >> > Under Win or OSX, getting a working setup that uses some contribs like >> > gd or mysql requires many steps. >> > >> > I'm trying to create the easiest possible setup and to define the >> > "defaults" that hide the differences between the 3 OS that I support >> > and document where to get the dependencies and how to install them. My >> > goal is to remove every "misleading" doc or examples for this I'm >> > thinking to start a new project that offer a "distribution" ready to >> > use if the defaults will be accepted. >> > >> > Actually I can build under Lin and Win without setting any envvar ( >> > using /opt/harbour as default install path since it's usable in all >> > the 3 OS ). I'm documenting how to setup external dependencies for >> > zip, gd, odbc, curl, pgsql, mysql, xhgtk. >> > >> > I plan to provide a skeleton Makefiles to create binaries, libs, cgi and >> > hrb. >> > >> > F.e. In the makefiles I've replace HB_ARCHITECTURE with: >> > >> > ... >> > OS=$(shell uname -s | tr -d "[-]" | tr '[A-Z]' '[a-z]') >> > ... >> > ifneq (,$(findstring mingw32,$(OS))) >> > ... >> > ifneq (,$(findstring linux,$(OS))) >> > ... >> > ifneq (,$(findstring darwin,$(OS))) >> > >> > 0but the differences about the use of the shared libs between Lin and >> > Win are still present. >> > >> > F.e. to link against gd and pgsql you need to use sth like: >> > EXT_LIST=$(HARBOUR_DYN_DIR)/hbgd.dll /opt/local/bin/libgd2.dll >> > $(HARBOUR_DYN_DIR)/hbpgsql.dll /opt/pgsql/bin/libpq.dll >> > >> > What do you think about adding switches like: -gd-shared, -gd-static, >> > -pgsql-shared, ...? >> > >> > BTW I've few showstoppers: >> > >> > 1 - in hb-func.sh using hb_exesuf="exe" prevent to create cgi binaries >> > called myprog.cgi. >> > I've set it to "" like in linux but then the strip step complains. So >> > far I couldn't find the right solution ( both 1.0.1 and 1.1 ) >> > >> > 2 - gtwvt is "broken" in the sense the fontsize selection doesn't work >> > anymore see my msg "gtvwt problem" ( 1.1 only ). >> > What do you think about creating a GT reference test so that every GT >> > change can be checked against it? >> > >> > 3 - gtxwc doesn't support palette definition and HB_GTI_CLOSABLE. >> > Actually I'm hacking the colors constants and I've commented out >> > "s_atomDelWin" message. >> > >> > Could you kindly give me some hints? >> > >> > best regards, >> > Lorenzo >> > _______________________________________________ >> > Harbour mailing list >> > Harbour@harbour-project.org >> > http://lists.harbour-project.org/mailman/listinfo/harbour >> >> _______________________________________________ >> Harbour mailing list >> Harbour@harbour-project.org >> http://lists.harbour-project.org/mailman/listinfo/harbour > > > _______________________________________________ > Harbour mailing list > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour > > -- Massimo Belgrano _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
