I think FLTK devs are likely going to wait until an obvious winner of the battle against X becomes firmly established. Many attempts have been made to replace X only to flounder and fail. I'm glad we didn't waste developer time on those.
When something both establishes and has a stable API, at that point we'd likely start on a dedicated backend driver for the new tech making it an option, leaving X support be the default until it's painfully obvious the new driver is stable and error free.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.