1020668 - Simulator Device Profiles

Status: RESOLVED DUPLICATE of bug 1090949

(Firefox OS Graveyard :: Simulator, defect)

Description

[Paul Rouget [:paul]]

From the app manager, we should be able to configure a simulator. At least support:
- gaia location
- B2G location
- screen size

The addon is already configurable via about:addons. Maybe we want to leverage that, or have our own mechanism.

Comment 1

[Alexandre Poirot [:ochameau]]

So gaia and b2g location are already configurable from about:addons.
Is this bug just about adding similar pref but for screen size?

There is a --screen option for b2g-bin, so it should only be about
adding a new addon pref in package.json and then passing this pref value to b2g executable from simulator-process.js

Comment 2

[Paul Rouget [:paul]]

I thought we had a user story about that, but can't find it:

Basically, we want the user to build a "simulator profile". We won't show the list of simulators installed in the runtime panel, but a list of simulator profile.

We will have a UI which will let the user select different options (simulator version, gaia profile, B2G directory, screen size, geolocation, ...). He will save these options under a custom name (a profile), and we will show this profile in the runtime panel. The user will be able to configure several profiles.

Comment 3

[Steve Lee]

+ to Paul's suggestion.

A set of predefined profiles or templates for common devices like flatfish or flame would be a useful extra feature. People will want to test against a number of formats - or can this be easily done without UI for test automation?

Comment 4

[Alexandre Poirot [:ochameau]]

Regarding the way gaia works for each product, I think we will have to build/distribute one gaia profile for each target we expect to support without involving the developer to download gaia and build its own profile.
Note that it may end up being easier with the ongoing work on gaia build system, where we expect to be able to build gaia profiles from Firefox. Without any other dependency other than Firefox and gaia sources.

For example, running on a gaia profile and modifying the simulator screen size won't automagically give you a Tablet/TV experience, there is many other tweaks made in gaia profiles.

The overall idea sounds great but mention many things, is there any way to split that in smaller chunks?
Supporting custom gaia/b2g locations is quite different from supporting custom geolocation position or screen size.