4 days / 20 talks
Awesome and great speakers

November 3-8

Jean Marc Azerad

Unlike many Omnis developers, Jean Marc’s first career was not programming, he earned his living doing research in sensorial neuro-physiology.
As a self-taught early adopter of personal computers (first Apple II in 1977), around 1984, he was teaching computers to adults as a student job to finance his Ph.D. His audience was essentially composed of business managers or accountants that knew they had to make the step to computers but were constantly confronted with weird young salespeople speaking an obscure language.
In 1985, he discovered Macintosh, realized it was THE tool those guys needed and that, with some good application building tools, he could make dedicated, easy to use, software for them.
He began with Omnis 3 in 1986 and keeps on writing software with an emphasis on making the Man/Computer relationship as simple as possible, taking advantage of his backgrounds in sensorial neuro-physiology and psychology.
The conversion, which wasn’t for the weak of heart, ended up being more of a rewrite, as all the code was made more object-oriented and was re-coded to use SQL instead of Omnis Data Files. Throughout the conversion he learned how to eke out every ounce of performance from Omnis Studio using Omnis tricks and C++ externals.

In addition to Omnis he also has a great deal of experience with PostgreSQL, PL/PGSQL stored procedures and triggers, Objective-C, and C++ externals and has used it to great advantage to make Theatre Manager faster and more capable. He’s always on the lookout for cool new things to integrate into Omnis so that he can make faster and more useful software.

About Debbuging

“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.“

Brian W. Kernighan (stolen from Mark Philips)

Studio uses an interpreted langage, not a compiled one. It makes it a fantastic langage when it comes to debugging. Set a breakpoint, have a look at the content of a variable and click on “Go” to execute the code, this is magical!

But do you know there is more?

Do you know how to use trace logs? Breakpoints on variable changes? Have you had a look at the method checker?

If the answer is yes, you don’t need this session but otherwise, you may get some productivity improvements by coming.

Studio’s IDE power unleashed

This session is not only about tips and tricks on the Omnis Studio IDE but also a place to collect wishes on your expectations for future versions.

We’ll talk about tools included in the IDE, with, sometimes, unknown useful features: the catalog, the notation inspector, the interface manager…



Follow Jean



About workshops


You’ll sign up for the session you want to attend on a first-come, first-served basis. Up to 6 participants may attend a session, if full, you can sign up for the same topic at a different time. During the session, the speaker will guide the audience through the main topic but you will be able to ask him/her to deviate and cover related areas. Sometimes participants offer new ideas and solutions to a problem.

Check the


Pursue any question or area not directly related to the core topic. Every speaker hosts at least 4 sessions which means there are about 11 to 12 simultaneous sessions running all the time with an average of 5 or 6 participants

Meet the Speakers

Check the


Flexible conference format means you can choose the best classes for you and at the best time. Some sessions will be repeated, so when you miss one, you can attend the same session later in the day or the week.

Check the Schedule