mordred at inaugust.com
Mon Jan 13 01:21:06 UTC 2014
On 01/11/2014 09:56 AM, Sean Dague wrote:
> As someone that's done a decent amount of hacking on
> status.html/status.js, I think we're getting to a level of complexity on
> our JS status pages that we should probably stop doing this all inline
> (probably should have stopped a while ago).
> and start incrementally porting bits over there over time.
Yes. I believe we're at that point. I've also been learning about js dev
and build toolchains, such as grunt, and I've been thinking that
status.js might want to be in its own repo.
> My current thought is - http://handlebarsjs.com/ - mostly because it's
> only a template library, won't cause us to do a complete rewrite, and we
> can move it in in parts. Other opinions are welcome.
storyboard and horizon are both doing things with angular.
> But if we get an ACK on some approach, we can then start phasing it in,
> vs. the current state of the art which is way too much string append.
Michael - any thoughts?
More information about the OpenStack-dev