[tizen_window_manager] Add tizen-core-wl window backend#1057
Conversation
There was a problem hiding this comment.
Code Review
This pull request introduces a WindowProxyInterface and a WindowProxy wrapper to abstract window operations, allowing the Tizen window manager to dynamically switch between EcoreWl2WindowProxy and a new TizenCoreWlWindowProxy backend depending on the platform version. Feedback on the changes suggests resolving and caching the dynamic library symbols in the constructor of TizenCoreWlWindowProxy rather than on every method call. This optimization would also ensure that if any required symbols are missing, the proxy can gracefully fall back to the EcoreWl2WindowProxy backend.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
4c66c75 to
e3d4a47
Compare
Introduce a WindowProxyInterface abstraction with two backends selected at
runtime by WindowProxy:
- TizenCoreWlWindowProxy (tizen-core-wl) on Tizen API version >= 11.0 when
the library is available
- EcoreWl2WindowProxy (ecore_wl2) otherwise, including as a fallback when
tizen-core-wl cannot be loaded on 11.0+
Both backends implement WindowProxyInterface (GetGeometry/Activate/Lower) and
resolve their symbols at runtime via dlopen/dlsym. TizenWindowManager
constructs WindowProxy, which picks the backend by querying the platform
version at startup.
e3d4a47 to
7bf463a
Compare
Introduce a WindowProxyInterface abstraction with two backends selected at runtime by WindowProxy:
Both backends implement WindowProxyInterface (GetGeometry/Activate/Lower) and resolve their symbols at runtime via dlopen/dlsym. TizenWindowManager constructs WindowProxy, which picks the backend by querying the platform version at startup.