Pritpal,
Many thanks for the info.
My question about the naming of source files, and functions, was
regarding:
contrib\gtwvg:
gtwvg.h
gtwvg.c
wvtcore.c
wvtutils.c
I was wondering if it could be:
wvgcore.c
wvgutils.c
?
Similarly I was wondering if it's possible for functions to be named
wvg_* instead of wvt_*?
[For prg callable functions I'd suggest a short term compatibility
header, with proposal for Developers to use Search & Replace for long
term correction.]
Ron
On Jun 28, 2008, at 1:23 PM, Pritpal Bedi wrote:
Hello Ron
> Pritpal, can you please explain which GTWV* libs (and of which exact
> sources) should be built by xHarbour, and xHarbour/Contribs, and
what
> functionality they provide? I'm hopping to clarify:
>
> [gt]wvt
> [gt]wvtg
> [gt]wvtgui
> [gt]wvg
>
> I'd love to clear all possible ambiguities, as well as, remove
> redundant source files, if any.
GTWVT - xhabour/source/rtl/gtwvt/gtwvt.c and gtwvt.h
This is almost same initial version which Peter posted on 22 Dec 2003.
GTWVTG - I do not know anything about it. How you came to this
term. It is no a library.
WVTGUI - Is now completely obsolete and should be removed from CVS
(xharbour/contrib/wvtgui).
This library was based on GTWVT for core operations
and implemted only
GUI components.
GTWVG - Is new library combining GTWVT + WVTGUI of old xharbour GT.
GTWVG can be used for
pure console applications instead of GTWVT. But
anybody needing only console
operations without any plans to implement GUI
components can use GTWVT.
Now onwards GTWVG and GTWVT are mutually exclusive
libraries. But both share the
same namespace and are interchangable. Future plan is
to strip the core part of
GTWVG and base it on GTWVT.
> Also, I'd like to know if/which GTWV[*] could be used along with
> CTWIN (GTCTW) to support multi windows operation, [maybe like the
now
> dysfunctional GTWVW]?
I do not know about CTWIN but it should not be a problem IMO.
However GTWVW cannot be replaced with CTWIN as both are wide apart
in concept
and design. I looked into GTWVW to seek a chance to port it to new GT
structure, but I think it cannot be done easily as the parameter slots
used in it are directly conflickting with new GT structure. It may
need
a total rewrite IMO, for sure I may be wrong.
> Finally, if possible could you please review the use of WVG* vs WVT*
> in the names of source file of contrib\gtwvg, and even better maybe
> also function names. This may further help resoution of current
> ambiguities.
As said, both libraries share the same namespace. It is so by
design. I will look into
where do I used WVG* names. I have to change those to WVT*. But for
sure
I could not understand your viewpoint on this point. Please clarify
a little.
On application level I has not changed even a single line of code
while
switching to GTWVG.
You can ask more for other clarifications.
Regards
Pritpal Bedi
The other season of giving begins 6/24/08. Check out the i’m
Talkathon. Check it out!
----------------------------------------------------------------------
---
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/
index.php_______________________________________________
xHarbour-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
xHarbour-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
