Closed
Bug 758128
Opened 13 years ago
Closed 11 years ago
Add the Manifest Builder
Categories
(Marketplace Graveyard :: Developer Pages, enhancement, P5)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: gkoberger, Unassigned)
References
()
Details
(Whiteboard: u=dev c=design p=3 [feature])
Attachments
(1 file)
|
293.54 KB,
image/png
|
Details |
Code: https://github.com/gkoberger/zamboni/commit/2b14079
Spec: https://docs.google.com/document/d/1kxHfrJ4U8-s_VA_btoQMzprI2tcmmYCONx25eMsgBC8/edit
Notes:
* Review this code. I seem to remember putting tmp files somewhere and not cleaning them up.
* The code above doesn't add resized images. We should do that.
* Later we can add advanced features such as "launch_path" or whatever else. Let's do a basic one first. (name, description, resized icon images)
Comment 1•13 years ago
|
||
This is something we've discussed about implementing to help ease the manifest creation->app submission process. A once over from UX would be awesome.
Whiteboard: [ui]
Updated•13 years ago
|
Comment 2•13 years ago
|
||
We might add a manifest builder to the devhub in the general context of the app generator.
Assignee: cvan → nobody
Whiteboard: [devhub]
Comment 3•13 years ago
|
||
CCing dbuc for roadmap consideration
Keywords: productwanted
Whiteboard: [devhub] → u=dev c=design p=3
Updated•12 years ago
|
Component: Developer Pages → Web Components
Product: Marketplace → Developer Ecosystem
Version: 1.0 → unspecified
Updated•12 years ago
|
Component: Web Components → Developer Pages
Keywords: productwanted,
uiwanted
Product: Developer Ecosystem → Marketplace
Version: unspecified → 2014-Q2
Updated•12 years ago
|
Whiteboard: u=dev c=design p=3 → u=dev c=design p=3 [feature]
Comment 5•11 years ago
|
||
We think this replaced by the dev tools initiatives.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Comment 6•11 years ago
|
||
(In reply to Andy McKay [:andym] from comment #5)
> We think this replaced by the dev tools initiatives.
:( Is it though?
Comment 7•11 years ago
|
||
(In reply to Christopher Van Wiemeersch [:cvan] from comment #6)
> (In reply to Andy McKay [:andym] from comment #5)
> > We think this replaced by the dev tools initiatives.
>
> :( Is it though?
It has to be. If editor/templates/validation (and whatever else I might be forgetting) are not good enough, let's drive the requirements over there, not layer on additional user paths. Hit me up if you have concerns.
You need to log in
before you can comment on or make changes to this bug.
Description
•