hwgui-developers

[Hwgui-developers] Few notes about new Designer

[Alexander S.K. <al...@be...>]

Hello All,

 the Designer is fully rewritten and has a number of important
 features.

 1. The controls set is fully configurable. The list of
 controls ( widgets ) is placed in special configuration file with XML
 format. The name of that file is in Designer's ini file
 "Designer.iml", currently it is resource/widgets.xml. To add a new
 control or even a controls set, or add new properties/methods for a
 control is easy now - just edit the widgets.xml. This allows to use
 the Designer not only for HwGUI based, but for any other
 applications - you can create a fully new controls set for your
 purposes.

 2. The Designer can be built not only as standalone program, but
 can be a part of other application where it is needed to edit forms
 at runtime.

 3. The output formats are configurable due to the using of external
 scripts. The native HwGUI format support is included in Designer's
 code, all others are included as plugins.
 Currently there are two plugins - for reading old .frm files (
 resource/f_text.prg ) and for writing the prgs - f_hwgprg.prg ( not
 fully functional yet ).

 4. Designer allows to describe not only properties, but methods, too
 - so the form description is a complete dialog procedure.
 You can read it from a file or from a string ( if you previously
 loaded it to the string from any source ) method and show it on a
 screen:

   oForm := HFormTmpl():Read( "testget1.xml" )
   oForm:Show()

 So, it allows to create really data driven applications.

 There are two sample forms included - testget1.xml and testget1.xml,
 which implements the functionality of samples/testget1.prg and
 samples/testget2.prg.

 Of course, it isn't fully completed - I need to decide how implement
 the tab pages control, how to describe the browse ...
 More controls should be added.
 I plan also to add syntax highliting in the methods editor.
  

Regards,
 Alexander
http://kresin.belgorod.su

[Hwgui-developers] hwgui-developers@lists.sourceforge.net

[Rodrigo M. <rod...@te...>]

Very good !
Great Job !

Best Regards
Rodrigo

Re: [Hwgui-developers] Few notes about new Designer

[Sandro R. R. F. <san...@ya...>]

Alexander
I liked very
But I would be better f_hwgprg.prg to record instead of Editbox for GET,
because for implementatios disponible in GET command, Valid, When, Picture,
etc. not present in edibox
The Rodrigo Moreno created the classrooms for Postgree in xHarbour style
classes for Mysql, would be possible, to associate in the future tables
forms, DBF and/or SQL.
Congratulations for the work, are excellent
Regards

Sandro Freire
http://www.lumainformatica.com.br
----- Original Message ----- 
From: "Alexander S.Kresin" <al...@be...>
To: <hwg...@li...>
Sent: Thursday, June 03, 2004 11:37 AM
Subject: [Hwgui-developers] Few notes about new Designer


> Hello All,
>
>  the Designer is fully rewritten and has a number of important
>  features.
>
>  1. The controls set is fully configurable. The list of
>  controls ( widgets ) is placed in special configuration file with XML
>  format. The name of that file is in Designer's ini file
>  "Designer.iml", currently it is resource/widgets.xml. To add a new
>  control or even a controls set, or add new properties/methods for a
>  control is easy now - just edit the widgets.xml. This allows to use
>  the Designer not only for HwGUI based, but for any other
>  applications - you can create a fully new controls set for your
>  purposes.
>
>  2. The Designer can be built not only as standalone program, but
>  can be a part of other application where it is needed to edit forms
>  at runtime.
>
>  3. The output formats are configurable due to the using of external
>  scripts. The native HwGUI format support is included in Designer's
>  code, all others are included as plugins.
>  Currently there are two plugins - for reading old .frm files (
>  resource/f_text.prg ) and for writing the prgs - f_hwgprg.prg ( not
>  fully functional yet ).
>
>  4. Designer allows to describe not only properties, but methods, too
>  - so the form description is a complete dialog procedure.
>  You can read it from a file or from a string ( if you previously
>  loaded it to the string from any source ) method and show it on a
>  screen:
>
>    oForm := HFormTmpl():Read( "testget1.xml" )
>    oForm:Show()
>
>  So, it allows to create really data driven applications.
>
>  There are two sample forms included - testget1.xml and testget1.xml,
>  which implements the functionality of samples/testget1.prg and
>  samples/testget2.prg.
>
>  Of course, it isn't fully completed - I need to decide how implement
>  the tab pages control, how to describe the browse ...
>  More controls should be added.
>  I plan also to add syntax highliting in the methods editor.
>
>
> Regards,
>  Alexander
> http://kresin.belgorod.su
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> From Windows to Linux, servers to mobile, InstallShield X is the one
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> Hwgui-developers mailing list
> Hwg...@li...
> https://lists.sourceforge.net/lists/listinfo/hwgui-developers

