launchpad-dev team mailing list archive

[Deryck Hodge <deryck.hodge@xxxxxxxxxxxxx>]

On Mon, Feb 20, 2012 at 10:55 PM, Robert Collins
<robertc@xxxxxxxxxxxxxxxxx> wrote:
> So, going back at least 18 months, maybe more, there has been a long
> slow-running conversation amongst us about what we render were, with
> different projects choosing different answers.
>
> I think we have enough data now, that we can consolidate on a good
> default answer and ask that everyone pick that answers *by default*
> with variation needing to be experiments - explicit decisions to learn
> something new.
>
> tl;dr: lets:
>  * render searchable content on server side and client side using a
> common template language
>  * render the forms needed to file a bug server side and optionally client side
>  * render all other forms exclusively client side and have them
> communicate exclusively via the API
>

Sorry I'm so slow in jumping in on this, Robert. But I wanted to give
a +1 to the plan. It's well argued and well thought out, and I have no
issues following this.

For those who haven't looked at the way we did server vs. client
rendering in the new bug listings work, I think that work is a decent
example of how we could proceed with this, where we need initial
server rendering. Essentially, we share a common template and
re-render on the client when the view needs to change. I also think we
should be driving toward adoption of YUI's App framework, which hooks
model and view objects together around YUI's event system in a way
that makes it easier to re-render on the client. This plan would tie
in well with that goal, too, which I'm sure you were conscious of,
given all the recent discussions.

Anyway, unreserved +1 from me.

Cheers,
deryck

-- 
Deryck Hodge
https://launchpad.net/~deryck
http://www.devurandom.org/