Closed
Bug 678650
Opened 14 years ago
Closed 14 years ago
Make a developer front end for add-on dependencies
Categories
(addons.mozilla.org Graveyard :: Developer Pages, defect, P3)
addons.mozilla.org Graveyard
Developer Pages
Tracking
(Not tracked)
RESOLVED
FIXED
6.2.5
People
(Reporter: clouserw, Assigned: cvan)
Details
(Whiteboard: [t:muffin][qa+])
The database and models are all hooked up for add-on dependencies already but we don't reveal that on the front end at all. Please find on the edit add-on listing page to give authors the opportunity to declare add-on dependencies. There should be some reusable chunks of UI in the admin tools (auto-complete for add-ons search and cvan's feature editor page come to mind).
There is the potential for cross app/add-on dependencies so let's not restrict add-on type I suppose.
I thought chowse had mockups for how to reveal this on the detail pages but I don't see them now. Regardless, we can solve that in another bug once this is hooked up.
| Reporter | ||
Updated•14 years ago
|
Priority: -- → P3
Comment 1•14 years ago
|
||
the mocks are linked from the marketplace spec
| Reporter | ||
Comment 2•14 years ago
|
||
found a mockup! http://moz.howsehold.org/amo/devtools/v3/manage_addon/03_edit_listing_expanded.png
I see fligtar already commented 20 minutes ago, but I'm doing it anyway.
| Reporter | ||
Updated•14 years ago
|
Assignee: gkoberger → cwiemeersch
| Reporter | ||
Updated•14 years ago
|
Target Milestone: 6.2.1 → 6.2.2
Updated•14 years ago
|
Whiteboard: [t:muffin]
| Assignee | ||
Updated•14 years ago
|
Target Milestone: 6.2.2 → 6.2.3
| Reporter | ||
Updated•14 years ago
|
Target Milestone: 6.2.3 → 6.2.4
| Assignee | ||
Comment 3•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: 6.2.4 → 6.2.5
| Reporter | ||
Comment 4•14 years ago
|
||
waffle flag is edit-dependencies; enabled on -dev
Whiteboard: [t:muffin] → [t:muffin][qa+]
Updated•10 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
•