Open kristianmandrup opened 9 years ago
Because of the way HTML imports dedups imports, you pretty much need a flat dependency tree. So the standard way to do this is to set the bower directory to "../", so dependencies are installed in sibling directories.
Here's the outline:
.bowerrc
in the paper-tabs
directory like this:{
"directory": "../"
}
Now you can run bower install and everything should just work. (I think the .bowerrc isn't there by default because of the risk of people polluting their directories if they run this in the wrong place.)
+1 on adding a contributing doc. Existing notes on contributing are outdated. Let me see if there's a bug for that.
These paper elements aren't really "self-contained". I can't simply clone the repo,
bower install
, open the demo and work from there... Looks like the repo has to exists within a specific app structure...From
demo.html
Running
bower install
will install all components intobower components
folder. What is the recommended structure for this to work? Why not add a dev folder which sets up the infrastructure to reference the outerpaper-tabs
files but can run stand-alone? or some other way?Also, please add some documentation for getting started (ie. contribution guide lines) and more on how scrolling behaviour is intended to work. Thanks :)