About HMG Design...
Posted: Tue Aug 12, 2008 2:40 am
Hi All,
From the start of HMG in early 2002, I've talked about the goal of 'hide operating system complexities'. Sometimes, I've used other words, but the idea is the same.
The release 2.5.5 is a good demostration of this concept.
Windows API includes two Combobox controls.
The standard combo and an enhanced version, capable of image handling.
IMHO, from an high level programmer point of view, must be only one combo in his toolbox, capable of handle images, if desired.
I could add a second combobox control (I could call it 'SuperCombo':) but IMHO it has no sense.
Instead that, the only thing that HMG programmers must care about, is that they have a new property called 'Image' for ComboBox control. That's all.
If you take a look at \hmg\source\c_combo.c file, you'll find two different functions to create a combo, depending on 'image' property content, but it is transparent for the HMG programmer.
There is lots of things required for Win32 API like IDs, ImageLists, Font objects, or pens that I've hide too.
This way, the programmer, can focus on the problem to solve via his application, instead the OS internals.
This is the xBase spirit. This is the HMG spirit too.
Regards,
Roberto.
From the start of HMG in early 2002, I've talked about the goal of 'hide operating system complexities'. Sometimes, I've used other words, but the idea is the same.
The release 2.5.5 is a good demostration of this concept.
Windows API includes two Combobox controls.
The standard combo and an enhanced version, capable of image handling.
IMHO, from an high level programmer point of view, must be only one combo in his toolbox, capable of handle images, if desired.
I could add a second combobox control (I could call it 'SuperCombo':) but IMHO it has no sense.
Instead that, the only thing that HMG programmers must care about, is that they have a new property called 'Image' for ComboBox control. That's all.
If you take a look at \hmg\source\c_combo.c file, you'll find two different functions to create a combo, depending on 'image' property content, but it is transparent for the HMG programmer.
There is lots of things required for Win32 API like IDs, ImageLists, Font objects, or pens that I've hide too.
This way, the programmer, can focus on the problem to solve via his application, instead the OS internals.
This is the xBase spirit. This is the HMG spirit too.
Regards,
Roberto.
