launchpad development|
Size: 1940
Comment:
|
Size: 1420
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 21: | Line 21: |
| Right now this looks like it will be: | A canonical url for a recipe will be: ~owner/+recipe/recipename |
| Line 23: | Line 23: |
| ~owner/distro/distroseries/sourcepackagename/+recipe/recipename | |
| Line 25: | Line 24: |
| * need canonical url specified * need to expose the recipe as a web service entry * need to have traversal to a recipe |
== API == |
| Line 29: | Line 26: |
| '''Note''': on the [[/BuildBranchToArchiveUI#Still%20requiring%20thought|main page]], the current suggestion is for: ~owner/distro/+source/package/+recipe/recipename. This is due to (1) recipes supporting multiple distroseries, and (2) the fact that we can't always know the sourcepackagename (it may be defined in any one of the packaging branches merged in the recipe) and it doesn't make sense to ask the user for it when it's already defined in the packaging). | A recipe should be exposed as a web service entry. |
| Line 32: | Line 31: |
| Mockup needed | Add mockup here. |
| Line 40: | Line 39: |
| * in-page editing of recipe details using multiline lazr-js widget? | * in-page editing of recipe details using multiline lazr-js widget? |
| Line 44: | Line 43: |
| * IHasRecipes (branch, project, distro, distroseries, source package, distro source package) | The following content classes will be adaptable to IHasRecipes: * IBranch * IProject * IDistro * IDistroSeries * ISourcePackage * IDistroSourcePackage |
| Line 48: | Line 55: |
| * +recipes view for IHasRecipes * what to show? |
Add mockup here. |
First Cut of Build Branch to Archive
The purpose of this page is to outline the work that we are going to do for the initial cut, and the proposed (loose) order for getting it done.
The rationale behind this is we'd like to have something actually happen when we get to the stage of having a user use the user interface to create a recipe.
I suggest that we work back end forward. We can use the object factory for all the tests, page tests included. Use the factory inside the harness to see how things are looking for secondary pages - like the recipes for a branch.
Note: nothing is set in concrete
URLs may change, recipe internals may change, we may all turn into flying monkeys.
Canonical URL for recipes
A canonical url for a recipe will be: ~owner/+recipe/recipename
API
A recipe should be exposed as a web service entry.
Page for a recipe
Add mockup here.
- View a recipe in detail, build history on the page for the recipe
Edit page for a recipe
- add edit links to the recipe page
- simple editing first
- in-page editing of recipe details using multiline lazr-js widget?
IHasRecipes
The following content classes will be adaptable to IHasRecipes:
- IBranch
- IProject
- IDistro
- IDistroSeries
- ISourcePackage
- IDistroSourcePackage
Listing for recipes
Add mockup here.
