Bla Zabukovec Technical Consultant for Development Tools AD
Blaž Zabukovec Technical Consultant for Development Tools AD Consulting, Slovenia
Intermediate model(s) between class and development libraries Master repository for common functionality across the company Allows you to ‘customize’ the libraries
Pattern Libs Class Libs
Advantages
Implement company standards
Apply company standards Add often used business objects
Standardized UI
Auditing entity Reports
Filter entity Prompting
Menu bar Tool bar Input Update
Behavior is controlled by option
Filter does not work on qualified fields Not equal behavior on Windows and i. Series platforms (case sensitive) Bug in Load/Save criteria Date format cannot be controlled
There are no suitable collection points for making enhancements Make new version of subroutine
Find meta code for retrieving field name
By default
Match. Case field is passed to Block. Fetch as parameter All processing for case-sensitiveness is made in Block. Fetch function
All rows are retrieved from the database Filtering is done in Block. Fetch function Fields from database and from criteria are compared Before comparison we convert all strings to upper case (if no case sensitive is chosen) Use. Row is set accordingly
Use QDCXLATE command to convert strings to upper case
Filtering is performed by SQL statement (non-case sensitive) If case sensitive is chosen, perform the same type of filtering as for i. Series
Local field Filter. L<Current> is not initialized before saving Initializing the field solves the problem
Self referenced entity represents tree data structure
Use Active. X control for representing tree ACTIVE/Tree. View
Edit data
ACTIVE/Tree. View. Tree Edit. Tree
While there is any data
Key 1 Key 2 Data 1 Data 2 Parent | Key 1 Parent | Key 2
Add FNC option NME function to the scoped Scripts function Edit NME object and type in bmp file Change action diagram to load Image. List control
We need a correspondence between nodes and keys (records)
Introduce a new entity Key 1 Key 2 Node key 1 key 2 key 1_key 2
Detect selected node Obtain keys from the selected node (Tree. Data entity) Recursively delete nodes and records
Recursive deletion of record in the database is not implemented directly Use replacement triple
Detect selected node Obtain parent keys the selected node (Tree. Data entity) Call Add. Record function (not yet implemented) Add new node into tree Refresh tree
Add. Record is a Insert Adds record for the specific parent
Move node from one parent to another The same as changing parent keys Use drag & drop Perform controls (self referenced nodes, …)
Drag
Do not forget to enable drag & drop on the panel
- Slides: 44