Closed
Bug 916262
Opened 11 years ago
Closed 11 years ago
Replace e.me frame on First Time Experience
Categories
(Firefox OS Graveyard :: Gaia::First Time Experience, defect)
Firefox OS Graveyard
Gaia::First Time Experience
All
Gonk (Firefox OS)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: fade, Assigned: evyatar)
References
Details
Attachments
(5 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.65 Safari/537.36
Expected results:
See approved design for e.me's screen on First Time Experience.
- Prepare translations, if needed
Reporter | ||
Updated•11 years ago
|
OS: All → Gonk (Firefox OS)
Reporter | ||
Comment 1•11 years ago
|
||
What assets in which resolutions should be submitted in order for this screen to be implemented?
Comment 2•11 years ago
|
||
I believe we need to cover:
320x480 and (x1.5) 480x800
Reporter | ||
Comment 3•11 years ago
|
||
I meant preparing the asset of the "screenshot" shown on this screen. Is its size different on multiple resolutions?
Perhaps seeing current assets could help. Where can I find them?
Reporter | ||
Updated•11 years ago
|
Flags: needinfo?(padamczyk)
Comment 4•11 years ago
|
||
You can find all the assets for FTE in here https://github.com/mozilla-b2g/gaia/tree/master/apps/communications/ftu/css/images
Comment 5•11 years ago
|
||
The link from Fernando should you a perspective. We don't need to worry about 2x.
But we'll need everything in this format:
> image.png
> image@1.5x.png
Flags: needinfo?(padamczyk)
Reporter | ||
Comment 6•11 years ago
|
||
Reporter | ||
Comment 7•11 years ago
|
||
Reporter | ||
Comment 8•11 years ago
|
||
Reporter | ||
Comment 9•11 years ago
|
||
Thanks, Fernando and Patryk.
We have already prepared all the three versions. Added as attachments.
Feel free to implement.
Comment 10•11 years ago
|
||
I think I remember something about trying to avoid specific languages on the tutorial, as that would lead to new bugs related with l10n. Is this policy still applies or did it change?
Reporter | ||
Comment 11•11 years ago
|
||
In this specific case, showing search query is crucial for user to understand how it works. Can we somehow embed live text instead? If not, will have to stick with this, it was approved by Patryk and Jamie Chen.
Reporter | ||
Comment 12•11 years ago
|
||
Will go with the attached resources. Please implement.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 13•11 years ago
|
||
Will go with the attached resources. Please implement.
Reporter | ||
Updated•11 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 14•11 years ago
|
||
Can anyone from the FTU team assign himself to this?
Comment 15•11 years ago
|
||
Sure I'll take a look if I manage to get some free cycles
Assignee: nobody → fernando.campo
Assignee | ||
Comment 16•11 years ago
|
||
Fernando, I wanted to try and take this off your plate, but I feel I don't know enough about the strings "politics" with bug 901041 and bug 902487 hanging.
what should be the correct way to approach this?
Should I add a step in the middle, but give it the l10n key "totorial-step6" (even though it won't be the sixth)?
e.me step is designated to be the 3rd.
Flags: needinfo?(fernando.campo)
Assignee | ||
Comment 17•11 years ago
|
||
Attaching a patch - it looks well on the device (approved by our UX guys), but I'm not sure about the FTU code itself.
Attachment #814034 -
Flags: review?(fernando.campo)
Comment 18•11 years ago
|
||
Having in mind the mess going on with FTU strings (as you pointed out, bug 902487 should solve it), I agree with you on the approach, as it's probably the best for the l10n guys.
As this is blocking the release for e.me for 1.2, I'm pinging someone from l10n team to confirm that this is the best approach given the time, and fix the strings on the mentione bug.
About the patch, it looks good, just need a better comment to clarify for future re-coding (on github)
Assignee: fernando.campo → evyatar
Status: UNCONFIRMED → ASSIGNED
blocking-b2g: --- → koi?
Ever confirmed: true
Flags: needinfo?(fernando.campo)
Comment 19•11 years ago
|
||
Comment on attachment 814034 [details]
Patch - redirect to github PR
Giving the r+ assuming that the changes proposed on github are implemented before merging ;)
Thanks for taking this!
Attachment #814034 -
Flags: review?(fernando.campo) → review+
Assignee | ||
Comment 20•11 years ago
|
||
expanded on my comment, though I'm not sure it'll be enough. since I'm probably not the one who will be fixing this when the time comes, I'm willing to comment whatever you feel will make it the most understandable later on :) https://github.com/mozilla-b2g/gaia/pull/12696#discussion_r6792775
Assignee | ||
Comment 21•11 years ago
|
||
also can we ni? the person from l10n? even with the r+, I don't want to merge it without making sure that's the best approach.
Comment 22•11 years ago
|
||
Sure, I totally forgot about it :D So ni for Pike, just to confirm that adding a 6th step string (when we only use 5) is better for l10n team than change the id of the different strings at this stage.
And the comment looks good enough for me, thanks
Flags: needinfo?(l10n)
Comment 23•11 years ago
|
||
ugh, didn't we have a bug to get rid of those numbers altogether? This is the second patch that proves that design wrong.
I suggest to add this string with using a real step name, and not a number.
Flags: needinfo?(l10n)
Assignee | ||
Comment 24•11 years ago
|
||
I agree, it would make it much easier to change and maintain later on. so should I simply change to "tutorial-step-evme"?
Comment 25•11 years ago
|
||
(In reply to Evyatar 'Tron' Amitay (everything.me) from comment #24)
> I agree, it would make it much easier to change and maintain later on. so
> should I simply change to "tutorial-step-evme"?
Sounds good.
Assignee | ||
Comment 26•11 years ago
|
||
no problem, updated the PR.
so with that and the r+ - is this good for landing?
Comment 27•11 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #23)
> ugh, didn't we have a bug to get rid of those numbers altogether? This is
> the second patch that proves that design wrong.
That would be bug 902487, still waiting for triage to dedicate some cycles to it.
> I suggest to add this string with using a real step name, and not a number.
I would rather to change all the names in the other bug, but it's ok with me this way, having even more mess would push us to solve it quicker :)
I checked the failing tests, but doesn't seem related, so I would say we are good to merge. Do you have permissions or should I do it myself?
Assignee | ||
Comment 28•11 years ago
|
||
merged into master!
07b4be36173e28d9c3453a65393b482af32c671f
https://github.com/mozilla-b2g/gaia/commit/07b4be36173e28d9c3453a65393b482af32c671f
Status: ASSIGNED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 29•11 years ago
|
||
E.me 1.2 feature set has been taken out of scope for 1.2 at this point, so not blocking.
blocking-b2g: koi? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•