Difference between revisions of "Architecture"
DougReeder (talk | contribs) (added Enyo Ports UI) |
DougReeder (talk | contribs) (re-organized, added API Design section) |
||
| Line 4: | Line 4: | ||
[[File:LunaNext-Architecture-Diag.png|thumbnail|WebOS Ports Architecture]] | [[File:LunaNext-Architecture-Diag.png|thumbnail|WebOS Ports Architecture]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
[[Luna Next|Luna Next]] | [[Luna Next|Luna Next]] | ||
| Line 40: | Line 36: | ||
[[Enyo Ports UI|Enyo Ports UI]] | [[Enyo Ports UI|Enyo Ports UI]] | ||
| + | |||
| + | |||
| + | == API Design == | ||
| + | Initially, we'll re-implement the webOS APIs. | ||
| + | We'll need some new APIs that are straightforward extensions of existing APIs (for example, [[Synergy_for_Tasks|Proposed Synergy for Tasks]]). | ||
| + | Other new APIs could substantially alter the app environment and user experience (for example, [[Intents|Proposed Lune OS Intents]]). | ||
| + | These must be carefully thought out, so they improve the environment for app developers and user. | ||
| + | |||
| + | When designing new APIs, favor URLs. For example, an attachment could be pulled from the net (http: or git: URL schemes) as easily as a file (file: URL scheme) or immediate data (data: URL scheme). | ||
| + | A contact URL could be an email (mailto: URL scheme), IM address (im:, aim:, sms:, gg:, irc: URL schemes) telephone (tel:, skype: or rtsp: URL schemes) or a web page (http: URL scheme). | ||
| + | |||
| + | == APIs == | ||
| + | Various info bits that still need further working out and documentation: | ||
| + | |||
| + | [[OTA API Blueprint|OTA API Blueprint]] | ||
[[Intents|Proposed Lune OS Intents]] | [[Intents|Proposed Lune OS Intents]] | ||
Revision as of 23:11, 20 May 2015
WebOS Ports Design Architecture
Here will be a description of the architecture of WebOS Ports. How all bits and pieces interact with each other.
Galaxy Nexus Communication Infrastructure
Building Custom LunaSysMgr for Open webOS
Chinese, Japanese, Korean Input Methods
API Design
Initially, we'll re-implement the webOS APIs. We'll need some new APIs that are straightforward extensions of existing APIs (for example, Proposed Synergy for Tasks). Other new APIs could substantially alter the app environment and user experience (for example, Proposed Lune OS Intents). These must be carefully thought out, so they improve the environment for app developers and user.
When designing new APIs, favor URLs. For example, an attachment could be pulled from the net (http: or git: URL schemes) as easily as a file (file: URL scheme) or immediate data (data: URL scheme). A contact URL could be an email (mailto: URL scheme), IM address (im:, aim:, sms:, gg:, irc: URL schemes) telephone (tel:, skype: or rtsp: URL schemes) or a web page (http: URL scheme).
APIs
Various info bits that still need further working out and documentation: