Hi Budyanto,
On 2008.10.29., at 4:21, Budyanto Dj. wrote:
Hi Viktor,
On 28 Oct 2008 at 21:27, Szakáts Viktor wrote:
But why do you need to add all these non console
related stuff to GTWVT??
I think Pritpal is trying to get into the scheme of "inherits from
GTWVT to avoid duplicated code".
IMO this way it's done the wrong way.
For one, GTWVG has - from the beginning -
lots of duplicated GTWVT code, which is
still there.
Secondly, point of inheritance is that
generic features get implemented on the
parent level, while speciality features
get implemented on the child / inherited
level.
In this case speciality features seems
to be (planned to be) implemented on the
parent level, which is IMO not ideal.
Rather, existing duplicate code in GTWVG
should be eliminated, and replaced with
GTWVG specific stuff. This may also mean
that GTWVG could become a middle GT layer,
just like CTWIN GT, but I don't know it
enough to tell this.
You're again and again trying to add Windows
specific features to GTWVT, but such things
simply don't belong there. GTWVT is a console
emulation, and there is no need for any platform
specific whistles and bells there. Rather the main
point is that an application written for GTWVT can
be ported to GTWIN, GTXWC, GTTRM without
modification and with an equivalent feature set.
If GTWVT is restricted to "console emulation only" then I wonder why
we need to develop
GTWVT? Why not using GTWIN instead which is a native console?
Because it has quite some limitations (like
screen size, limited fonts selection) and
a worse "feel". GTWVT feels much more "native
Windows", than GTWIN. It also allows for a
WinMain() app to be built, which could have
other advantages.
We have an extremely flexible GT system in Harbour,
so there is very few need to touch core code to
implement special ideas beyond the core goals
and scope. This is exactly done this way to let
developers easily build upon in, and it's true for
GTs just as well as RDDs, or our Harbour API.
Isn't the GTINFO interface created with an idea that some feature(s)
may be absent in some other
GTs?
It is. That's not really the question, the
question is whether to implement special
GTWVG (or Windows GUI) hb_gtInfo() features
on the GTWVG level, or in GTWVT and core.
Also lets not forget that if there are some
features which get implemented on the
higher level (in GTWVG), it may turn out
to be useful and be moved "down" to core
eventually, if all the obstacles and portability
issues are cleared, etc.
My 2 cents.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