[Hwgui-developers] Re[2]: Few notes about new Designer

[Alexander S.K. <al...@be...>]

=F7=E5=F2=E2=E5=F0=E3, 3 =E8=FE=ED=FF 2004 =E3. Sandro sandrorrfreire@yah=
oo.com.br wrote:

SRRF> Alexander
SRRF> I liked very
SRRF> But I would be better f_hwgprg.prg to record instead of Editbox for=
 GET,
SRRF> because for implementatios disponible in GET command, Valid, When, =
Picture,
SRRF> etc. not present in edibox

  Yes, of course. Full support of GETs functionality will be in
  f_hwgprg.prg, too.
  Last days I concentrated mostly on reading/executing xml - data
  driven applications are my 'idee fixe' :). I find it very useful to
  have configurable forms separately of the application - to have
  possibility to configure them for different tasks, different users
  ... This is very needed, IMO, for ERP systems.
  We may keep forms in separate xml files, in the database of any
  kind, just read them and execute.
 =20
SRRF> The Rodrigo Moreno created the classrooms for Postgree in xHarbour =
style
SRRF> classes for Mysql, would be possible, to associate in the future ta=
bles
SRRF> forms, DBF and/or SQL.

 This is possible already.

Regards,
 Alexander
http://kresin.belgorod.su

Re: [Hwgui-developers] Re[2]: Few notes about new Designer

[Sandro R. R. F. <san...@ya...>]

My idea is terms somewhat seemed to demonstrated in the example demodbf.prg
With definite edition buttons daily pay
Regards

Sandro Freire
http://www.lumainformatica.com.br
----- Original Message ----- 
From: "Alexander S.Kresin" <al...@be...>
To: <hwg...@li...>
Sent: Thursday, June 03, 2004 2:49 PM
Subject: [Hwgui-developers] Re[2]: Few notes about new Designer


÷åòâåðã, 3 èþíÿ 2004 ã. Sandro san...@ya... wrote:

SRRF> Alexander
SRRF> I liked very
SRRF> But I would be better f_hwgprg.prg to record instead of Editbox for
GET,
SRRF> because for implementatios disponible in GET command, Valid, When,
Picture,
SRRF> etc. not present in edibox

  Yes, of course. Full support of GETs functionality will be in
  f_hwgprg.prg, too.
  Last days I concentrated mostly on reading/executing xml - data
  driven applications are my 'idee fixe' :). I find it very useful to
  have configurable forms separately of the application - to have
  possibility to configure them for different tasks, different users
  ... This is very needed, IMO, for ERP systems.
  We may keep forms in separate xml files, in the database of any
  kind, just read them and execute.

SRRF> The Rodrigo Moreno created the classrooms for Postgree in xHarbour
style
SRRF> classes for Mysql, would be possible, to associate in the future
tables
SRRF> forms, DBF and/or SQL.

 This is possible already.

Regards,
 Alexander
http://kresin.belgorod.su




-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Hwgui-developers mailing list
Hwg...@li...
https://lists.sourceforge.net/lists/listinfo/hwgui-developers

[Hwgui-developers] Re: Few notes about new Designer

[Alexander S.K. <al...@be...>]

On 03.06.2004 22:02, Sandro R. R. Freire <san...@ya...> wrote:

SRRF> My idea is terms somewhat seemed to demonstrated in the example demodbf.prg
SRRF> With definite edition buttons daily pay

 Recently added testdbf1.xml implements the functionality of the
 samples/demodbf.prg.
 Below are few notes about it.

 1. There is a line 'common' in the events of a form, it is intended for
 functions, which are needed for the form and which can be called from
 any other event handler of the form.
 The function must be ended with the 'ENDFUNC' statement. The 'Return'
 isn't obligatory, but may be used if the function must return some
 value.
 
 2. The form has a property 'Variables' - you
 may add there variables, which will be declared as 'Private' in the
 beginning of HFormTmpl():Show() and may be used in any event handler
 of the form.

 3. Each widget has a property 'Name' - this is a object name, which
 also will be declared as 'Private' in the beginning of
 HFormTmpl():Show().

 4. The widgets, which have corresponding 'GET' items, has a property
 'Varname' - the name of the correspondibg variable, which also will
 be declared as 'Private' in the beginning of HFormTmpl():Show().
 

Regards,
 Alexander
http://kresin.belgorod.su