introduce initial, unit tested google cloud platform element set

This is the minimum needed for my codelab (compute engine is the first and only cloud product supported, and only part of GCE at that) but I think it also builds a decent starting point for cloud polymer components. I defined a naming convention for elements and files to hopefully avoid a proliferation of confusing and inconsistent names used across the many cloud products.
The extender's ready needs to call this.super()
On Jun 19, 2014 10:33 AM, "Marc Cohen" <notifications@github.com> wrote:

> In gcloud-compute.html:
>
> > +
> > +      /**
> > +       * 'scope' is the Compute Engine scope associated
> > +       * with a given resource. In practical terms, if will
> > +       * be a string taken from the following set of values:
> > +       * 'global', 'regional', 'zonal'
> > +       *
> > +       * @attribute scope
> > +       * @type string
> > +       * @default 'global'
> > +       */
> > +      scope: 'global',
> > +
> > +      ready: function() {
> > +        this.gapi = document.querySelector('gcloud-gapi');
> > +        this.config = document.querySelector('gcloud-config');
>
> If I define ready() in an extendee, will polymer auto-run both ready's in
> the correct order, or does the outer ready() need to explicitly call the
> inner ready()?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleWebComponents/google-gcloud/pull/1/files#r13981657>
> .
>