4 days / 20 talks
Awesome and great speakers
Doug Easterbrook
In order to fulfil that goal, Doug Easterbrook, the founder of the company, has been developing with Omnis since 1986. Our cornerstone application, Theatre Manager has been through 5 re-writes: Omnis 3+, Omnis 5, Omnis 7, Studio and are in the process of rebuilding the web services component using current open source web standards in conjunction with Studio as servers. The development team have done some amazing and innovative things which will form the foundation of our session topic(s).
Some of the key technologies implemented in Theatre Manager and in use by over 300 theatrical and sports venues:
Omnis Studio 5.3.2
PostgreSQL server
Scaleable ultra-thin web client using a custom apache module or nginx web servers
Use of externals in key areas to extend the capabilities of Studio
An application architecture that allows us to build new applications quickly with a high degree of re-use
In the sessions, we are very happy to share all our experiences of building world class scaleable applications in a number of subject areas in the application development lifecycle…. from design->coding->testing->deployment->error reporting (and repeat).
Bootstrap and Adaptive Web Pages
This session will show you a number of web marketing facts that illustrate why you want to consider using bootstrap for your web pages, how to theme them quickly and easily and the process of converting HTML3 web pages to HTML 5 so that they run on all devices without changes. If you are using ultra-thin web pages, see why a lot of web designers around the world use bootstrap.
The responsive bootstrap web pages have been a key element in Arts Management’s efforts to help customers rebrand their web sites and we are finding that their patrons have far less questions about how to use the pages and far more shopping cart completions — on all kinds of devices.
Part of the discussion include effects on old and supported browsers, use of Font Awesome, web site and commerce requirements, utilities to check what your site can support and evaluate SSL certificates for security.
Improve Studio performance with a bag full of Postgres tricks
omnis and how it handles changes to the list (things to avoid),
* where stored procs can help to do things that prevent list changes, * alterations to the table class to minimize data transfer
* defaults for key creation
* referential integrity setup
* triggers to do things at source
* background worker strategy
* listen notify
* backups, tips, and other site management things
* upgrading versions
* postgres dam settings
* use of returning and the performance gain
* implementing some of this in the table class
* caching strategies
Also:
adding in things like ‘upsert’ ( in insert if fail, then update in one statement – in postgres 9.5 – which has helped for performance of things we’ve done in workers
implementing time zone awareness in an omnis application with postgres (its pretty dead easy, but took me a few days to solve the problem)
UPSERT Which is an insert, if fail UDPATE — which I’ve also built into a table class. Where we use it — saving window positions where we expect them to be there (but they might not) and duplicates are not allowed. so rather than find, if exist, update, else insert (2 statements), it becomes one —> insert, on duplicate fail, udpate. its great for some conditions.
and more
