1940
Comment:
|
2510
|
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 * need canonical url specified * need to expose the recipe as a web service entry * need to have traversal to a recipe '''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). == Page for a recipe == Mockup needed * 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? |
|
Line 44: | Line 26: |
* IHasRecipes (branch, project, distro, distroseries, source package, distro source package) | The following content classes will be adaptable to IHasRecipes: |
Line 46: | Line 28: |
== Listing for recipes == | * IBranch * IProject * IDistro * IDistroSeries * ISourcePackage * IDistroSourcePackage |
Line 48: | Line 35: |
* +recipes view for IHasRecipes * what to show? |
== Pages for a recipe == === Recipe Index === [[http://people.canonical.com/~rockstar/RecipeView.png|RecipeView]] The index page will have links to edit all the editable fields. The recipe contents will be editable in a separate view from the rest of the recipe. Eventually, we can probably use the lazr-js widgets that correspond with each form field for editing inline. === Add Recipe === [[http://people.canonical.com/~rockstar/RecipeAdd.png|RecipeAdd]] Eventually, we'd like to implement a better method for creating a recipe (like a wizard that will actually write the recipe contents for the user (making it easier to create a recipe). For now, we'll prepopulate the debian version string field, and automatically start the recipe contents with the bzr-builder version string. === Edit Recipe === Basic editing page... This flow provides for people without javascript enabled. === Recipe Listings === [[http://people.canonical.com/~rockstar/RecipeListing.png|RecipeListing]] The listing view will be available for all content classes providing IHasRecipes. === Branch Index New Recipe Portlet === On a branch page, we'll add a portlet for viewing the build history of all related recipes, with a link to view the recipe listings as well as a link to create a new recipe for the branch. [[http://people.canonical.com/~rockstar/RecipeBranchPortlet.png|RecipeBranchPortlet]] == API == A recipe should be exposed as a web service entry. |
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
IHasRecipes
The following content classes will be adaptable to IHasRecipes:
- IBranch
- IProject
- IDistro
- IDistroSeries
- ISourcePackage
- IDistroSourcePackage
Pages for a recipe
Recipe Index
The index page will have links to edit all the editable fields. The recipe contents will be editable in a separate view from the rest of the recipe. Eventually, we can probably use the lazr-js widgets that correspond with each form field for editing inline.
Add Recipe
Eventually, we'd like to implement a better method for creating a recipe (like a wizard that will actually write the recipe contents for the user (making it easier to create a recipe). For now, we'll prepopulate the debian version string field, and automatically start the recipe contents with the bzr-builder version string.
Edit Recipe
Basic editing page... This flow provides for people without javascript enabled.
Recipe Listings
The listing view will be available for all content classes providing IHasRecipes.
Branch Index New Recipe Portlet
On a branch page, we'll add a portlet for viewing the build history of all related recipes, with a link to view the recipe listings as well as a link to create a new recipe for the branch.
API
A recipe should be exposed as a web service entry.