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

On Thu, Aug 20, 2015 at 2:11 PM, <[email protected]> wrote:

> 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 [email protected]
> :
>
>> 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!
>>
>>
>> On Wednesday, August 19, 2015 at 3:09:12 PM UTC-7, Daniel Freedman wrote:
>>>
>>> Polymer/core-elements is all Polymer 0.5x elements
>>>
>>> You want PolymerElements/iron-elements
>>>
>>> On Wed, Aug 19, 2015 at 2:54 PM, <[email protected]> wrote:
>>>
>>>> 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
>>>>
>>>> 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 [email protected].
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/polymer-dev/ad5f7363-4a38-4c9d-a011-85fa9a590562%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/polymer-dev/ad5f7363-4a38-4c9d-a011-85fa9a590562%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/polymer-dev/f127f453-9477-4bbd-b552-70a848a06a63%40googlegroups.com
> <https://groups.google.com/d/msgid/polymer-dev/f127f453-9477-4bbd-b552-70a848a06a63%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/polymer-dev/CAJj5OwBVy0NkgGHnaUupyACx5FwmmaTMLe-d63whGp-Hr_7XPg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to