launchpad-dev team mailing list archive

[Michael Nelson <michael.nelson@xxxxxxxxxxxxx>]

On Wed, Feb 3, 2010 at 12:38 PM, Michael Nelson
<michael.nelson@xxxxxxxxxxxxx> wrote:
> On Tue, Feb 2, 2010 at 3:15 PM, Martin Albisetti <argentina@xxxxxxxxx> wrote:
[snip]
>> - I wonder why the packaging branch isn't something you can search for
>> and change. IIRC, there are some advanced use cases where you use more
>> voodoo, but the common case would be marvelously simple if you would
>> just select a packaging branch to create a recipe
>
> I'm not sure how we could establish that link in the general case
> (eg., I have a packaging branch in my +junk area?) But assuming that
> it is possible, yes, the packaging branch could be a(n optional)
> selector or inline branch picker.
>
> This would mean that the text area would only be required for specific
> recipes that merge multiple packaging/fix branches. Which leaves me
> wondering whether we even should/need to convey the structure of the
> actual recipe (ie. we could remove the uneditable header, and just
> have a normal form with fields, rather than trying to emulate the
> recipe text). We headed down this direction because there is no
> standard way to construct a recipe and so I thought we'd need to
> expose the recipe for what it was. But all of the above fields are
> applicable to the various types of recipes (as long as the packaging
> branch option is optional). As long as we always enable the text area
> at the end so power users can add custom merge directives etc., we
> should be able to cover the most common use-cases without exposing the
> recipe?
>
> I'll have a play with other layouts (after thinking more about James' points).
>

I've put an example of the overlay that doesn't try to display the
structure of a recipe, but uses normal form fields (and hence
potentially a branch picker for the packaging branch) on the wiki at:

https://dev.launchpad.net/BuildBranchToArchiveUI#New%20Questions

As you'll see there, I'm not quite sure how to best include the
text-area for custom recipe text (it needs to be available there, but
it'd be nice to only display it when requested.