Meteor - Polymer - Bower issues

[paul.dar...@gmail.com]

Hi guys,

Having a few issues that I could use some help with. I have decided to use meteor + polymer on my next app.

1. Pretty new to Meteor

2. Brand new to Polymer

Deploying Meteor as you likely know is a breeze. Polymer in my experience has been less of a breeze :)

I have tried to go through the current available examples but they're all based on Polymer 0.5.x I am hoping to use the production 1.1 release and I think that's the problem I am having.

I am trying to use Bower as it appears to be the recommended way of setting up Polymer but I'm running in to a few issues.

I have a .bowerrc file in my app folder with the following content:

{"directory":"public/components/"}

From what I understand that's the recommended way of working with meteor and polymer.

The problem arises mainly when I try to install Polymer

bower install --save Polymer/polymer  <- no problems, pulls in polymer 1.1 in to /public/components as configured.

problem starts here: bower install --save Polymer/core-elements

-- at this step it finds multiple webcomponentsjs version and makes me chose between different ones as some elements have different versions listed as dependencies

-- it also creates a second folder /public/public/components with the core-* elements in there.

try to run bower install --save Polymer/iron-elements resolves to a non existing repository.

Having had to learn so much in such a short time on both meteor and polymer I'm sure it's just jumbled in my mind. If someone could help out with a couple of clear steps on deploying a sample polymer + meteor app from scratch (with version 1 for production) that would be much appreciated!

Thanks in advance.

Paul

[Daniel Freedman]

Polymer/core-elements is all Polymer 0.5x elements

You want PolymerElements/iron-elements

Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/ad5f7363-4a38-4c9d-a011-85fa9a590562%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[paul.dar...@gmail.com]

Thanks very much Daniel,

That definitely puts me a little closer to success. Your suggestion resolved all the dependency issues that I was having now just need to figure out why meteor is rendering the template twice when I include the element.html in my head definition. As soon as I comment it out, template gets rendered as expected. I suspect it's a meteor thing so if I can't figure it out on my own will try the forums! :)

Thanks again!

[piete...@vandormael.eu]

Hi Paul,

I had exactly the same experience. Meteor is really easy and because it is so complete you do powerful stuff easily. Polymer is just the web library it is, formerly "web framework" I would say, and it doesn't cater for newbies when it comes to hosting and a clear project structure for example. If you want the powerful backend you could try Google's Firebase, but you'll have to link it all together.

From a Web-newbie's perspective I can't stop thinking that a one-stop-shop Polymer-Dart-Firebase combo would be irresistible, and I fear it's not so actively being pursued. I've gotten there myself finally though, and have been able to build some amazing things.

I've stayed clear of mixing Meteor in as it's bound to be even more experimental than mixing Polymer with Dart.

Best regards,

Op donderdag 20 augustus 2015 09:32:16 UTC+2 schreef paul.dar...@gmail.com:

[Rob Dodson]

I'll be talking about Polymer + Firebase at the Polymer Summit in September. Stay tuned!

To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/f127f453-9477-4bbd-b552-70a848a06a63%40googlegroups.com.

[paul.dar...@gmail.com]

It seems that it's all slowly coming together. In case someone else runs in to the issue I was having with the "double" render of the template, apparently it was caused by trying to import a polymer element that didn't exist, so instead of throwing an error it just showed the template again right underneath the first render :) ... once I figured that out, it seems to be working very well so I can finally start writing some useful code for my test app!

As far as web noobs... I'm not quite in that category. I am a JS only web noob. I've developed all sorts of things in the original web explosion of the LAMP stack. Lots of PHP/mysql CSS/JS type of things. Back in the day even had my own set of libraries (the type today we take for granted) that would do browser detection then create high level methods for animations, ajax calls etc, much before it was mainstream as today. Had PHP "boilderplate" system where you could define your data structure in php arrays then the scripts would create all the mysql database and all the CRUD applications would be based on that data construct definitions.

Now that I'm getting back in to web dev (10 years plus after) it's amazing to see how so many of these "ideas" of mine have come to live in so many different ways.

I am loving Meteor for the simplicity and power it offers in one place, so that's why after trying a few different things I decided to stick with that, Polymer also has a very clear and simple approach to a very complex problem, can't go wrong with tools like that.

Decided against react.js as I found I hated the idea of mixing view code in to app logic code. If performance is the only gain by doing that, I am sure Meteor will improve as it's only version 1.x at the moment.

Thanks for your comments!

paul

[paul.dar...@gmail.com]

Thanks for the heads up Rob, will definitely be waiting for that session.

You been the voice/face to my polymer introduction on youtube, excellent work.

Thanks for doing those!

Paul