<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 11 November 2014 20:10, Anton Zemlyanov <span dir="ltr"><<a href="mailto:azemlyanov@mirantis.com" target="_blank">azemlyanov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Modernizing Horizon using Angular is really great. I would suggest a couple of minor things to consider. <div><br></div><div>First, font-awesome is excellent and free font, but there are two problems: it has lots of icons that are not used, it also miss some other icons worth to have. I would suggest Fontello, it is tool for picking glyphs from all the free fonts round there and building custom fonts</div></div></blockquote><div><br></div><div>Thanks for bringing this up. We discussed the need for additional symbols at the meetup, and it may very well be that we do come up with a custom font with a selection from font-awesome plus additional symbols designed as we go along. Very good idea.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Grunt is being forced out by Gulp that is times faster while having the same level of plugins and tools and is easier to use<br></div></div></blockquote><div><br></div><div>Thanks for the pointer. I mentioned grunt in particular because it's quite mature at this point, was the default tool for the yoeman project builder I used and is also the tool of choice for Storyboard. If there is a compelling reason to switch though, I imagine the Storyboard folk may also be interested. From a brief look around there does seem to be a lot of enthusiasm for gulp. I will look at making a branch of angboard that uses gulp to get a good feeling for it (unless someone produces a PR that does it for me ;)</div><div><br></div><div><br></div><div> Richard</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div class="h5">On Tue, Nov 11, 2014 at 11:02 AM, Richard Jones <span dir="ltr"><<a href="mailto:r1chardj0n3s@gmail.com" target="_blank">r1chardj0n3s@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hi all,<div><br></div><div>At the summit last week, we developed a plan for moving forward with modernising Horizon's UI using AngularJS. If you weren't at that meeting and are interested in helping out with this effort please let me know!</div><div><br></div><div>The relevant etherpad from the meeting:</div><div><a href="https://etherpad.openstack.org/p/kilo-horizon-contributors-meetup" target="_blank">https://etherpad.openstack.org/p/kilo-horizon-contributors-meetup</a><br></div><div><br></div><div>TL;DR: piece by piece we will replace Django views in Horizon with angular views, and we're going to start with Identity</div><div><br></div><div>First up, I'd like to ask the UX folk who raised their hands in that meeting to indicate which of the Identity panes we should start with. I believe a wizard was mentioned, as a way to exercise the new wizard code from Maxime.</div><div><br></div><div>At the same time, I'm looking at updating the AngularJS recommendations in the wiki. I believe other aspects of the current approach to angular code should also be revisited, if we're to scale up to the full angular front-end envisaged. I'd appreciate if those interested in this aspect in particular could contact me so we can sort this out as a team!</div><div><br></div><div>I'd like to start the design work for the new REST API layer we'll be exposing to the angular application code, but that is also part of the broader discussion about the structure of the angular code in the Horizon application as mentioned above. Should it be a new blueprint/spec?</div><div><br></div><div>There were some discussions around tooling. We're using xstatic to manage 3rd party components, but there's a lot missing from that environment. I hesitate to add supporting xstatic components on to the already large pile of work we have to do, so would recommend we switch to managing those components with bower instead. For reference the list of 3rd party components I used in angboard* (which is really only a teensy fraction of the total application we'd end up with, so this components list is probably reduced):</div><div><br></div><div><div> json3</div><div> es5-shim</div><div> angular</div><div> angular-route</div><div> angular-cookies</div><div> angular-animate</div><div> angular-sanitize</div><div> angular-smart-table<br></div><div> angular-local-storage</div><div> angular-bootstrap</div><div> angular-translate</div><div> font-awesome</div><div> boot</div><div> underscore</div><div> ng-websocket</div><div><br></div></div><div>Just looking at PyPI, it looks like only a few of those are in xstatic, and those are out of date.</div><div><br></div><div>grunt provides a lot of features for developing an angular interface. In particular LiveReload accelerates development significantly. There's a django-livereload but it uses tiny-lr under the hood, so we're still using a node application for LiveReload support... so it might make sense to just use grunt. grunt provides many other features as well (wiredep integration with bower, build facilities with ngMin, test monitoring and reload etc).</div><div><br></div><div>There seemed to be agreement to move to jasmine (from qunit) for writing the tests. It's not noted in the etherpad, but I recall karma was accepted as a given for the test runner. For those not in the meeting, angboard uses mocha+chai for test writing, but I agreed that jasmine is acceptable, and is already used by Storyboard (see below).</div><div><br></div><div>Also, phantomjs so we don't have to fire up a browser for exercising (what should hopefully be an extensive) unit test suite.</div><div><br></div><div>The Storyboard project has successfully integrated these tools into the OpenStack CI environment.</div><div><br></div><div><br></div><div> Richard</div><div><br></div><div>* <a href="https://github.com/r1chardj0n3s/angboard" target="_blank">https://github.com/r1chardj0n3s/angboard</a><br></div></div>
<br></div></div>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div></div></div>