bedipritpal wrote:Hello Group
Though this message can be ignored, but it will be useful if acted upon.
There are tons of scattered "demos" with names "demo_n" .
It is a lot of work for user to see what is where to look into.
Plus it is a repeatitive code. Also it does not portray a composite
application view of HMG.
What I believe, most of the demos can be clubbed into one
showcase application with bells and whisles. It will facilitates:
1. A showcase application a new user can use as a template.
2. Maintenance of the code will be easier.
3. You will have to write less code.
4. User will always have to look into at one place.
hbIDE is one example of showcasing hbQT as a whole.
I agree with you about that we need a complete application to show all HMG capabilities.
In fact we already have them in HMG 3.x samples. We do no included in HMG.4 yet, because many things are not completed yet and they will not work.
I do not agree with you about demo_* concerns. I'll explain:
Until 3.x version HMG supported two kinds of syntax: xBase and alternate.
xBase is the @...COMMAND style and alternate is the DEFINE... END style.
HMG.4 supports OOP too.
The idea of 'repetitive' demos is to show how to do the same things using each one of the three styles. So, they must remain.
Besides that, my experience as teacher in computing science, is that the best way to teach to beginners is to focus in only one topic at the same time.
So, if someone is curious about the (ie) button control, he just must to go to the button folder and look at the three demos (OOP, xBase and Alternate syntax) to choose your preferred style and learn about the basics of the control.
Please, remember that HMG is aimed to be simple and easy to use, inspired by the original xBase spirit. The samples must be evaluated in such context.