DCP-o-matic

As part of my preparation for the joys of macOS Catalina, it may become convenient for me to drop support for the following macOS versions:

• 10.6 — ‘Snow Leopard’
• 10.7 — ‘Lion’
• 10.8 — ‘Mountain Lion’

Would this cause anybody any great problems?

Is it possible to freeze a 'final version' for these?

- Carsten

Absolutely. It's just a question of whether I can be lazy and build just one 64-bit version on Catalina targeting 10.9, without then having to reboot into High Sierra and build a 32/64 fat version against 10.6.

I still use my trusty white Mac Book running SL, and I still have DCP-o-matic on it - however, I admit I haven't used it much lately. I also still have DCP-o-matic 1.83 and DVD-o-matic on it for 'historical' reasons.

That means - as long as no 'real' problems arise later on due to development system/version issues, in theory you could create an up to date Snow Leopard version any time upon special request? Maybe, as long as this remains relevant, e.g. only for a stable version?

- Carsten

In theory, yes. Although I think dropping 10.6 support would allow us to use some more "modern" (i.e. only 10 year old!) bits of C++, which would be nice. If I've got that right the code wouldn't build any more on 10.6.

Okay, well, I guess, SL, it is actually more nostalgia felt for my Mac Book. Bought it late 2006.

SHRIEK, 13 years...

What do you think, how far away is 2.16?

- Carsten

I haven't really thought about 2.16. We need to consider what should go into it. I feel like a functioning GL backend and direct disk writing might be nice to shoot for...