This session aims to give an inside view of notation: explain what notation is, how it works, and how the use of notation differs or is similar within JS Client-, Omnis Server- and Fat-Client programming. The session begins by covering the basics such as the overall concept, different types of notation, notation shortcuts, optimisation tricks and notation\’92s role in inheritance. Following this, the session advances to more specialised notation relevant to Reporting, List handling, JS Client, Omnis Server programming, Desktop Client programming, etc. Notation is a vast subject and, time permitting, some choices will be made jointly as to which specialised notation the session will cover.
You will learn about:-
* notation as a hierarchical description of the Omnis environment
* the difference between build-in and custom notation, properties and methods, instance and class notation.
* the power of notation in manipulating window/remote forms and their objects.
* the benefits and relevance of notation in inheritance.
* different performance tricks that can be utilised within sever-client and fat-client models.
* notation new to Studio 8/9
* notation and the Studio 8/9 code assistant
* Java Script Client (server/client module overview and detailed look at special client and server notation)
* Special Interest Notation (object variable, complex grid, list notation, report notation)
Last years session focused on creating an external library that was capable of adding custom constants to the Omnis Studio Catalogue. It involved reading constant descriptions from an external JSON file and converting them to a format required by Omnis. The aim was also to provide a mechanism for adding typed constants to Omnis, but there was not enough time to complete this work.\
This year we will build on last year\’92s work and add a non-visual object to the library which provides functions for returning typed constants. It does not matter if you did not attend last years session as we will go over what we did last year and help will be at hand to create your first XCOMP project.\
Knowing how to add non-visual external objects to Omnis is a highly useful skill as it opens up vast amounts of functionality for tight integration into the Omnis language.\
You will learn:-
* how to create a c++ project using XCODE or Visual C++ Express
* what is required to write an Omnis external library for registering constants
* a way of simulating typed constants using a non-visual object
* about the Omnis external SDK
* about various uses for non-visual objects and how to subclass and override the object’s functions in Omnis code
You will learn:
* what is required to write an Omnis JS control design interface