In my opinion gtwvt will be very useful for harbour user in windows 32 because allow a easy switch cui gui xbase++ class & gtwvw is also a important bridge for Xbase developer and xharbour+gtwvw No support for ,windows ce,windows 64,linux but maybe wine ..is similar situation to gtxwc,gtwvw a documentation will help user undestrand the non portable library
2009/3/26 Viktor Szakáts <[email protected]>: > Thanks Angel. I agree with you. > If we indeed think this direction seriously we could make > some moves to separate portable and non-portable libs > from each other. Something should count as portable if > at least Windows (including x86, x64 and wince), > Linux and Darwin are supported. If more platforms are > supported, good, but if some of these are not, we should > consider handling these differently. Unfortunately the > decision cannot be that automatic, we need to make exceptions: > hbwin is a common need for Windows users (but we should > have *only one* Windows specific lib, no separate hbole f.e.), > rddads is also a common need, and it's not supported outside > win/linux. > After evaluating our contrib list, I could only name a few > ones which would be dropped by above rules, the most > problematic and less portable specific lib is gtwvg. I hope > Pritpal can save the Xbase++ layer of it, so it can be useful > for QT, but otherwise I'd like to propose to do something > about it, like moving it to examples, or opening a separate > SVN project for it. The rest of libs is about okay, maybe only > hbblat stands out as Windows only, albeit it's the only way > to send e-mails from a Windows system and the code very > simple (only one C function) and unobtrusive, so I think it > should stay. hbole integration should be done ASAP. > We also have a few places where portable libs use platform > specific features: hbct, hbfbird, hbfimage, hbmysql, hbnf, hbodbc, > hbssl, xhb. I'll try to evaluate all these, and also ask for help > from other to eliminate them. (by using Harbour API calls, or > other means). > Brgds, > Viktor > On Thu, Mar 26, 2009 at 4:34 PM, Angel Pais <[email protected]> wrote: >> >> Hello Viktor: >> >> Here's an outsider's point of view and vision about harbour. >> This is a multiplattform compiler so in my personall point of view the >> only c commpiler that should be guaranteed to work flawless is gcc/mingw. >> Other compilers should be responsibility of special distros supporters. >> Also hbmk2 should be the only and official way to compile and build >> everything, from core to utils to samples. >> >> JMHO >> Angel >> >> PD: Same about gui. xbgtk and or QT should be the only ones officialy >> supported by this project. >> >> >> Viktor Szakáts escribió: >>> >>> Hi agree about importance of give a choice and agree mingw/msvc path >>> can we follow Minigui that include harbour & MinGW to be ready to use >>> for windows platform? >>> >>> >>> I don't know MiniGUI, so I cannot tell. >>> >>> What is possible though is to provide such a binary distribution which is >>> based on MinGW, contains MinGW binaries and also includes MSVC libs. Such >>> package is a self-contained one being able to create executables without any >>> external tools, it also has GNU Make, and it's also possible to use it with >>> MSVC and even POCC if someone has these installed. >>> >>> I'll check if I can make hbmk2 detect such embedded mingw installation >>> automatically. >>> >>> Such package is a 42MB .zip, and if this seems to be okay for everyone >>> such package may replace our current compiler dependent distros, by the >>> simple names of: >>> >>> harbour-1.1.0-win-x86.zip >>> harbour-1.1.0-win-x86.exe >>> harbour-1.1.0-win-x64.zip >>> harbour-1.1.0-win-x64.exe >>> harbour-1.1.0-wince-arm.zip >>> harbour-1.1.0-wince-arm.exe >>> >>> I think such distros would send a much better message towards users and >>> give them a much better service. Of course, all BCC/owatcom users will have >>> to migrate to above proper compilers to be able to follow. >>> >>> Opinions? >>> >>> Brgds, >>> Viktor >>> >> >> _______________________________________________ >> Harbour mailing list >> [email protected] >> http://lists.harbour-project.org/mailman/listinfo/harbour > > > _______________________________________________ > Harbour mailing list > [email protected] > http://lists.harbour-project.org/mailman/listinfo/harbour > > -- Massimo Belgrano _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
