<div dir="ltr">Personally, I think that it's a great step now to move this code to the templates. As for the huge frameworks - I prefer something like Angular.JS or Knockout.JS.<div><br></div><div>Currently, the status.js file isn't so bug to rewrite it as a real life web app and so, we could just add templates to make it much more readable and improvable.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 13, 2014 at 5:05 PM, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 01/12/2014 09:56 PM, Michael Krotscheck wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If all you're looking for is a javascript-based in-browser templating<br>
system, then handlebars is a fine choice. I'm not certain on how complex<br>
status.html/status.js is, however if you expect it to grow to something<br>
more like an application then perhaps looking at angular as a full<br>
application framework might help you avoid both this growing pain and<br>
future ones (alternatives: Ember, backbone, etc).<br>
</blockquote>
<br></div>
Honestly, I've not done enough large scale js projects to know whether we'd consider status.js to be big or not. I just know it's definitely getting too big for += all the html together and doing document.writes.<br>
<br>
I guess the real question I had is is there an incremental path towards any of the other frameworks? I can see how to incrementally bring in templates, but again my personal lack of experience on these others means I don't know.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Quick warning though, a lot of the javascript community out there uses<br>
tooling that is built on top of Node.js, for which current official<br>
packages for Centos/Ubuntu don't exist, and therefore infra won't<br>
support it for openstack. Storyboard is able to get around this because<br>
it's not actually part of openstack proper, but you might be forced to<br>
manage your code manually. That's not a deal breaker in my opinion -<br>
it's just more tedious (though I think it might be less tedious than<br>
what you're doing right now).<br>
</blockquote>
<br></div>
I'd ideally like to be able to function without node, mostly because it's another development environment to have to manager. But I realize that's pushing against the current at this point. So I agree, not a deal breaker.<div class="im HOEnZb">
<br>
<br>
-Sean<br>
<br>
-- <br>
Sean Dague<br>
Samsung Research America<br>
<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a> / <a href="mailto:sean.dague@samsung.com" target="_blank">sean.dague@samsung.com</a><br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br></div><div class="HOEnZb"><div class="h5">
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>Sincerely yours,</div><div>Sergey Lukjanov</div><div>Savanna Technical Lead</div><div>Mirantis Inc.</div></div>
</div>