On Nov 11, 2003, at 2:14 PM, tuviah snyder wrote:
Embedded Revolution supports access to the main event loop. The idea behind embedded Revolution is you would link your external code with librev and compile a custom engine. The advantages are
1) no external overhead on Linux. 2) Single file executable 3) Access to event loops.
That's good to know. What is the availability/licensing of Embedded Revolution?
I don't see why we can't support access to the event loop for externals as well..the external would need to register the callback however to avoid any performance problems.
Can you describe the purpose of X_main_loop(), X_set_pre_xevent_handler(), and X_set_post_xevent_handler() in XCmdGlue.c? Is that what you are referring to in item 3) above, or is it something else?
We are working on it. Tim Monroe just wrote an excellent article on developing QT externals with Rev, and we plan to extend on some of that for our own docsSDK docs would be good, but I fear they would only confirm we have a lot of work to do to do any useful externals.
Is RR providing externals API documentation in addition to a tutorial? Not knowing the purpose and usage of most of these functions is the main problem for me.
Alex Rice <[EMAIL PROTECTED]> | Mindlube Software | <http://mindlube.com>
what a waste of thumbs that are opposable to make machines that are disposable -Ani DiFranco
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
