Yes, so we could perhaps extend this to cover the other common areas where we use the UI toolkit for non-UI things (mostly OS interaction, I guess), although at some point it becomes about more than just tools, so the name might be confusing.
On Mon, Dec 4, 2017 at 1:28 PM, Tomasz Wlostowski <[email protected] > wrote: > On 04/12/17 19:23, Jon Evans wrote: > > It's probably a good idea to implement a "toolkit abstraction layer" if > > we ever go down this road, so that we wouldn't have to do it *again* if > > we ever switch again. > > This is the very purpose of the internal event system (TOOL_EVENT, > TOOL_ACTION, TOOL_DISPATCHER) - be able to run interactive tools without > dependencies on the UI toolkit. > > Tom >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
