You must do your best to not let the reactor pattern go critical while using your window-managing environment. If it does happen to go critical, you could lose all your work, and your monitor could go up in smoke. I did happen to have a monitor go up in smoke on me once. It was crazy.
But seriously, Reactor Pattern is a term that denotes an object-oriented approach to dealing with system-events that happen at any rate, even if they arrive simultaneously, from multiple sources. I'm not too familiar with it, but window-managers and operating systems should pay close attention to things like this. As for a 2d toolkit, every good 3d windowmanager should have one. Hopefully, a hardware accellerated one, in fact, that supports the proper 3d deformations that need to take place before rendering any 2d widgets or graphics to the screen. I feel that 2d and 3d primitives should both be accounted for, before any work on a 3d user-interface occurs. Likewise, there should be support for camera-oriented objects (such as vehicles), as well as objects that are unique to one specific client (such as interface widgets for those vehicles, because you don't want anybody else steering your car if you're the driver). -Steve On 3/9/07, HEBLACK, J <[EMAIL PROTECTED]> wrote: > I saw P.A.'s response about not getting the arbitrary Windows or OS X > frames to render. Slowly I downloaded your two links and then have > attached a demos summary page attachment entitled download via email. So > could this 3d Window Manager referred to contain a 2d toolkit such as > http://fox-toolkit.org? That is one question for you to write back > about. The fox-toolkit snapshot has cross-platform api work containing > threadpools, reactor pattern (who knows what that is!?), and then the > asynchronous call via worker thread to gui thread, and of course a new > event system. _______________________________________________ vos-d mailing list [email protected] http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
