Hello, > Basically RenderBoy is the rendering process and the main browser > process has a ProxyView which forwards mouse moves and clicks to the > render process. The render process draws into a bitmap and sends the > bitmap data to the browser process which displays it in the ProxyView. very cool, this is basically how i planned to implement it, but in my idea, i've imagined the app_server that does the drawing operations instead of sending bitmaps, just because i see it non-efficent. > I don't know if the design is perfect by any means and I'm sure it > could use a lot of clean-up and optimizing, but it does work. From what i know, the RemoteView should handle the redirect process itself, i mean that a programmer should not add any other code in the app hosting the RemoteView...so maybe the way can be to register a BHandler to the app/window? Additionally...maybe there should be a way to distinguish those messages (im_what) from "normal" app_kit notification messages? > I imagine you could download that code and still build it with Jam to > try it out. Already done, i've removed all useless code and split them into two apps...so that these can just go in the test directory of the haiku tree. > Extracting that into a more generic BRemoteView would be nice. I don't > know if I have the time to help, but if you do make that please send No problem, your code is already a good help. > the code back my way, or send a patch so we could maybe put it in > Haiku's shared kit. Yeah sure! Regards