How harbour and xharbour will have more thing in common?
Massimo Belgrano
This Is dream common to harbour/xharbour userbase
make compatibile hbqt,gtwvg from harbour to xharbour
add hbmk2 from harbour to xharbour
support commercial product sqlrdd also in harbour
Join effort for double result starting from developer list
https://groups.google.com/forum/#!forum/harbour-devel
http://news.gmane.org/gmane.comp.lang.xharbour.devel
When is planed next version of xharbour 1.3?
What can be done for reduce the differences between harbour and xharbour?
Mel Smith
I have the same dream that you do !
However, we have now so many 'harbour language' choices (for building
apps, for GUI options, for librairies, etc). And we have so many egos
involved, and so many very smart people who have invested their time, and
their souls, and their money, to put their imprint on Harbour, that it is
not likely they will be able to compromise for the greater good of all.
They would become 'programming Saints' if they did !
I guess we 'lesser mortals' have to wait and see what the gurus will do.
In the meantime, we have Harbour and xHarbour drifting apart ...
To: David Smith (our mother ship):
What are your thoughts on this scary future of ours ?
-Mel
dlzc
More like "worry wart"...
> What are your thoughts on this scary future of ours ?
Windoze 8 is pretty much going to trash any hopes we have of a future,
it would seem. We should not be concentrating on pulling libraries
together, but pulling cooperating modules together. Not making a mark
at the bit level, but wearing seven league boots.
Look at the advancement of Science. Newton (and others) provide
calculus, and Science explodes. Each step does not have to
reduplicate the foundation laid by others, but uses previous steps,
and proceeds to bigger and better theories.
So rather than proceed with the future hinted at by dBaseIII+, we nose-
dived into converting the language into, essentially, C. And this
language is intended to be some sort of swiss army knife, that does
the Clipper 5.3 thing, and acts as a platform to bring Windoze
functionality into the base language. So it is the worst of all
possible places to start from. Like learning English as a second
language (I hear).
Here is an appropriate quote:
http://www.goodreads.com/author/quotes/3856024.James_Nicoll
... we have been down that alley, and we came back with DOS-isms, C-
isms, Windoze knobs, a smattering of OOP, some really good libraries
(Zip for example), and Mr. Pinkas spliced on Visual Basic (sort of).
Any free, open source project is going to have "tow motors" that drag
the various bits in all sorts of directions. And you are right, the
egos have made incompatibilities between the versions. And this
happens, because there is no agreed on direction. But from what I
see, both code-bases are going in the wrong direction anyway.
What we need is...
When I can complete that, I'll be smarter than I am right now. But
Mel, I don't think that the two crews can provide us a future much
beyond Windows 7. We need better object orientation, we documentation
of that (probably before one lick of library code is generated), we
need to be able to open a file and do some nice data entry with
lookups, in less than 20 lines of our code. We need to be able to
encapsulate business rules in some OOP fashion, and that should not
take more than another 20 lines either.
We aren't working smarter. The fork in the language is just
distracting us from any sort of horizon, any sort of navigation.
David A. Smith
Tim Jacob
What did I miss? How is Windows 8 going to trash any hopes of a future
with (x)Harbour?
Thanks
Tim Jacob
dlzc
On Jul 5, 6:13 am, Tim Jacob <tja...@nospam.jollyfarmer.com> wrote:
> On 07/05/2011 2:12 AM, dlzc wrote:
...
> > Windoze 8 is pretty much going to trash any hopes we
> > have of a future, it would seem.
>
> What did I miss? How is Windows 8 going to trash any
> hopes of a future with (x)Harbour?
http://groups.google.com/group/comp.lang.clipper.visual-objects/msg/1482c715cfa0771e
... click on "More options", then "View thread". If it applies to VO,
it applies to us.
I read this as Windows 8 is more mobile application oriented, and that
may just be my paranoia, the thread is specific to mobile processors,
or M$ is just out to make another Vi$ta mistake.
Be glad if someone who knows more chimes in.
David A. Smith