The Omnis Academy course is perfect for developers with some basic programming knowledge, but who want to learn more – it is ideal for self-employed developers, enterprise developers, students, Omnis partners and any prospects evaluating application development tools. The academy is also great for existing Omnis developers who are using an older version of Omnis but wish to learn about the latest version, Omnis Studio 10.1. In the academy you will:

• Learn how to use Omnis Studio 10.1, one of the most productive and flexible application development environments
• Enhance your programming and application development skills, or develop your career
• Learn step-by-step in a classroom location, with all source code & printed materials provided
• Learn from one of our expert trainers who have many years of experience in application development, training and consultancy
• Meet other application developers, swap ideas, learn from each other!

In the Omnis Academy course you will learn about the Omnis JavaScript Client technology, for developing web and mobile applications with Omnis Studio, including object orientation, database access, JavaScript form and UI design.

In a City near you in 2020

The following countries or regions are hosting our 3 day academy courses in January, February or March in 2020:

More information and Registration

We would love to welcome you along to one of our Academy courses in 2020, and we’re sure you will benefit so much from this training  opportunity – you will be able to start that new project, or greatly enhance your existing Omnis applications, taking advantage of everything that Omnis Studio 10.1 has to offer. Please contact your local sales office for more details, or go to our website to sign up for the academy:

www.omnis.net/developers/academy

Go the link, choose your country or region under ‘In the Classroom’, choose your preferred date, and then fill out your details – we will contact you soon after you register your interest. We look forward to seeing you in 2020!

The post Learn something new in 2020: Web & Mobile Application Development in The Omnis Academy appeared first on Omnis.

Using a Worker in a SQL List or Row

If you want to use a worker object with your SQL list or row, you need to assign a new SQL session property, $useworker to kTrue, but after assigning $sessionobject (after which you can no longer assign $sessionobject, or access $statementobject). There is also a new property $synchronous, which defaults to false meaning use another thread. If set to true (and $useworker is true), the worker object executes synchronously in the current thread.

Selecting & Fetching Data

When using SQL Worker based lists the result set is generated by the worker in a separate thread, therefore the $select() and $fetch() methods cannot be used. In this case, you can use a new method $selectfetch that performs both the select and the fetch of the data ($selectfetch() cannot be used with a row variable and it cannot be overridden in a table class). It has the following definition:

• $selectfetch()
  $selectfetch([bDistinct=kFalse, iMaxRows=1, bAppend=kTrue, cText,…])
  bDistinct
  Pass this as kTrue to make the worker use a SELECT DISTINCT query rather than SELECT.
  iMaxRows
  The maximum number of rows to fetch. Must be between 1 and 10000000 inclusive.
  bAppend
  Pass this as kTrue to append the fetched data to the list, kFalse to replace the list contents with the fetched
  cText,…
  Any further parameters are treated as SQL text and appended to the generated SELECT or SELECT DISTINCT

After fetching the data, the worker generates a notification to $completed in the table instance. When using a worker, you cannot override $insert, $update or $delete in a table class. When you execute these methods via a worker, the table instance copies the current values of the affected row (rows for $update) into the parameter list for the worker, and then starts the worker.

Smart List Methods

When using a worker, you cannot override $do… methods, or call $doinsert, $doupdate or $dodelete. When you call $dowork, $doinserts, $doupdates or $dodeletes, the table instance generates a single query for each of the relevant operations insert, update and delete.

Completion Row

The table instance properties $rowsaffected and $rowsfetched are not relevant when using a worker. $completed in the table instance is passed a row variable parameter with columns: errorcode, errortext, work, errors, and rowsFetched.

For more information about using SQL Worker Objects, refer to the online docs.

The post Faster, more efficient SQL data handling with SQL Worker Lists appeared first on Omnis.

• Command Keywords are added to a command automatically when pressing Tab, enabled using a new option in the Line menu
• Construct Parameters for $add, $open, etc are added as appropriate
• Method name matching to allow you to find a method name as you enter code
• A new option Show Inherited Methods First to display inherited methods at the top of the methods list in the Code Editor
• Closing Quotes, Braces, and Square Brackets are entered automatically, if required after the opening character is entered

