Active Scripting was the interface used by Internet Explorer versions 3 through 8 to bind scripting engines like JScript and VBScript. It provided COM interfaces for the scripting engine and host applications to communicate. Active Scripting was used by IE, Windows Script Host, ASP, Office applications, and other third party apps to integrate scripting. It required scripting engines to implement interfaces like IAcriptScript and allowed hosts like IE to debug scripts through COM debugging APIs. With IE9, Microsoft moved to a new scripting model that replaced Active Scripting.
This document discusses Firefox OS and its use of e10s (electrolysis) architecture. It covers the process model used in Firefox OS including the b2g process, plugin container process, and hardware access. It also summarizes the Inter-Process Communication (IPC) mechanisms like IPDL, network APIs like XMLHttpRequest and WebSockets, as well as inter-app communication capabilities in Firefox OS like Web Activities and direct app connections.
Active Scripting was the interface used by Internet Explorer versions 3 through 8 to bind scripting engines like JScript and VBScript. It provided COM interfaces for the scripting engine and host applications to communicate. Active Scripting was used by IE, Windows Script Host, ASP, Office applications, and other third party apps to integrate scripting. It required scripting engines to implement interfaces like IAcriptScript and allowed hosts like IE to debug scripts through COM debugging APIs. With IE9, Microsoft moved to a new scripting model that replaced Active Scripting.
This document discusses Firefox OS and its use of e10s (electrolysis) architecture. It covers the process model used in Firefox OS including the b2g process, plugin container process, and hardware access. It also summarizes the Inter-Process Communication (IPC) mechanisms like IPDL, network APIs like XMLHttpRequest and WebSockets, as well as inter-app communication capabilities in Firefox OS like Web Activities and direct app connections.
This short document discusses HTML5 and localization. It questions who benefits from BML and emphasizes thinking globally rather than locally, while also noting the need to localize. The document ends by stating a belief that the internet should be public, open, and accessible.
6. Terminology for gfx
• Core
Graphics
• OSX
• Direct
API (and iTunues for Windows?)
2D
• Windows
(Vista + Update / 7+)以降で使える2D API
• OpenGL
• クロノスグループで定義している3D
API
7. Terminology for gfx
• Cairo
(by RedHat, Intel and etc)
• GTK等で利用されている2D
API
• 様々なバックエンドを持つ
• Skia
(by Google)
• AndroidやChromiumで利用されている2D
API
• オプションとしてOpenGLバックエンドを利用可能
8. Terminology for Gecko’s gfx
• Thebes
• 現在も使われているグラフィック
API (Gecko 1.9 /
Firefox 3から採用)
• Moz2D
(Azure)
• 新しい2D
API (Gecko 7から採用)
• Layers
• “Compositor”
(animation / color conversion and etc)
9. Terminology for Gecko’s gfx
• OMTC
• Off
Main Thread Compositing
• APZC
• Async
Pan/Zoom Controller
26. References
• Graphics
in Mozilla – Part 1
• http://blog.vlad1.com/2007/12/11/graphics-in-
mozilla/
• Introducing
the Azure project
• https://blog.mozilla.org/joe/2011/04/26/introducing-
the-azure-project/
