Hi Pritpal, > Though it compiles fine with current Harbour and possibly with -DUNICODE > also but still it may require an overhaul. The style is sephagatti as it > was started after my first encounter with xHarbour in 2002 and > when Augusto Infante and Andy Wos committed What32 library. > So it is not Harbour standards strictly. > > The library is heavily based on What32 which I have as unified with > this library with Wvn_* name space. As hbwin.lib has evoled to a > reasonable extent, many of the functions will have duplication > but because namespace is different, will not cause any harm. > > It also uses C Structures so again it does not adhere to Harbour's > philosophy. > > The areas of particular interest to users will be PageScript compatible > functions and PrintPreview mechanism which can be exploited > with gtwin also though these are more suitable for gtwvt and gtwvg. > Though there are a lot other convinient functions but probably > I think all can be done more or less with current Harbour. > > Few components I will have to pull out like Graphics and Charts > because the code was given to me by Augusto Infante and later > revised by Andy Wos and I do not know if I am permitted to publish > that as open source. > > Augusto or Andy, if you are reading this mail, please allow to do so. > > Also I wil pull-out CT3 compatible COM_* components as these are now > available with Harbour anyway and also due to fact that I had contributed > this library to xhb.com and my professional ethics do not permit so. > > Today, 17 May 2010, I have decided to put it under Harbour contribs. > But I want to retain vouch32 folder name in harbour/contrib/vouch32. > This is the only recognistion I need plus your willingness to polish > the code. I would have certainly be happy to polish it but due to > heavy involvement with hbQt+ direction, I cannot spare time onto that. > > If group is willing I can start the process under harbour/contrib/vouch32.
Thanks a lot for your offer. Unfortunately I'm not very positive about the inclusion in contrib, having went through all the trouble with WHAT32 in the past. Even with small Windows code, there is A LOT of work to make it compile (see service and MAPI support for two examples) and to make it work on all our supported environments and to level it to Harbour standards. It also has to be maintained by someone, otherwise it can easily become a build stopper (as was with WHAT32 and as is sometimes with GTWVG). Also Harbour contrib is already getting overbloated (both in terms of size and build-time), so for VOUCH32, I'd like to suggest to create hbmk2 make files for it and host it in another repository. I'm sure it will be much easier and most probably more convenient for everyone. I'd suggest to remove '32' from the name. In case of Harbour, I went to great pain to remove any "bitness" information from all the files, suggesting the portable nature of our (Windows) code. Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
