Closed
Bug 899995
Opened 11 years ago
Closed 11 years ago
Do not display the Homescreen section if there is only one homescreen
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Firefox OS Graveyard
Gaia::Settings
Tracking
(blocking-b2g:koi+, firefox28 wontfix, b2g-v1.2 fixed)
People
(Reporter: vingtetun, Assigned: olav)
References
Details
Attachments
(2 files, 1 obsolete file)
Since it is unclear if it will be possible to have multiple |privileged| homescreen for 1.2 I think it would be good to hide the section if there is only one. That will let devs prototype on it while it will not distract users.
Assignee | ||
Comment 1•11 years ago
|
||
This approach iterates over apps on settings startup. Not ideal and very interested in hearing about better approaches.
Attachment #783787 -
Flags: review?(21)
Comment 2•11 years ago
|
||
To do this really correctly, you need also need to listen to mozApps.mgmt.oninstall and onuninstall to make sure you don't end up out of sync with the real list of installed apps.
Assignee | ||
Comment 3•11 years ago
|
||
Absolutely. Added that.
Reporter | ||
Comment 4•11 years ago
|
||
Comment on attachment 783787 [details] [review] github_pointer Can you also check that this does not slow down Settings startup?
Attachment #783787 -
Flags: review?(21)
Assignee | ||
Comment 5•11 years ago
|
||
The mozApps.mgmt.oninstall / onuninstall was already used by settings/js/apps.js so I changed to a scheme similar to the system app with window events for applicationinstall / applicationuninstall . As for the performance test I didn't quite nail it. |APP=settings make test-perf| has some runtime bugs, but printing the results gave me: With patch: [ { time: 522, type: 'w' }, { time: 522, type: 'w' }, { time: 522, type: 'w' }, { time: 522, type: 'w' }, { time: 939, type: 'c' }, { time: 939, type: 'c' }, { time: 939, type: 'c' }, { time: 939, type: 'c' }, { time: 869, type: 'c' }, { time: 869, type: 'c' }, { time: 869, type: 'c' }, { time: 869, type: 'c' }, { time: 863, type: 'c' }, { time: 863, type: 'c' }, { time: 863, type: 'c' }, { time: 863, type: 'c' }, { time: 870, type: 'c' }, { time: 870, type: 'c' }, { time: 870, type: 'c' }, { time: 870, type: 'c' } ] Without patch: [ { time: 437, type: 'w' }, { time: 437, type: 'w' }, { time: 437, type: 'w' }, { time: 803, type: 'c' }, { time: 803, type: 'c' }, { time: 803, type: 'c' }, { time: 789, type: 'c' }, { time: 789, type: 'c' }, { time: 789, type: 'c' }, { time: 786, type: 'c' }, { time: 786, type: 'c' }, { time: 786, type: 'c' }, { time: 792, type: 'c' }, { time: 792, type: 'c' }, { time: 792, type: 'c' } ] So there seems to be startup issues with iterating over the apps like this.
Updated•11 years ago
|
Assignee: nobody → olav
Assignee | ||
Updated•11 years ago
|
Attachment #783787 -
Flags: feedback?(fabrice)
Comment 6•11 years ago
|
||
If load time regressed by almost 100ms that's quite bad for sure :( Not sure how to that differently though since the entry is in the first panel.
Updated•11 years ago
|
Attachment #783787 -
Flags: feedback?(fabrice) → feedback+
Assignee | ||
Comment 7•11 years ago
|
||
As per https://groups.google.com/forum/#!topic/mozilla.dev.gaia/lnYs9kjUtKE I moved all mozApps.mgmt into a lazyloaded script and feel stupid for not doing that earlier :)
Assignee | ||
Updated•11 years ago
|
Attachment #783787 -
Flags: review?(fabrice)
Assignee | ||
Updated•11 years ago
|
Attachment #783787 -
Flags: review?(fabrice) → review?(crdlc)
Comment 8•11 years ago
|
||
Hi Olav, IMHO I am not the correct person to review code in Settings app, the part of the homescreen sounds good for me. Does someone tell you that I should review it? or could we move this review to other person who more knowledge on Settings app?
Flags: needinfo?(olav)
Assignee | ||
Comment 9•11 years ago
|
||
I was told Fabrice was the wrong reviewer. Somewhere between Fernando Rodriguez Sela on the Settings app and you on the Homescreen app and my patch for adding homescreen section to settings I mixed things up :) I'll move it along!
Flags: needinfo?(olav)
Assignee | ||
Updated•11 years ago
|
Attachment #783787 -
Flags: review?(crdlc) → review?(kaze)
Updated•11 years ago
|
Attachment mime type: text/plain → text/x-github-pull-request
Reporter | ||
Comment 10•11 years ago
|
||
We need this patch in koi since there is no way to point of having this section here since homescreen are still certified app in this version.
blocking-b2g: --- → koi?
Comment 11•11 years ago
|
||
(In reply to Vivien Nicolas (:vingtetun) (:21) from comment #10) > We need this patch in koi since there is no way to point of having this > section here since homescreen are still certified app in this version. Agreed during triage.
blocking-b2g: koi? → koi+
Target Milestone: --- → 1.2 C4(Nov8)
Comment 12•11 years ago
|
||
This bug appears to be tracking the fact that you can only have one homescreen, so there's an unnecessary Settings section. Please just remove the section for 1.2, rather than doing anything fancier. When will this work be done? Hopefully in the next day.
Flags: needinfo?(olav)
Assignee | ||
Comment 13•11 years ago
|
||
PR up at https://github.com/mozilla-b2g/gaia/pull/13162 against master This only removes the UI for selecting the section, not the logic for changing homescreens itself. Should it instead be targeted directly at 1.2 branch? If so, should all logic for replaceable homescreens go with it? FYI: https://github.com/mozilla-b2g/gaia/pull/11271 against master still applies nicely :)
Flags: needinfo?(olav)
Assignee | ||
Comment 14•11 years ago
|
||
Attachment #823834 -
Flags: review?(21)
Reporter | ||
Comment 15•11 years ago
|
||
Comment on attachment 823834 [details] [review] Remove homescreen section links from settings This patch just remove the Homescreen section in the panel for 1.2. Let's not land that in 1.3 please, but only in 1.2.
Attachment #823834 -
Flags: review?(21) → review+
Assignee | ||
Comment 16•11 years ago
|
||
Attachment #823834 -
Attachment is obsolete: true
Assignee | ||
Updated•11 years ago
|
Attachment #783787 -
Flags: review?(kaze) → review?(21)
Assignee | ||
Comment 17•11 years ago
|
||
Merged github.com/mozilla-b2g/gaia/pull/13180 into v1.2 Added vingtetun as reviewer for github.com/mozilla-b2g/gaia/pull/11271 against master
Comment 18•11 years ago
|
||
According to comment 15 this bug should only be fixed in v1.2 right? I am marking this as fixed so this won't get pop-up in koi+ query...
Status: NEW → RESOLVED
Closed: 11 years ago
status-b2g-v1.2:
--- → fixed
status-firefox28:
--- → wontfix
Resolution: --- → FIXED
Reporter | ||
Comment 19•11 years ago
|
||
Re-opening since the 1.2 patch is mostly done as a quick version of the real fix for shipping purposes.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 20•11 years ago
|
||
(In reply to Vivien Nicolas (:vingtetun) (:21) from comment #19) > Re-opening since the 1.2 patch is mostly done as a quick version of the real > fix for shipping purposes. This will caused this bug to be flagged as unfixed koi+. Do you mind do that elsewhere?
Flags: needinfo?(21)
Reporter | ||
Comment 21•11 years ago
|
||
Comment on attachment 783787 [details] [review] github_pointer Let's land the real fix.
Attachment #783787 -
Flags: review?(21) → review+
Assignee | ||
Comment 22•11 years ago
|
||
Merged! https://github.com/mozilla-b2g/gaia/pull/11271
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•11 years ago
|
Flags: needinfo?(21)
You need to log in
before you can comment on or make changes to this bug.
Description
•