Max - thanks for pointing out the error in the path in the dialog - consider that added to the queue for fixing once people are back from the holidays next week.
Overall, it's important to realize that when web components are in wide usage, there will be tens of thousands of elements from many different vendors. One download for all of this is impractical. Even today, as Niels points out, this is impractical. We are building for that future, not today with a relatively small number of components. The purpose of the zip files is to provide a preview for a given component, not all components, not all of Polymer. The zip files contain the dependencies for just that one component. The minute one wants to actually use more than one component, managing overlapping dependencies becomes essentially impossible. This is when a package manager like Bower is needed, and recommended by the Polymer team. These are not equivalent use cases, and making them look like each other, modulo the path bug Max pointed out, is probably going to lead to bigger problems down the line. The zip files are for kicking the tires. If you want to get in the car and go somewhere, use Bower. Ultimately, tools will spring up to make managing all of these individual components from different vendors easier, and possible without the command line for users that prefer that. Alternatively, smarter CDN-like things will allow for simply linking to a common URL. We're simply just not there yet and those tools do not yet exist. -Matt On Thu, Jan 1, 2015 at 6:25 PM, Max <[email protected]> wrote: > I just tried downloading the zip file and unzipping it. I see a few > issues. Here are my steps : > > 1. from < > https://www.polymer-project.org/docs/start/getting-the-code.html#using-zip> > click 'GET POLYMER' > dialogue appears with 'DOWNLOAD ZIP' and example import : > '<link rel="import" href="components/polymer/polymer.html">' > 2. click 'DOWNLOAD ZIP' > 3. cd ~/Downloads/; mkdir tmp; cd tmp; unzip ../archive.zip > > the structure of the download doesn't correspond fo the import link in the > dialogue above : > > [tmp]$ find . -name polymer.html > ./components/bower_components/polymer/polymer.html > ./components/bower_components/polymer/dist/polymer.html > > It does seem to include polymer.html and webcomponents.js, and I presume > all their dependencies. > It doesn't include any core or paper elements, but I wouldn't expect that > since they're not 'polymer' (just elements written using polymer). > > Still, it's clear the instructions aren't correct. Either the archiver > should produce a zip file with bower_components renamed to components, or > the import link in the dialogue should be changed to be '<link rel="import" > href="components/bower_components/polymer/polymer.html">'. > > Personally, I think there's an unnecessary directory level there - and to > make it consistent with using the command line (with default rc), the > dialog should be changed to use 'bower_components/' *and* the top > 'components/' directory level removed. > > Max. > > On Fri Jan 02 2015 at 10:08:47 Максим Иванов <[email protected]> wrote: > >> Guys I've been programming for 15 years. I know what the console. If the >> Console is the only possible solution for installing and automation >> updates do not need to be misleading phrase: "*The ZIP file contains all >> dependencies for this component and is a great way to get started.*" Now >> that I've spent a lot of time that would look into this lie. Zip file >> that does not contain all. I can get to work with the polymer. And I >> want to draw the attention of developers that this is not the precision >> makes entry into the polymer is much more difficult than many people >> think. I think that this will affect the success of the project. So >> either make a correct description, or make zip archive that contains all >> really. >> >> PS; sorry for my bad english >> >> 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/8819c0ab-4ba4-49cf-a578-32079ccb8b83%40googlegroups.com >> <https://groups.google.com/d/msgid/polymer-dev/8819c0ab-4ba4-49cf-a578-32079ccb8b83%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/CAMZCrPiYCGR8gXbauCkYWB2eHZJRTtG%3Drh5MGZQJ%2BD%2B5gNeGUQ%40mail.gmail.com > <https://groups.google.com/d/msgid/polymer-dev/CAMZCrPiYCGR8gXbauCkYWB2eHZJRTtG%3Drh5MGZQJ%2BD%2B5gNeGUQ%40mail.gmail.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/CAKrkLHor9pcGWoBHe8JHM%2B-CLhJmSZt1A40WKUQE%3DKUa%2BGtJnw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
