IRC Log Viewer » #firebreath » 2015-07-20

IRC Nick Time (GMT-7) Message
Beau_ 09:07 taxilian, thanks for the update. Any tips on what to search for in the logs to get a low level understanding about FB2 works in Chrome?
Specifically, will FB2 under Chrome get access to an HWND that it can subclass?
taxilian 10:07 Beau_ no
Beau_ no
that's somewhat deceptive, actually; it's technically possible to get access to an HWND by doing some really creepy HWND-fu, but it will only work on windows and may not continue working forever
that's somewhat deceptive, actually; it's technically possible to get access to an HWND by doing some really creepy HWND-fu, but it will only work on windows and may not continue working forever
Beau_ 10:07 I see. So the Windows version of FB1 exposes the HWND to you directly for NPAPI and ActiveX. Does this mean that FB2 of NPAPI and ActiveX on Windows will also no longer expose HWND? My plugin sort of needs HWND cause I use it to add scrollbars and dialogs as children.
taxilian 10:07 No, we'll still allow access to the window when it's possible to get it
No, we'll still allow access to the window when it's possible to get it
Beau_ 11:07 ok. starting to get my head wrapped around this. So does FB make use of Native Messaging AND NaCL, or just NM?
ok. starting to get my head wrapped around this. So does FB make use of Native Messaging AND NaCL, or just NM?
taxilian 11:07 just NM currently
but one possible method for drawing would be to add a NaCL abstraction in the browser which could be controlled from the NM host to draw
another possible method is to use WebGL across the FireWyrm protocol
Beau_ 11:07 So for a FB2 plugin on Chrome that only uses NM and doesn't access an HWND, does that mean its not possible to draw?
taxilian 11:07 Yes; currently that's exactly what it means
Beau_ 11:07 Ok, thanks. This helps me immensely. Btw, how much do you hate Chrome right now?
taxilian 11:07 LOL. let's just say they're on my list.... =]