Trace: » porting
Porting Harmonia to different platforms.
In harmonia.ui.native.win32.* package I am using simple naming convention:
All functions with names starting with native… needs to be ported as they seen from generic packages. The same is valid for class names: e.g. NativeImage? is a class visible and used by generic code.
There are four native modules and six and only six generic modules importing them.
harmonia.ui.window→ harmonia.ui.native.win32windowharmonia.ui.graphics→ harmonia.ui.native.win32graphicsharmonia.ui.images→ harmonia.ui.native.win32graphicsharmonia.ui.application→ harmonia.ui.native.win32applicationharmonia.ui.exchange.clipboard→ harmonia.ui.native.win32exchangeharmonia.ui.exchange.dnd→ harmonia.ui.native.win32exchange (planned, not in distribution)
This list is frozen and highly probable will not be changed in future.
All other modules do not use any native* functions nor classes now and beyond.
So for porting it is just enough to update version sections in those six files.