Print Procedure Print Form Definition
Print Procedure Print Form Definition
Hi
Thanks for the update.
Is there an option to Print Procedure Print Form Definition it was an option I used regularly on the old system.
Graham
Re:?Print Procedure? ?Print Form Definition?
There is no actions/functions for printing definitions.
This too is one place where DFW always have been weaker than DFD
..
There is a Print Definition thing on the Print Dialogue, but it
doesnt work and when it did it produced just rubbish
(Just checked 6.52 and
it didnt work there either
.so havent worked for at least 10 year
)
This is one of the weaknesses of the DFW structure. Functionality is made
as special case as part of the GUI structure instead of being a resources
that can be accessed through DataEase in general.
The problem with this is that as things change/progress the default
functionality lag behind or stop working and new functionality added to the
product is not included in the structure.
There need to be an acceptance amongst the caretakers/developers of a product
like DataEase that they dont know everything, so they need to make sure that
what they do dont impact everything or disturb everything. live and let
live.
In both DE8 and especially in future versions of DataEase we will keep
hardcoded functionality to a minimum. Everything need to be part of the
user/developer universe so changes and updates follow normal DataEase rules.
In DE8 we will make an document plugin that is an application that can be
installed in any DE8 app, where the user/developer can generate a Document with
updated information about all Forms/Reports/Scripts/DQLs (including ExecDQL)
etc.
Since this is a DE8 app, the users can of course also change/steal parts of it
and include it in their own apps.
We prepared for this by making a function called RefreshStatus()
that will update the Status tables included in DE8, we also restructured the
Status tables so they now show proper table structure rather than
aggregated data.
These tables can be used to generate any report on an application already now
as they contain structured information about Tables,forms,DQLs, OMLs etc.
What they dont contain is information about Buttons which will be added.
Re:?Print Procedure? ?Print Form Definition?
There is no actions/functions for printing definitions.
This too is one place where DFW always have been weaker than DFD
..
There is a Print Definition thing on the Print Dialogue, but it
doesnt work and when it did it produced just rubbish
(Just checked 6.52 and
it didnt work there either
.so havent worked for at least 10 year
)
This is one of the weaknesses of the DFW structure. Functionality is made
as special case as part of the GUI structure instead of being a resources
that can be accessed through DataEase in general.
The problem with this is that as things change/progress the default
functionality lag behind or stop working and new functionality added to the
product is not included in the structure.
There need to be an acceptance amongst the caretakers/developers of a product
like DataEase that they dont know everything, so they need to make sure that
what they do dont impact everything or disturb everything. live and let
live.
In both DE8 and especially in future versions of DataEase we will keep
hardcoded functionality to a minimum. Everything need to be part of the
user/developer universe so changes and updates follow normal DataEase rules.
In DE8 we will make an document plugin that is an application that can be installed
in any DE8 app, where the user/developer can generate a Document with updated
information about all Forms/Reports/Scripts/DQLs (including ExecDQL) etc.
Since this is a DE8 app, the users can of course also change/steal parts of it
and include it in their own apps.
We prepared for this by making a function called RefreshStatus()
that will update the Status tables included in DE8, we also restructured the
Status tables so they now show proper table structure rather than
aggregated data.
These tables can be used to generate any report on an application already now
as they contain structured information about Tables,forms,DQLs, OMLs etc.
What they dont contain is information about Buttons which will be added.