Hi Viktor, Thanks for your explanation. There're still some things to clarify, if you don't mind.
On 29 Oct 2008 at 7:50, Szakáts Viktor wrote: > >> 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. I see that we are having a "grey area" here. Even your own explanation contradicts with one another: > >> [...] Rather the main > >> point is that an application written for GTWVT can > >> be ported to GTWIN [...] without > >> modification and with an equivalent feature set. but then you said later: > Because it [GTWIN] has quite some limitations (like > screen size, limited fonts selection) [...] Don't you agree here that an application written to use that "special feature" of GTWVT (special screen size, font selection) cannot be ported to GTWIN "without modification with an equivalent feature set"? So, how to determine which enhancements are allowed (eg. special fonts/screen size), and which others are not (eg. window style)? Even gfxPrimitive() is allowed in GTWVT, although there is no equivalent feature in GTWIN. Why? regards, budyanto _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
