ofWorks and openFrameworks strenghts

[dimitre]

ofWorks and OF strenghts

First overall strenghts of each one.

ofWorks

• housekeeping done, up to date libs and build system, ready for core development
• reproduceable recipes
• bootstrap script from zero to demo at once.
• ofLibs pinned down all libraries to same exact commit. easy library updating system.
• static libraries whenever possible, more resilent to dependency hell
• use static libs automatically by dropping in a folder called libs inside project
• create software icon by creating a folder called icon and putting a png there (.ico in windows)
• Templates for ZED editor and Chalet build system
• Can advance more freely, not locked into printed books or old projects
• Dropped hard to maintain projectGenerator and apothecary
• Dropped FreeImage. hard to build with latest dependencies like libtiff and png, to have everything up to date

openFrameworks

• Multiple active developers
• Support legacy Raspberry PIs (teoretical)
• Android support on older versions
• iOS/Simulator support. not planned until Chalet support xcframeworks
• proper emscripten support. most libs are building in ofLibs but untested
• projectGenerator frontend in Electron
• make build system
• vs2019 direct support (ofWorks can generate VS2019/2022/2026 through Chalet export)

Functionality

ofWorks

• retina window support. minor tweaks to fix
• macos with FFT support (with kissfft atm)
• video player set position without delay
• rewritten GLFW window handling and a little bit different API (more on that soon)
• crude RGFW support
• cleaner codebase, long deprecated functions gone
• much leaner ofToDataPath

TODO

• [] write about GLFW differences