Linked by Thom Holwerda on Mon 13th Feb 2012 23:40 UTC
Mozilla has announced plans to integrate its Firefox web browser with Metro for Windows 8 - including Gecko. "Windows 8 contains two application environments, 'Classic' and 'Metro'. Classic is very similar to the Windows 7 environment at this time, it requires a simple evolution of the current Firefox Windows product. Metro is an entirely new environment and requires a new Firefox front end and system integration points. The feature goal here is a new Gecko based browser built for and integrated with the Metro environment. Firefox on Metro, like all other Metro apps will be full screen, focused on touch interactions, and connected to the rest of the Metro environment through Windows 8 contracts." I haven't checked - does Microsoft allow different rendering engines?
Post a Comment
Member since:
2005-07-06
RE: Different Rendering Engines
by mattymoo on Tue 14th Feb 2012 01:05 UTC
in reply to "Different Rendering Engines"
Member since:2011-12-29
RE[2]: Different Rendering Engines
by BrianH on Tue 14th Feb 2012 01:26 UTC
in reply to "RE: Different Rendering Engines"
Member since:2005-07-06
RE[3]: Different Rendering Engines
by vaette on Tue 14th Feb 2012 10:47 UTC
in reply to "RE[2]: Different Rendering Engines"
Member since:2008-08-09
Right, the native code support in WinRT is changing the picture quite significantly for porting efforts. Extremely portable pieces of software like Firefox and Opera will still take a lot of effort (just a thing like the lack of complete file system support), but it is clearly doable and more or less a no-brainer to port to an operating system that is certain to be one of the main players in the future.
Member since:
2006-05-12
Member since:2008-08-09
They would probably need a new plugin model that is itself suited for WinRT though, since the APIs and application lifecycle models are so different (and NPAPI/ActiveX/whatever plugins of today are really very general applications with some added hooks). Once that is in place though there is no real reason not to have plugins.
Member since:2008-07-15
They would probably need a new plugin model that is itself suited for WinRT though, since the APIs and application lifecycle models are so different (and NPAPI/ActiveX/whatever plugins of today are really very general applications with some added hooks). Once that is in place though there is no real reason not to have plugins.
Depends on the particular plugin. Several Firefox plugins, in particular those that don't need to go outside of the browser environment, are simply written in Javascript. I would imagine that keeping support for these wouldn't be difficult.