Gaia/Architecture Proposal: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 438: Line 438:
* [https://groups.google.com/d/msg/mozilla.dev.gaia/TTl90CZoOvg/eaLTf_iIde4J Delta Updates vs. Signed Resources]
* [https://groups.google.com/d/msg/mozilla.dev.gaia/TTl90CZoOvg/eaLTf_iIde4J Delta Updates vs. Signed Resources]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1036275 Support http-served packaged HTML pages/apps]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1036275 Support http-served packaged HTML pages/apps]
== Are there still any plans to break the apps out into their own repos, instead of having them all in the same Gaia repo ==
Yes. There is plan to break apps into [ app backend + (n * app_front_end_per_device) + toolkit repo(s)]
== Are we still going to be giving support for packaged apps? ==
We will probably be supporting packaged apps in the platform to ensure backwards compatibility for a while and we will have to have apps running the new architecture alongside packaged apps for a while in Gaia. Mostly because we may not convert all of them at once. But we should probably stop allowing new packaged apps additions to the Marketplace at some point.
== Are we considering actually having separated pages and multi page apps in the window manager, having different urls for each page. For example to have a different url for each contact? ==
Yes. Deep linking with a unique url by default is one of the goal. For now the Content Wrapper is on the way. The goal is to get rid of it asap. But we need a few new platform features to do that.
Confirmed users
483

edits

Navigation menu