Viktor Szakáts wrote:
Since we don't have plans (and it wouldn't sound too realistic
either on the mid-run) to implement XBP using alternative
portable GUI libs (like wx or GTK) inside the Harbour Project
repository, IMO for now it's safe to simply call it 'hbxbp', it's
also nice, clean, short and non-ambiguous. Later we can
switch to 'hbxbpqt' if we happen to develop other flavours
like 'hbxbpwx' or 'hbxbpgtk'.
So my vote: hbxbp
Amin!
So the roadmap looks like this :
harbour/contrib/hbxbp
xbpWindow.prg
xbpPartHandler.prg
...
...
xbpLast.prg
...
xbp.ch
gra.ch
...
All above files parts refer to functions in xbpGenric.prg
xbpGeneric.prg
xbpGenric.ch
The functions inside will call the underlying interface
library
in this case hbqt, in future : wx, xgtk, winapi, etc ?
Will use hbqt.lib currently then may be wx
The idea is to separate prg calling GUI code from API code.
Opinions?
Looks good. We can lift the 8.3 restriction for this lib too,
as it won't be built for DOS. If others agree.
Two things to focus on:
1) Only and only use the hbqt provided API in this library,
that means no local C code, no direct access to QT libs.
And also no reliance on other contribs, like hbwin, gtqtc,
xhb, hbct or any other. Harbour core stuff can be used,
naturally, except I guess any GT related stuff.
2) As close compatibility with Xbase++ as possible.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
