Page 2 of 3
Re: Future Directions
Posted: Thu Aug 12, 2010 11:51 am
by Roberto Lopez
Hi,
Thanks for your support words.
Before starting the team work, I want to work a little more on the base code to establish basic guidelines for development and make your work easier.
To make clear how easy this will be, I'll use textbox's inputmask.
Since Windows API has not native support for InputMask, HMG's inputmask took about two years of work to make it reasonable reliable and stable (for me and various contributors involved in fixing and enhancing).
To have a textBox InputMask using QT as back-end will only need the following:
Code: Select all
*..............................................................................*
METHOD InputMask ( cValue ) CLASS TEXTBOX
If ::lCreated
If Pcount() == 0
RETURN ::oQTObject:InputMask()
ElseIf Pcount() == 1
::oQTObject:SetInputMask( cValue )
EndIf
Else
If Pcount() == 0
RETURN ::cInputMask
ElseIf Pcount() == 1
::cInputMask := cValue
EndIf
EndIf
RETURN Nil
THIS is what I'm talking about

Re: Future Directions
Posted: Thu Aug 12, 2010 12:04 pm
by sudip
Fantastic !!!

Re: Future Directions
Posted: Thu Aug 12, 2010 1:46 pm
by Rathinagiri
Super! I am eagerly waiting for your framework.
Roberto, I already knew how you create your framework so simple and easy to understand.
I don't know whether or not you remember. Initially you had given the idea of alternate syntax and I had helped by implementing the job. It is a different story altogether that you have revamped the alternate syntax in a better way after that.
Less talk and more walk would bring the goal nearer.

Let's start doing it.
Re: Future Directions
Posted: Thu Aug 12, 2010 3:59 pm
by Roberto Lopez
rathinagiri wrote:I don't know whether or not you remember. Initially you had given the idea of alternate syntax and I had helped by implementing the job.
I remember it. You was a little 'upset' because @...<Command> syntax where sometimes inconsistent
Anyway, some time after the alternate syntax was implemented, I've discovered how to solve the problem. The solution was to declare all clauses as optional. That way, you can use clauses in any order

Re: Future Directions
Posted: Thu Aug 12, 2010 3:59 pm
by sudip
Hello All,
May be out of the topic, but has some relation with HBQt.

Just now I am able to compile and run Harbour HBQt test file with HBIDE
Thanks to Pritpal and Massimo

- hbqt.jpg (45.54 KiB) Viewed 4556 times
Re: Future Directions
Posted: Thu Aug 12, 2010 4:38 pm
by luisvasquezcl
Estimado Roberto,
averiguando lo que dijo Sudip por el demo de harbour, bajé los fuentes y alli efectivamente hay un demo con muchos controles definidos que pueden ser utilizados como ejemplo para implementar en hmg.
Además, estuve revisando el manual de QT y en realidad es tremendamente simple por lo que habremos muchos con ganas de apoyar para sacar adelante este proyecto y ponerlo a producir.
Esto se va a poner bueno, ya estoy esperando la 1a release.
saludos cordiales de un impaciente
Luis Vasquez.
Re: Future Directions
Posted: Thu Aug 12, 2010 5:42 pm
by Rathinagiri
I had long back downloaded the Harbour sourcecode along with HBQT. But never looked into the details.
You know what I had seen first?! How the tableview control is and what are all the features.
I think Roberto has swindled a treasure.

Again, I am eagerly waiting for the SIMPLEST implementation of QT via HMG.
Re: Future Directions
Posted: Thu Aug 12, 2010 5:43 pm
by Rathinagiri
Hi Sudip,
How is the incremental search in QT?!
Re: Future Directions
Posted: Thu Aug 12, 2010 5:56 pm
by sudip
Hi Rathi,
HBQt has Good Incremental search with Listbox. HBQt Grid's edit mode is activated when pressing any key (non-navigational keys) like spreadsheet.

Re: Future Directions
Posted: Thu Aug 12, 2010 8:16 pm
by Roberto Lopez
Hi All,
I've created a new project at Sourceforge and I've started to work with SVN preparing it for the team work:
http://hmg.svn.sourceforge.net/viewvc/hmg/
Meaning that contributors will be able to upload your changes directly. To do that, I'm using Tortoise SVN.
Contributors will need a SourceForge.net account.