Hello Viktor

<<<
It's a compatibility issue, but how come naming
GTWVG functions as GTWVT is the central idea?
I don't understand.
>>>

:-(((

<<<
[ I thought the central idea is that GTWVG is a GUI
which allows me to use Clipper legacy console output
commands to generate GUI (or hybrid) apps. The fact
that it's technically based on GTWVT, and that it
shares a lot of code with it, really doesn't matter
in regards to the final user (developer) experience
IMO. It's just an implementation detail. ]
>>>

User is not concerner nor he cares. I agree.

<<<
I can understand that. Still, it's extremely
confusing to name GTWVG functions as GTWVT.
>>>

Why confusing. Since its inception it is being used as is.
More we are in a process the pull out the core part out of 
GTWVG and totally base it on GTWVT, just like it existed
in xHarbour for so many years.

<<<
Names are also used quite inconsistently right now,
some are named WVG and some WVT, so I think we should
somehow transition things to WVG. To not break app
compatibility, a simple #define layer could be added
to translate WVT to WVG for the application level code,
optionally with a notice that code is recommended to
be updated.
>>>

Again please I strongly oppose this. 
As already agreed upon, contribs are the private areas 
and so I would not like it to be changed just because 
it does not confirm to some standards.

<<<
Right now if a casual Harbour user sees "WVT_SetClipboard()",
he/she would logically look for this function in the
core, they would naturally expect it to require gtwvt.lib.
It's unlikely they could easily figure that gtwvg.lib is
what they really need.
>>>

This has to be documented in a better way. That's it.

<<<
Names are very important.
>>>

Surely yes. But in case GTWVG, no.

Regards
Pritpal Bedi

-- 
View this message in context: 
http://www.nabble.com/2008-06-26-11%3A21-UTC%2B0200-Viktor-Szakats-%28harbour.01-syenar-hu%29-tp18129952p18146982.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.

_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to