Viktor
Again I say I agree with your view point.
Long back, perhaps 2002, I initiated a lot of
message about this very fact, on xHarbour NG,
to streamline all WINAPI functionality in one
common library. At that moment What32 was
just came into being. I was puzzled and
wondered why everyone is writing his own
WINAPI modules, What32, HWGUI, MINIGUI,
the then WHOOPGUI, and a lot more.
Moreover I had requested all Windows developers
to create a common API lib with a distinct namespace,
OR to modify their libs to distinct name spaces,
to make all of them usable in every application,
but nobody cared. So I gave up. I changed namespace
of What32 and kept it as local repository.
This is such a cheos that we are unable to use
finest of all API developers in a single application, a pity.
Now as you have raised this topic again, I propose next
logical evolution as :
Higher level generic calls like:
HB_FUNC( API_SETBKCOLOR )
{
#if defined( HB_OS_WIN )
hb_retl( SetBkMode( ... ) );
#elif defined( HB_LINUX )
hb...
#endif
}
The upper level API will form the basis of portable GUI
in future.
May be I am not clear, but the idea can be discussed.
Regards
Pritpal Bedi
--
View this message in context:
http://www.nabble.com/SF.net-SVN%3A-harbour-project%3A-10164--trunk-harbour-tp21821360p21823009.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
