- When calling the onScreenKeyboard you pass a callback to an event (like you described)
- The display on screen keyboard command is a blocking one and when it completes you call a get results function
- After text is entered a message is sent to the calling plugin with the text.
- An inputEvent is available from the plugin host so any plugin can hook it.
I liked option 4 since it was in line with how most of the rest of the framework was done - and would allow for nice expandability in the future. At the same time I imagine some beginning programmers would like to be able to do something like:
Maybe i'll do option 4 and add a class to the helperFramework that would be getTextFromOSK() and make it easy for users to achieve something like the above in an events driven framework. Sound ok? or am I overlooking the better option?