Some of you already use xbrowse as a screen designer i think.
Xbrowse that will have folowing basics :
The program will than read the setting (ex. Invoice) and build a screen (The call can be afther a dlg. is setup)
I think that the oData can be used to configure more in the program itself
oInv_Cust... (colors, font, ....)
Has anyone a sample using this technique ?
Most likely i will also be using (Oop the oDatabase technique) for new parts of the program
Would you use row/col or pixels ? (I will be using 1 kind of screen, NO changes of resolution are needed)
Xbrowse that will have folowing basics :
ID Screen name xPos yPos oData
01 Invoice Customer Nr : 05 10 oInv_Cust
01 Invoice Date : 06 10 oInv_Date
02 Customers Customer Nr : 05 20 oCus_Cust
....The program will than read the setting (ex. Invoice) and build a screen (The call can be afther a dlg. is setup)
I think that the oData can be used to configure more in the program itself
oInv_Cust... (colors, font, ....)
Has anyone a sample using this technique ?
Most likely i will also be using (Oop the oDatabase technique) for new parts of the program
Would you use row/col or pixels ? (I will be using 1 kind of screen, NO changes of resolution are needed)
Marc Venken
Using: FWH 23.08 with Harbour
Using: FWH 23.08 with Harbour
