v7.0

This is the first release to be distributed as binary installer for both OSX and Windows.

Support for display systems has been greatly improved: display systems are now loaded at runtime based on their name in the configuration file. New display systems can be added to omegalib just by adding their dll or shared library to the binary distribution. The Omegalib core ships with two display systems: Equalizer and GLFW.

Other major changes since v6.0 include python multithreading support, improved logging and several bugfixes to resource allocation and cluster shutdown.

v6.6

Added support for OSX binary distributions using the new installer system.
Added new GLFW display system and displaySystem plugin support.

v6.5

This release comes with an updated version of omicron for better logging support, some improvements on UI widget scaling and several fixes on Texture support (scaling / deallocation)

Full change log: v6.4...v6.5

v6.4

NOTE due to an issue with branch versioning, version 6.3 is not an official release, and is just considered a work in progress towards 6.4. Changes implemented both in 6.3 and 6.4 are reported here.

BREAKING CHANGE: Texture::initialize has been substituted by a generic method with better control over texture and channel format. Old code specifying format using GL_ values will need to be converted. See commit 473e17e

Main Changes

• Added support for filtered log. omegalib by default generates much less verbose logs. Change with -L v option to enable verbose mode, or -L d option for debug mode with even more messages. Added olog and oflog in omicron to support filtered logging.
• Improved Texture class to support more initialization options.
• Improved cluster shutdown
• Pointer colors are now based on user id
• Improved command line parsing (#139)
• Modular system configuration (#96)
• Added deprecation warnings (#138)
• Initial support for new installer system

v6.2

This version adds python multithreading support and some other minor fixes and improvements.

A note on python multithreading
You can execute custom code from other python threads but you should avoid calling
into omegalib functions as much as possible. Some things may work but there are no
guarantees. You should limit using multiple python threads to execute long
blocking operations (i.e. reading data from a file, web IO stuff).

Also note that the python interpreter itself is not designed to support
multithread. In other words, only a single thread will execute bytecode at any
given time. Python functions going out of the interpreter (like the aforementioned
IO operations, hashing code, etc) will let the interpreter run other threads.
Also since omegalib now releases the python interpreter after the update and
event callbacks, if you have threads in your python script they will keep running
while the application does rendering or performs other operations. Since rendering
& other updates are usually the most expensive steps in an omegalib application,
letting other python threads run concurrently could give you a good performance
boost in some scenario. again avoid calling omegalib from those threads, since
there is no way to know what the omegalib runtime is doing at the time (rendering,
updating other stuff, baking bread, etc.)

v6.1

This release fixes some bugs from 6.0.

v6.0

Core for this release will be support for Worskspaces. Most of the changes will be in the MVI module, the core repository will only have supporting changes.

• OSX Yosemite support
• Improved Oculus Rift DK2 support through the oculus module
• reordered initialization sequence so init script can access the display configuration
• (orun) optional string argument is now the application configuration file. This can be used to launch applications directly form their config file.
• Icon-only Button widget
• fixes and improvements to mission control.
  • breaking change recipient specifier in command strings is now ended with a colon character. before: @client doThis() after: @client:doThis(). Also, mission control client uses application name as its identifier.
• canvas size is now updated at runtime depending on what tiles are enabled.
• widget style changes:activeStyleandinactiveStylesupport, addedscaleandalpha` to style options.
• display tile can have 2D grid indices even in custom geometry configurations.
• User-defined quick commands
• Module versioning
• Fully dynamic canvas size
• Support for Visual Studio 2012 (thanks to @caishanli) and 2013
• several gui improvement and bugfixes
• the omegaVtk module adds support for vtk 6.X

v5.3

• Added support for remote application syncing and launching, using the new olauncher command line tool.
• Build fixes for OSX10.9 and XCode 5
• Added headless support for programs that do not need a display (using the Null display type, i.e. in system/headless.cfg)
• Added headless render support using the offscreen option in tile config sections. Useful to create a streaming render server (i.e. to render and stream content to web pages through porthole).
• Improved mouse/keyboard navigation (default = standard fps, Ctrl key pressed for full free fly with no ground plane)
• (equalizer) Fixed keyboard processing for ascii symbol characters.
• Added clearColor, clearDepth, setClearColor to python API
• orun -x option to set startup script command
• added initScript configuration option

omegaToolkit

• Added TextBox widget
• Added source and destination rect to Image widget
• Two new examples, textbox and imgscroll.
• Widget size anchor.

omicron

• Various fixes and improvement to asset cache manager. Now files get transmitted only if a newer version is available. Added fixes to WIndows->Linux/OSX file transfers.
• Event.getChar

v5.2

See release notes here: https://github.com/uic-evl/omegalib/wiki/ReleaseNotes#wiki-omegalib-v52-current-developer-version

v5.1

https://github.com/uic-evl/omegalib/wiki/ReleaseNotes#omegalib-v51