Closed Bug 980935 Opened 7 years ago Closed 5 years ago

Homescreen Gadgets


(Firefox OS Graveyard :: Gaia::Homescreen, enhancement)

Not set


(Not tracked)



(Reporter: zoran.jovanovic, Unassigned)




(2 files, 1 obsolete file)

Provide hooks in homescreen for gadget framework to add, remove, rearrange, resize and interact with gadget in homescreen app.

The initial drop attached (NOTE: work in progress!) is intended as UX proof of concept, comes with some obvious shortcomings, and should serve as proposal for the way forward.

The initial drop provides the following:
    - method to add and remove gadget in Homescreen
      Any type of application can provide a gadget. Application's manifest file defines a gadget, path to its source and placement. UI in Homescreen is added to add/remove gadgets - long tap will open a context menu with wallpapers and gadgets actions.
    - method to fit a gadget in Homescreen's icon grid
      A new icon type is defined for gadget placement.
    - method to interact with gadget and its parent application
      Message handler defines the messages propagated. Gadget can trigger a mozActivity or start the parent application.
    - demo application

The initial drop does not provide:
    - secure process sandboxing (remote mozbrowser iframe does not fork a new process)
    - method to fit a gadget in Lockscreen or utility tray
    - resize functionality
Attached patch gadget-demo.patch (obsolete) — Splinter Review
Blocks: 980929
Attached file gadget_demo.tar
Attachment #8387609 - Attachment is obsolete: true
Depends on: 879475
IMO This won't land before 2.0 (currently named 1.5), thus we should keep an eye on bug 989848 which is the planned 2.0 Homescreen.
Depends on: 1006495
Mass update: Resolve wontfix all issues with legacy homescreens.

As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.
Blocks: 1231115
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.