Closed
Bug 631961
Opened 14 years ago
Closed 13 years ago
Platform options for add-ons which support mobile + other apps
Categories
(addons.mozilla.org Graveyard :: Developer Pages, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
6.0.4
People
(Reporter: krupa.mozbugs, Assigned: kumar)
References
()
Details
(Whiteboard: [Step 2][qa+])
Attachments
(2 files)
steps to reproduce: 1. Create an add-on which is supported on Mobile+Firefox 2. Upload the add-on 3. Observe the available platform options expected behavior: Available platform options are: Firefox-a) All platforms b)MACOSX c) Windows d)Linux Mobile- a)All platforms b)Maemo c)Android observed behavior: The only available platform option is "All Platforms"
Reporter | ||
Comment 1•14 years ago
|
||
Comment 2•14 years ago
|
||
Kumar was working on these. Kumar, if you have questions, let me know.
Assignee: nobody → kumar.mcmillan
Priority: -- → P2
Target Milestone: 5.12.9 → 5.12.10
Assignee | ||
Comment 3•14 years ago
|
||
I forgot to mention it in the first bug but Jeff and I decided to postpone multi-platform options in the case of an Add-on that supports multiple apps because it introduces a lot of extra complexity and effort. To complete this feature as requested, some logic around the Files data model will need to change. For example, the concept of All Platforms currently results in single file whereas this feature would require All Platforms to result in a single file *per application*. This would be a significant change that affects a lot of pages: upload / download / version management. There might be another way to implement it, like creating an All Platforms file then excluding certain platforms per app on download screens. How common is this use case? I.E. when would an addon author provide a *single* file that is limited to supporting, say, Windows and Android? I'd guess that in most cases an add-on with a single file supporting both desktop and Android would target All Platforms.
Comment 4•14 years ago
|
||
What kumar said too nicely is: this doesn't make sense.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Comment 5•14 years ago
|
||
(In reply to comment #3) > How common is this use case? I.E. when would an addon author provide a > *single* file that is limited to supporting, say, Windows and Android? I think specific platforms for both desktop and mobile will be rare, but I think All Platforms on desktop and one platform on mobile will be quite common. When I originally mocked up the UI that Krupa mentions (http://people.mozilla.com/~fligtar/devcp/zamboni/submission.png) I imagined a new mobileplatform column in files that would work the same way as as the main platform field. These platforms aren't tied to a specific application, but to a device format. Just as Firefox, Thunderbird, Seamonkey, etc. all share desktop platforms, if there was a Mobile Thunderbird it would share the same platforms field with Mobile Firefox.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Updated•14 years ago
|
Target Milestone: 5.12.10 → Q1 2011
Comment 6•14 years ago
|
||
Is this something we want to support? Shouldn't the mobile version of an add-on be as small as possible?
Status: REOPENED → NEW
Assignee | ||
Comment 7•14 years ago
|
||
In the mockup, what happened to the "I have another platform file" checkbox and the "upload another file" button on the initial submission page? That would help address the issue, I think.
Comment 8•14 years ago
|
||
was overruled in the design phase
Comment 9•14 years ago
|
||
Is the course of action clear here or should we have a design meeting?
Target Milestone: Q1 2011 → 5.12.11
Updated•14 years ago
|
Target Milestone: 5.12.11 → Q1 2011
Updated•13 years ago
|
Target Milestone: Q1 2011 → 6.0.3
Assignee | ||
Comment 10•13 years ago
|
||
There is contradictory info here. What the original feature request asks for (I think) is two groups of checkboxes: 1) Which desktop platform is this file for? ...; 2) Which mobile platform is this file for? However, fligtar says that this was removed from the final mock up. Should we go back to the original mock up and implement the two groups of checkboxes?
Comment 11•13 years ago
|
||
I'd like the checkboxes laid out as in the original mock, but I think the issue we'll run into is that the platform choices depend on which applications are supported and (I think) we show the platform options before parsing install.rdf. Ideally we would show the platform choices after parsing install.rdf, based on the AJAX response from the validator.
Assignee | ||
Comment 12•13 years ago
|
||
ok, I'll lay it out like the original. Actually, we do already use an ajax response after parsing the install.rdf -- this is how we know currently to show the mobile platforms.
Updated•13 years ago
|
Target Milestone: 6.0.3 → 6.0.4
Updated•13 years ago
|
Whiteboard: [Step 2] → [Step 2][qa+]
Updated•13 years ago
|
Priority: P2 → P1
Assignee | ||
Comment 13•13 years ago
|
||
Fixed in https://github.com/jbalogh/zamboni/commit/2a48fdbb3407a5c43c0c0a4fd8a258a94b671c56
Status: NEW → RESOLVED
Closed: 14 years ago → 13 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 14•13 years ago
|
||
Note that there are a couple side effects to this fix (but nothing worse than how it was before) bug 646266 bug 646268
Reporter | ||
Comment 15•13 years ago
|
||
Filed bug 649497, bug 649486, bug 650038, bug 650040, and bug 650031. New bugs will be filed separately. Marking this as verified.
Status: RESOLVED → VERIFIED
Updated•8 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•