Closed Bug 1026257 Opened 6 years ago Closed 6 years ago

Would like to be able to set default number of colums in vertical homescreen at build time

Categories

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

x86_64
Linux
defect
Not set

Tracking

(feature-b2g:-, b2g-v2.0 verified, b2g-v2.1 verified, b2g-v2.2 verified)

VERIFIED FIXED
2.0 S4 (20june)
feature-b2g -
Tracking Status
b2g-v2.0 --- verified
b2g-v2.1 --- verified
b2g-v2.2 --- verified

People

(Reporter: dhylands, Assigned: crdlc)

References

Details

(Whiteboard: [systemsfe])

Attachments

(2 files)

I find the 3 column setting to be just too huge on my flame.

So I'd like to be able to somehow tweak the initial value of the preference that controls this at build time.

Normally, I would just create a custom-prefs.js or something, but the vertical home screen doesn't seem to use an actual setting.

For now, I'm editing https://github.com/mozilla-b2g/gaia/blob/master/shared/elements/gaia_grid/js/grid_layout.js#L44 and changing

> _cols : minIconsInRow

to be:

> _cols: 4

I also noticed that on my flame, when I use 4 columns that the rightmost column is slightly cut off, but I find that better than 3 columns.
Blocks: vertical-home-next
No longer blocks: vertical-homescreen
Assignee: nobody → crdlc
Status: NEW → ASSIGNED
Attached file Github pull request
thanks Kevin
Attachment #8441292 - Flags: review?(kgrandon)
Whiteboard: [systemsfe]
Comment on attachment 8441292 [details]
Github pull request

Clearing review for now, added a few comments to github.
Attachment #8441292 - Flags: review?(kgrandon)
feature-b2g: --- → 2.0
Target Milestone: --- → 2.0 S4 (20june)
This is not something that really blocks the feature at all, I consider this more of a developer enhancement at this point. Not sure why it was marked as 2.0.
feature-b2g: 2.0 → -
Comment on attachment 8441292 [details]
Github pull request

I like the changes, thanks.
Attachment #8441292 - Flags: review+
Attached file homescreens.json
You can copy this file to /gaia/distribution/ to test the feature
It would be an interesting feature for OEMs & operators, giving them more flexibility to customize devices, so I would suggest to uplift it to 2.0
Flags: needinfo?(pdolanjski)
We will request uplift for anything that lands in the next few weeks to not put vertical homescreen at risk. If we don't we will run into risks with merge conflicts.
Flags: needinfo?(pdolanjski)
Merged in master:

https://github.com/crdlc/gaia/commit/f3e8effa420e22d1eadad5112311e43674a14d41
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Comment on attachment 8441292 [details]
Github pull request

This is needed for the vertical homescreen.
Attachment #8441292 - Flags: approval-gaia-v2.0?(bbajaj)
Keywords: verifyme
Attachment #8441292 - Flags: approval-gaia-v2.0?(bbajaj) → approval-gaia-v2.0+
Issue verified fixed on Flame 2.0, Flame 2.1, and Flame 2.2

Actual Results: User is able to see and modify variables for homescreen columns in gaia/apps/verticalhome/build/default-homescreens.json and see correct results after build.

Device: Flame 2.0 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141028000202
Gaia: 5e532a84e762b1bb6231756182cf1465671a061e
Gecko: 124f0bed1700
Gonk: 6e51d9216901d39d192d9e6dd86a5e15b0641a89
Version: 32.0 (2.0)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Device: Flame 2.1 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141028001203
Gaia: a0174f7166745256aaca1cb3aa9f894033fbffa6
Gecko: 43bda3541f6b
Gonk: 6e51d9216901d39d192d9e6dd86a5e15b0641a89
Version: 34.0 (2.1)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Device: Flame Master (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141028040202
Gaia: 6a7fb482a03c5083ef79b41e7b0dfab27527cd04
Gecko: a255a234946e
Version: 36.0a1 (Master)
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: verifyme
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
You need to log in before you can comment on or make changes to this bug.