On 01/13/2014 04:28 PM, Michael Krotscheck wrote:
> On 01/13/2014 01:12 PM, Sean Dague wrote:
>>
>> Well, as an expert in the area, particular recommendations would be
>> appreciated. I don't feel like we necessarily need one answer, but it
>> would be nice knock some of the options off the table.
@Michael, very nice conclusion, absolutely agree.
On Tue, Jan 14, 2014 at 1:28 AM, Michael Krotscheck wrote:
> On 01/13/2014 01:12 PM, Sean Dague wrote:
>
>>
>> Well, as an expert in the area, particular recommendations would be
>> appreciated. I don't feel like we necessarily need one answer, b
On 01/13/2014 01:12 PM, Sean Dague wrote:
Well, as an expert in the area, particular recommendations would be
appreciated. I don't feel like we necessarily need one answer, but it
would be nice knock some of the options off the table.
I'd say: Start with handlebars, unless you want to lay appl
On 01/13/2014 03:06 PM, Michael Krotscheck wrote:
> On 01/13/2014 05:05 AM, Sean Dague wrote:
>> 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
On 01/13/2014 05:05 AM, Sean Dague wrote:
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.
Yes indeed.
I guess the real question I
On 01/12/2014 09:56 PM, Michael Krotscheck wrote:
> If all you're looking for is a javascript-based in-browser templating
> system, then handlebars is a fine choice. I'm not certain on how complex
> status.html/status.js is, however if you expect it to grow to something
> more like an application t
Currently, we already have a simple status page in zuul repo and status
page in infra/config, probably, we should think about moving them to the
separated repo and merge their functionality and in this case it'll be easy
to use any actual js tools. Otherwise it'll be not really straightforward
to h
Just to make a context for this discussion, here are the two files that
where're speaking about:
https://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/files/zuul/status.html
https://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/files/zu
On 01/13/2014 05:05 AM, Sean Dague wrote:
On 01/12/2014 09:56 PM, Michael Krotscheck wrote:
If all you're looking for is a javascript-based in-browser templating
system, then handlebars is a fine choice. I'm not certain on how complex
status.html/status.js is, however if you expect it to grow to
If you're just using it for client-side templates, you should be able to treat
it like any other js library (jquery, etc) without using npm (node's package
manager) for installation. Handlebars, for example, has a single downloadable
js file that is available on their website:
http://builds.ha
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.
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 mor
On 01/12/2014 09:56 PM, Michael Krotscheck wrote:
If all you're looking for is a javascript-based in-browser templating
system, then handlebars is a fine choice. I'm not certain on how complex
status.html/status.js is, however if you expect it to grow to something
more like an application then pe
If all you're looking for is a javascript-based in-browser templating
system, then handlebars is a fine choice. I'm not certain on how complex
status.html/status.js is, however if you expect it to grow to something
more like an application then perhaps looking at angular as a full
application frame
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).
I'd like to p
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).
I'd like to propose that we pick some javascript temp
15 matches
Mail list logo
