On Tue, Mar 10, 2015 at 8:19 AM, Martin Amm <[email protected]> wrote: > I personally think that removing the module registry was a step in the > wrong direction. >
The module registry wasn't 100% required for core (as evidenced by the fact that it could be removed :) ), so it's easiest to remove it for now while we still try to figure out the right solution for elements and libraries that need to reference each other. That might be just be some instructions on how to use existing module systems like AMD or SystemJS with HTML imports. We also played with a version of the old module system that was tweaked slightly to be AMD compliant (mostly a rename of modulate->define). That's nice to me because it doesn't require any source transformation. I know others might prefer Browserify, SystemJS or an ES6 transpiler which do. We will be publishing a lot more information, and maybe some more code too, but for 0.8 it was better to slim down and focus. Cheers, Justin > I think that having to hard code file names for dependencies is currently > the weakest point in the Polymer architecture. > > I'd prefer to replace the current import like > <link rel="import" href="*../core-icons/core-icons.html* > <http://127.0.0.1:62447/components/core-icons/core-icons.html>"> > > with > <link rel="import" name="*core-icons* > <http://127.0.0.1:62447/components/core-icons/core-icons.html>"> > > and then being able to define in globally which url provides > core-icons.html. > This would indeed be great, but the module registry couldn't provide this behavior because it can't hook the resolution of import URLs. The solution here probably involves a spec for import hooks that's ideally just the same as the one for ES6 modules. > > This would allow to e.g. replace core-icons/core-icons.html with > my-icons/core-icons.html > > It would also allow to control client side caching by e.g. starting > with /version1/core-icons.html and replace it later with a > newer /version2/core-icons.html without having to modify all imports. > > > > 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/6084ebf7-ef28-403e-9e9d-28f12fc7891a%40googlegroups.com > <https://groups.google.com/d/msgid/polymer-dev/6084ebf7-ef28-403e-9e9d-28f12fc7891a%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/CAEKsHmBO5CBWMF%2BONWh4YWn%3DkPKX0JwdNiq42K0Kc%3DGYwXOB2Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
