Re: [aerogear-dev] bower repos for custom builds

On Jan 31, 2014, at 3:42 PM, Douglas Campos <qmx(a)qmx.me&gt; wrote: currently the builds in the AeroGear-components repo's are basically the result of running $ grunt data-manager // or pipeline, or whatever so aerogear.core.js and all related dependencies are built it. since bower is basically just a front end on top of curl this is nice if someone is just using one thing, but if they want more than 1 "component", code will start to get duplicated, although each "component" is in it's own closure(IIFE), so they shouldn't mess with each other, but still. 1 solution is to break core into it's own repo and add it to the components dependency so only one copy would exist, but the user would have to remember to include that in there script declarations and that would sort of break the IIFE that is suppose to enclose the whole thing this is where AMD might come in, not sure. i know dojo breaks there components into pieces and each one has to be included, although i haven't played with it. At this point i'm not really sure if AMDifiying the library is worth it, i need to do more research on how to break things up