Beginning with HMG. Which version 3 or 4 ?

[esgici]

Thanks Brother Sudip

I was really worried before your reply.

Regards

--

Esgici

[Carlos Britos]

Hi all.
Yesterday I wrote to Roberto since he has been out of the forum for a while, to ask him if he is ok.
He told me, all is ok, just his spending more time to his job. And as soon as possible he'll be back. It's not easy to mix the passion to his job and to Hmg.
He authorized me to send this message to the group.

The translation is not literal but I think the message is clear.

[esgici]

...
...I think the message is clear.

Yes, more than enough

Thank you very much to you too Carlos

Saludos Cordiales.

--
Esgici

[sudip]

Thanks a lot Carlos

[esgici]

Hi Sudip,

Your previous picture (avatar) was better

Regards

--

Esgici

[mrduck]

I'm working on the only hmg-3 code I have other than abm2, yafc from Luigi...

I confirm that abm2 is quite complicated to port but perhaps I should take it in another way

As Luigi said, yafc is complicated too, but for other reasons: hmg4 is incomplete and Luigi uses some things that are not yet ported, but most importantly NOT ALL SYNTAX is ported !

In hmg-3 there are 2 different syntax for DEFINE TOOLBAR and only one was present in hmg4. I ported the second but - I don't understand why, the DEFINE TOOLBAR xcommand is not converted as it should.

Other "preprocessor" problems were present (and probably a lot more are present) and I tried to clean them up.

I see that in hmg4 for several objects you have 2 similar ways to create them:
DEFINE TOOLBAR ;
PARAMETER1 A ;
PARAMETER2 B

or

DEFINE TOOLBAR
PARAMETER1 A
PARAMETER2 B

note the missing ";" at the end of the second case...

For the preprocessor they are completely unrelated and must be handled differently...

[sudip]

Hi Sudip,

Your previous picture (avatar) was better

That was not my picture
I want to show all of you how "Angry" I am

Ok, jokes apart, I am thinking to join HMG 4 seriously. Rathi, is there anything for me?

[Hazael]

Hello friends,

I was just looking for the answer for the same question...
My program is CUI only and I had no interest in GUI because of the complexity and extra payload BUT things change... and I am now looking for a good GUI "way" to go.
I looked for wxHarbour, qtHarbour, HMG, xHGtk, HbQt and Marinas-GUI.
Well, for a begginer the compatibility is not an issue so the HMG 3 x HMG 4 compat issue really does not matter - anyway for HMG 3 users it may be although I belive it is not worthy to keept compat since QT is different and may require too much work to keep it compatible (maybe not).

I liked wxHarbour but couldnt understand it well - seems to be very powerful.

xHGtk seems easier but still powerful but couldn't find much help and I almost gave up (will try a bit more).

qtHarbour is still incomplete and may take a long time yet. May be a good option but not yet.

Marinas-GUI is very nice and pretty easy. Qt based and good documentation: www.marinas-gui.org - seems to be a nice choice but I need to test it more.

HMG 3 I never tried and will not try because it is Windows only and in my case it is important to be multi-plataform.

HMG 4 is one of the easiest I found (with Marinas-GUI) and the way to build the examples is simple but seems imcomplete and unstable...

HbQt is the "Harbour Official" but it is not easy and is a work in progress...

I am in a dilema...

[Rathinagiri]

Hi Qatan,

IMHO, HMG needs lesser learning and it took me minimum time to port my previous clipper projects to GUI ones.

Every alternative has its own merits and demerits. Therefore, HMG would also have some.

But, I experienced implementing some big projects live on HMG and they are working well for years on Win98, 2000, XP, Vista and Windows 7.

Now, whether to take HMG 3 or 4. HMG 3 is a stable product. HMG 4 is in alpha version. It has to undergo many changes. However, we will work hard to make it compatible to HMG3 so that only minimal changes are required to port from HMG 3 to 4.

[mrduck]

Hi Qatan
you are mixing things up a bit between "layers"...

hbQt and qtHarbour are layers to use Qt with harbour.

On top of that layers you can have "frameworks". Up to now both hmg4 and marinas use hbQt as layer.

So your choice now is between hmg4 and marinas