As ever one of the contributors of the system app, where the browser 'app' live in, I am not convinced by applying NGA in system app. Or let's say I am not convinced by NGA.
Today we benefits from NGA is because we are living in the mobile world: nearly all apps are panel-based architecture. This means you could easily think of the panel is an iframe. But system app is the first exception. Generally speaking, system app is not panel based. It's more complex and I call this 'two-dimensional' application architecture. A new "panel" could come from left side(new appWindow) to replace the active "panel" (current AppWindow), or coming from to side (new attention window) without changing anything except visibility of the active 'panel'. It's impractical to treat this kind of transition as what we have in a normal webapp. We definitely don't want any closing AppWindow to be 'swapped out' from memory right away. However I agree that we should split UI-related, or DOM related logic from data model related logic, and I believe this could be done without NGA. Back to the browser 'app' case, regardless the portal page (which is part of search app), it's not difficult to create different browser chrome look and feel for mobile and TV. But what needs to do here is not applying NGA. It will bring us too much trouble, for instance, we will see browser iframe in iframe created by NGA, and it's difficult to maintain the state between the three iframes(system, iframe of NGA, app itself in browser iframe). We just need a TVBrowserChrome submodule and make AppWindow to instantiate it either using build time solution or run time solution. _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
