maas-devel team mailing list archive

[Christian Robottom Reis <kiko@xxxxxxxxxxxxx>]

Hello there,

    Raphael, Blake, Gavin and I had a discussion today about our UI and
API plumbing to see what we currently have and what will change for 1.8
and beyond. I've summarized this below:

    1.7
        - Uses YUI3 for:
            * Homepage node graph
                (also uses libjs-raphael)
            * Node edit (power control widget swapping)
            * Node listing live updating
            * Images live reloading
            * Logged-in user drop-down
        - Uses JQuery (bundled with Django) for:
            * Network edit page MAC filtering
        - (We dropped txlongpoll for 1.7.0 so one less dependency -- yay)

    1.8
        - We are introducing AngularJS, initially for
            * Node listing
            * Node details
        - Angular itself uses JQuery, and currently we are using the
          in-archive version; we should be able to use that rather than
          the version bundled with Django for the existing callsite
        - We will drop the homepage graph in favor of a new design
        - We may also be able to remove the other callsites that depend
          on YUI3, depending on time and complexity

    Next
        - As we prepare for a new version of the API (2.0), we should
          consider replacing piston with tastypie (or something like
          it), which would allow us to remove the serialization code
          added for AngularJS

If I've missed anything or if there's something we should change, let me
know. Thanks!

PS: I had meant to note that we could use requires.io to track how
up-to-date our dependencies are. Has anyone considered that?
-- 
Christian Robottom Reis   | [+1] 612 888 4935    | http://launchpad.net/~kiko
Canonical VP Hyperscale   | [+55 16] 9 9112 6430