Re: SOME CLARIFICATIONS...
Posted: Sun Mar 28, 2010 9:14 am
Hi,
Iam 100% with you Roberto. Thank you very much for your work. You're are a true blessing to me. I honestly feel, from my little experience, that it is always by far more beneficial sticking with official builds...be it harbour or minigui.
Most times, and with all due respect to the extended builds architects, these extensions only work towards confusion and fracturing the user base, for not so justifiable reason. I had the benefit of using hmgextended for some years and I did not find anything there that I couldn't do in hmg official...except the mdi interface, which, and thanks to Roberto, I now know is not a good way to go. I have also tried ooHg which purposes to introduce full oop style to Minigui....but I also succeeded in writing classes for all hmg controls, albeit by calling _def* functions directly (the alternate syntax proved ploblematic) ...which makes me wonder about the real gain to be derived from such extensions. I apologise if my views hurt someone,...that is not the intention here...Alot of work goes to these extensions which I believe if shared with the HMG official, instead of as different projects, can only be beneficial to all, but obviously keeping in line with the vision of hmg.
Just my 2 cents.
Iam 100% with you Roberto. Thank you very much for your work. You're are a true blessing to me. I honestly feel, from my little experience, that it is always by far more beneficial sticking with official builds...be it harbour or minigui.
Most times, and with all due respect to the extended builds architects, these extensions only work towards confusion and fracturing the user base, for not so justifiable reason. I had the benefit of using hmgextended for some years and I did not find anything there that I couldn't do in hmg official...except the mdi interface, which, and thanks to Roberto, I now know is not a good way to go. I have also tried ooHg which purposes to introduce full oop style to Minigui....but I also succeeded in writing classes for all hmg controls, albeit by calling _def* functions directly (the alternate syntax proved ploblematic) ...which makes me wonder about the real gain to be derived from such extensions. I apologise if my views hurt someone,...that is not the intention here...Alot of work goes to these extensions which I believe if shared with the HMG official, instead of as different projects, can only be beneficial to all, but obviously keeping in line with the vision of hmg.
Just my 2 cents.