Firefox/Windows 8 Integration: Difference between revisions
< Firefox
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
* There is no multi-tasking (Only one app will run unsuspended at a time). | * There is no multi-tasking (Only one app will run unsuspended at a time). | ||
* There are no overlapping windows, nor traditional popup windows, everything is chromeless, everything is designed to be consistent across applications. | * There are no overlapping windows, nor traditional popup windows, everything is chromeless, everything is designed to be consistent across applications. | ||
* Interprocess communication is not possible. (no | * Interprocess communication is not possible. (no electrolysis?) | ||
* Based on WinRT APIs, applications can be built in Javascript, C++, C#, or VB.NET. C++ compiles to native code but has some extra syntax flare. | * Based on WinRT APIs, applications can be built in Javascript, C++, C#, or VB.NET. C++ compiles to native code but has some extra syntax flare. | ||
* Not possible to simply and easily port Firefox as a Metro application. A significant amount of Win32 APIs will not be available in Metro. | * Not possible to simply and easily port Firefox as a Metro application. A significant amount of Win32 APIs will not be available in Metro. | ||
Revision as of 12:18, 26 September 2011
Microsoft Windows 8 will be the next version of the Windows operating system which is aimed at desktops, laptops, netbooks, tablets, servers, and media center PCs. A major part of Windows 8 is the introduction of Metro-style applications which are based on the new WinRT APIs. This page will cover both Windows Metro integration and changes for existing Desktop integration.
Metro support in Windows 8
- Unlike Desktop, Metro apps will ONLY be available through the Windows store.
- There is no multi-tasking (Only one app will run unsuspended at a time).
- There are no overlapping windows, nor traditional popup windows, everything is chromeless, everything is designed to be consistent across applications.
- Interprocess communication is not possible. (no electrolysis?)
- Based on WinRT APIs, applications can be built in Javascript, C++, C#, or VB.NET. C++ compiles to native code but has some extra syntax flare.
- Not possible to simply and easily port Firefox as a Metro application. A significant amount of Win32 APIs will not be available in Metro.
- There is a new concept called contracts for interconnection/sharing with different metro apps.
- The 5 main contracts are: Search, Share, Start, Devices, and Settings.
- A second app can be shown in Metro app with the snap state. It is shown side by side and you can determine the width of each window via a separator.
- The top and bottom edges are for per app toolbars. The left and right edge are reserved for system toolbars (This my require Fennec redesign if we end up using it for Metro).
- You can schedule popup notifications when your Metro app is not running.
Desktop changes in Windows 8
- The start menu is removed. Clicking it now takes you to the Metro interface.
- It is unclear whether or not there will be Desktop support for ARM. If there is support, there will NOT be an emulation layer like WOW64 for x86 apps.
- It is unclear whether or not all Desktop apps get suspended when switching to Metro. (TODO we need to verify this)
- There are taskbar imporvements for multi monitor (taskbar spanning)