Dexterity for Dummies

					Dexterity for Dummies

 Name
 Company, Position & Location
 Experience with Dexterity
 Other Programming Experience
 Objectives for this presentation
 Favourite Hobby

   David Musgrave
   Managing Director of Winthrop Dexterity
    Consultants in Perth, Western Australia
   Worked with Dexterity since V2.04 in 1994
   Worked with many languages since 1984
   To give an overview of Dex Architecture
   Family, DJ’ing and Horse riding
Where is Perth, Australia

 Name
 Company, Position & Location
 Experience with Dexterity
 Other Programming Experience
 Objectives for this presentation
 Favourite Hobby
Presentation Structure

   Informal and informative

   Ask questions

   Stop me if you don’t understand

   NB: Please turn Mobiles & Pagers off
Objectives of Presentation

   To introduce the design concepts
    behind Dexterity.

   To provide an understanding of what
    Dexterity allows the developer to do.
Agenda of Presentation

 History and Background
 Data Dictionaries & Resources
 Coding, Strings & Messages
 Modifier & Report Writer
 Third Party Products
 Development Techniques
Q & A
History & Background
   Research begins in 1988
   Development system for graphical
    programming with scripting used as code
   Support for leading operating systems
   Data and applications shared across
   Wide ability for customization
   International focus
History & Background
    Development Platforms
     –   Windows 95, Windows 98, Windows NT
         (Intel), Windows NT (DEC Alpha)
     –   Macintosh is being phased out
    Data Managers
     –   Pervasive.SQL, c-tree Plus, Microsoft SQL
         Server v6.5 and v7.0
    Three-tier Architecture -        Client, Data
     Server, Process or Application Server
History & Background
   Dexterity is developed Microsoft Visual C++.
   The same language that the Microsoft Office
    suite was developed in.
   Only Visual C++ can be linked with VBA.
   Has been full 32 bit environment since 2.00.
   It has been Y2K compliant since the start.
   It separates Business Logic from Technology.
   It is Data Dictionary based with a runtime.
Data Dictionaries & Resources
   A Data Dictionary is a collection of
    information which can be interpreted as
   In Dexterity, it is a collection of Resources
    which can be executed by the runtime as
   Every “Object” in Dexterity is a Resource,
    having a Resource Type & a Resource ID.
Data Dictionaries & Resources
   Dexterity uses Resources in a “building
    block” approach from the bottom up.
   Data types - String, Integer, Boolean.
   Fields - Customer Number, Description.
   Tables - RM_Customer_MSTR.
   Forms containing Windows -
   Reports - SOP Blank Invoice Report
Coding, Strings & Messages
   The scripting language of Dexterity is called
    sanScript (after Steven A. Nicolai).
   SanScript code can be added to any field on
    a window, the window itself, or the form.
   Different code can be executed on different
    “Events” - Pre, Change, Post
   Code used from many Forms can be added
    at a Global level.
Coding, Strings & Messages
   All text that is visible to the User is
    “Translatable” or at least should be!!!!!!!
   All Field Prompts, Window Names, Table
    Display Names, etc. can be changed
    without having source code.
   If Messages are used from within the
    code, they can be changed also.
   Source code is removed when the product
    is shipped to the customer.
Modifier & Report Writer
   The Modifier & Report Writer allow
    resources within a Dexterity product to be
    changed by the end user.
   You cannot change a resource which
    would damage the product - Tables.
   All changes are stored in a separate
    Custom dictionary.
   The original Application dictionary is
Third Party Products
   Third Party products are built inside a
    copy of Dynamics dictionary.
   Anything added has Resource ID >=
   This allows the changes to be extracted,
    so that only the changes can be delivered.
   These are called “Chunks” or .cnk files.
   It also allows re-use of all Dynamics
Development Techniques
   New Tables, Forms, Windows & Reports.
   Modify a Dynamics Form or Report.
   Creates an alternate Form or Report.
   Avoid as only one alternate can be used
    by one user at any one time.

   Or added into Dexterity 3.0 …
Development Techniques
   Triggers
   sanScript code which can be executed
    when “events” occur in Dynamics.
   Focus - Fields, Windows, Forms
   Procedure - Global Scripts
   Database - ADD, DELETE, UPDATE
   Form - Adding an Extras menu
   Often all of the above techniques are used.
   Any questions?

   Congratulations

   Now you all Dexperts!
Thank-you for attending

Shared By:
Description: Dexterity for Dummies;Dexterity for MSGP 10;