On Tue, Mar 2, 2010 at 1:52 PM, James Westby <[email protected]> wrote: > On Tue, 2 Mar 2010 13:16:11 +0000, Jonathan Lange <[email protected]> wrote: >> A derived recipe isn't designed for readability. To understand what it >> means, you need to be able to look at the parent recipes. The >> difference between "insert-after" and "insert-nest" causes me to pause >> and think when I read them. All of these combined make me think that >> derived recipes can confuse newbies. >> >> I think it's pretty much inherent to derivation though. > > Agreed. I plan to have a way to see the complete recipe, and you may > want to implement that in the web ui too. > > Do you think that the difference in the insert-* methods are > warranted? Just having insert-after means you can't do one thing (modify > a nested branch that is currently unmodified in the parent), so I put it > there for completeness. >
I think it's warranted. >> >> What's the next step? >> > >> > I need to know that the proposals here allow for the desired UI to be >> > implemented, and we need a decision on the two options in the >> > multi-series proposal. >> > Tim's made one already. :) ... > > Do we want input from the design team/Mark on the mockups/changes at > some stage? > We need approval from Mark on the derivation stuff, I think. Aaron & Paul are already beginning work without the UX team's input, and I think that's the right thing to do. jml _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