Command Keywords

There is a new option on the Code Editor Line menu, Tab Adds Missing Optional Keyword, which is enabled by default. In this case, pressing Tab for commands that have optional keywords, such as Do, For and Enter data, the Code Assistant appends the optional keyword(s) to the command, ready for you to enter its parameter(s). For example, pressing tab after entering Do $cinst.$test() will add the “Returns” keyword. In the case of the For and For each line in list commands, tab will cause the keywords “from”, “to” and “step” to be added in turn.

Construct Parameters

Where possible, the Code Assistant help window now expands “params…” for $add, $open, etc to show the constructor parameters of the class referenced. Omnis identifies the class name that precedes the method name in your code (e.g. classname.$open), and will show the construct parameters for the class.

Method Name Matching

A new keypress has been added to the Code Editor to allow you to search for a method name where the name of a method is required in a line of code. You can press Shift-space after entering a string in the code assistant and any possible matching method names are added to the help list. For notation, if you enter $test and then press Shift-space, the code assistant only shows matching strings that are notation (start with $) and contain “test”.

Showing Inherited Methods First

There is a new option on the View menu of the Code Editor, Show Inherited Methods First, which allows you to display inherited methods at the top of the methods list in the Code Editor; the option defaults to off which means inherited methods will be shown after all other methods at the bottom of the list, as in previous versions.

Entering Quotes, Braces, and Square Brackets

There is a new mechanism in the Code Assistant to detect situations where automatically supplying the ” (closing quote) after typing an “ (opening quote) makes sense. Similarly, a } (closing brace) is inserted automatically where it makes sense after typing { (open brace), or a ] (closing square bracket) is inserted after you enter a valid calculation after entering an [ (opening square bracket); this includes the case when entering a calculation at the end of the parameter for the Sta: command.

More information & Download

For more information about the enhancements in Omnis Studio 10.1, and to download it, please go to the Developer Resources section of our website:
www.omnis.net/developers/resources/download/

You can view or download the ‘What’s New in Omnis Studio 10.1‘ PDF guide from the same page.

The post Enhanced Code Editor in Omnis Studio 10.1 makes developing apps quicker & easier appeared first on Omnis.

The variable panel is displayed in the bottom right area of the Method editor window and allows you to view and modify variables while you debug and step through your Omnis code. It is populated as code execution is paused, such as at a breakpoint. After you resume execution, it remains populated (but disabled) for a short time, until either execution pauses again (when it updates) or execution does not pause soon enough (in this case it clears).

When execution pauses, the focus moves to the variable panel. For example, while stepping through code the Variable panel will show $cinst, the task and instance variable values, and the values of any watched variables: see the Variable panel highlighted in red below.

Omnis Studio 10.1 Variable Panel

Viewing Variable Data

The variable panel has a number of buttons that allow you to drill down into the data, showing Task, Instance, and Local variables, for example. Each time the debugger pauses execution, it refreshes each level of the hierarchy until it reaches a level which is no longer valid. The panel displays variables in a grid using either the row or list representation of the grid as appropriate – you can use the arrow keys or tab/shift-tab to move around the grid. The grid display for a variable or list cell shows a text representation of the value. This may be either its value, or it may be some other representation, e.g. the number of lines in a list, or an object instance name.

A Snapshot of your data

When you first pause execution, the debug window displays the top-level variable panel, with Auto selected by default. The Auto tab shows variables identified from the line before the current executing line (if there is one), the current line, and up to 2 lines after the current line — this gives you a very useful snapshot of the data in your live code.

Download a Free Trial of Omnis Studio 10.1

The new release is available to all supported developers (on the ODPP), or if you would like to try out all the new features, you can download it today and register for a free 90-day trial:
https://www.omnis.net/developers/free-trial/

The post Easier & Faster debugging with new Variable Panel in Omnis Studio 10.1 appeared first on Omnis.