GoogleWebComponents / google-calendar

Google Calendar web components
https://elements.polymer-project.org/elements/google-calendar
Other
97 stars 38 forks source link

Paths to bower components? #8

Open dalanmiller-roche opened 10 years ago

dalanmiller-roche commented 10 years ago

Is there a main docs page that describes how to test these out? After doing bower install while in the directory I then have to change all the paths to fit where the components are and then I'm still getting errors.

Uncaught ReferenceError: Platform is not defined | polymer-expressions.js:57

ebidel commented 10 years ago

You should be able to bower install the goole-calendar element, start a web server in the directory you did that in, and got demo.html. is that what you did? On Jun 26, 2014 7:57 AM, "Daniel Alan Miller" notifications@github.com wrote:

Is there a main docs page that describes how to test these out? After doing bower install while in the directory I then have to change all the paths to fit where the components are and then I'm still getting errors.

Uncaught ReferenceError: Platform is not defined | polymer-expressions.js:57

— Reply to this email directly or view it on GitHub https://github.com/GoogleWebComponents/google-calendar/issues/8.

sjmiles commented 10 years ago

If you bower install inside of a component folder, bower will install the dependencies inside that folder, which is improper (we're working with the Bower team to fix this btw).

If that's what happened, you can end up with something like this:

<folder>\
   google-calendar\
       bower_components\
           platform\
           ....

When what you actually want is this:

<folder>\
   platform\
   ....
   google-calendar\

You can simply move the folders from google-calendar\bower_components into the outer folder to fix this.

dalanmiller-roche commented 10 years ago

Yeah I noticed this so I just changed the paths in the files themselves but still couldn't get the demo working. I'll start from scratch again today.

Daniel Alan Miller FPSMM Messaging & Real-time Collaboration Intern An Internal Perspective https://sites.google.com/a/roche.com/daniel-miller-fpsmm-intern-summer-2014/

2014-06-26 20:00 GMT+02:00 Scott J. Miles notifications@github.com:

If you bower install inside of a component folder, bower will install the dependencies inside that folder, which is improper (we're working with the Bower team to fix this btw).

If that's what happened, you can end up with something like this:

\ google-calendar\ bower_components\ platform\ .... When what you actually want is this: \ platform\ .... google-calendar\ You can simply move the folders from google-calendar\bower_components into the outer folder to fix this. — Reply to this email directly or view it on GitHub https://github.com/GoogleWebComponents/google-calendar/issues/8#issuecomment-47258170 .
devnook commented 10 years ago

If you are running demo locally, you might need to adjust the client id for accessing the calendar API: https://github.com/GoogleWebComponents/google-calendar/blob/master/demo.html#L24

(The one included in the demo has a javascript origin registered to googlewebcomponents.github.io)