samples/textbox/demo01_op.prg (OOP, I think real OOP)
samples/textbox/demo01_cl.prg (command line)
and both "demo01" must do the same things....
I agree with this position. directory must be one and demos different only for coding style must have different suffix.
So everyone can learn OOP just comparing the code...
At first, I want to empathize that this is no my intention to start a flame about this.
I'm only trying to discuss ideas. It is a funny and productive thing.
Sadly, sometimes the written words meaning is misunderstood, but, since it is not possible for us to drink a coffee together and talk about this in person, I'm making this clarification
Many times, across almost 10 years of HMG development, many people wanted to 'educate' HMG users (and to me too) because our 'wrong' way of coding...
Well... semi-oop model is not wrong. It is an alternative way of coding
So, the HMG users must not be 'educated' in OOP to correct their incorrect programming behavior
The people that selected HMG, done so, because it is simpler, cleaner and easier than standard OOP.
If we want to keep them with us, we must show them, how well HMG.4 is doing with semi-oop and how powerful is, comparing it with previous versions.
So, as mentioned in my previous post, my proposition is to have both things:
1. 'Twin' oop/semi-oop samples together for testing, comparison and OOP learning (for those HMG users interested on that).
2. A Separate folder with semi-oop samples only for those users that prefers semi-oop for your applications and are not interested on dealing with standard OOP.
Please remember that such 'mix' of samples is the main reason about users confusion about semi-oop support in HMG.4.
A separate/clean place for the samples, with polished semi-oop code, will solve the problem...