{"shas":[["dbf01c09c2162002aacd689525098614f909e48a","ee76976466d2b81240838f3bccb1d70f34ac9b44@colorado.edu","FLUID-3905: Delinted IoC once more, and stray comma found in fileQueueView which prevented loading on IE","Antranig Basman"],["020d4dc9d019e6517a7057ab520f6d79e3e41251","ee76976466d2b81240838f3bccb1d70f34ac9b44@colorado.edu","FLUID-4159: Working ability to instantiate Uploader as part of IoC tree, demo updated to show both modes (since we currently do not have any automated test case which instantiates an entire uploader). Removal of unadvertised \"parent\" facility for demands blocks (together with test case), since this case is now handled more coherently by \"mergePaths\" feature for component options. Restoration of \"demands redirects\" which now will follow 1 redirect from a demands block based on \"funcName\". Sensible results are only guaranteed if the first demands block contains ONLY funcName, this needs to be enforced. Demands blocks rewritten in uploader to allow \"fluid.uploaderImpl\" to be directly instantiated - together with \"redirect\" demands block to enable \"fluid.uploader\" to be used for this purpose. Rewriting of progressiveEnhancement to support the case where more than one type of component might be progressively enhanced in the same tree. Restoration of test cases for progressiveEnhancement. A serious conceptual flaw still exists with progressiveEnhancement - if more than one pE block for the same component is in scope, with differing directives, the result will be an \"ambiguous match\" rather than selecting the version which is closest in scope. This may require fundamental changes to demands resolution to resolve.","Antranig Basman"],["a786383ef6daa0de8b9331cd4f3a84327652d093","ee76976466d2b81240838f3bccb1d70f34ac9b44@colorado.edu","FLUID-4160, FLUID-3780: Improved documentation of intent on some dubious utilities in FluidDOMUtilities.js and DataBinding.js after review by FISH. Corrected comment for expectFilledSelector() function, some linting","Antranig Basman"],["5e3f25183e02e782fd65a697f8f2c06587a3cd9c","1b34bffe6b8dd6c929a854cf46c70e06803ab6b4@gmail.com","FLUID-4161: Updated url to License file\n\nUpdated the url to the license file in the copyright comments. This had still been pointing to SVN. I've updated it to now point at the raw copy of the license file housed in our github repo.","Justin Obara"],["91fff12024acc07c94cf426498e287724d7becd6","ee76976466d2b81240838f3bccb1d70f34ac9b44@colorado.edu","FLUID-4130: Renamed \"mergePaths\" directive in options to \"mergeOptions\" and \"mergeAllOptions\". Both of these directives are now supported as direct members of a demands block, rather than requiring intervening \"options\" structure. Both are also supported still as member of component's options. Adjusted Uploader to account for changes in names. Rationalised uploader demands blocks somewhat, removed redundant directives and correctly wired \"onFileDialog\" event","Antranig Basman"],["1b8c5e09d2147b0bf1d75fa13c15b5b43bb64981","ee76976466d2b81240838f3bccb1d70f34ac9b44@colorado.edu","FLUID-4162: Support for out-of-order construction of autoInit creator function and namespace with the same name","Antranig Basman"],["9ab11c05ad2813f8baefff6abcd2c27b41e4ed92","ee76976466d2b81240838f3bccb1d70f34ac9b44@colorado.edu","FLUID-4159, FLUID-4151: Allow demands blocks to be issued against the Uploader within an IoC tree. New IoC directive \"fluid.alias\" allows to express the intent that demands blocks should be \"forwarded\" from an outer function (e.g. fluid.uploader) to an inner one (e.g. fluid.uploader.multiFileUploader). Currently the only case we support is where demands blocks for the inner function ONLY specify \"funcName\" - other cases will fail. New powerful improvement in IoC diagnostics - file and line number tracking for fluid.demands! Include file \"FluidDebugging.js\" to get access to this facility on Firefox. We'll add other browsers as we understand them better (prototype code is available at emwendelin/javascript-stacktrace). Reordered demands blocks for FileQueueView so that they are properly scoped within files, and take advantage of new facility just provided for FLUID-4162 to allow nice namespacing of init functions. MAJOR change to resolution order of demands blocks - blocks with mismatches are now penalised above all. This makes it possible to write a \"catch-all\" demands block for fileQueueView.eventBinder which beats any mismatched blocks (previously the positive match on fileQueueView would beat the null match). Test cases required for fine details of demands resolution. Perhaps mismatched blocks should be discarded entirely.","Antranig Basman"],["eb3216c43cabe1b4fad29ce84a6b9b6ea2c02e16","15b407793e00661b0f6435a4e2ff8cc57b1b934c@gmail.com","Merge branch 'master' into FLUID-4140","Michelle D'Souza"]],"repo":"colinbdclark/infusion","actor":"michelled","ref":"refs/heads/FLUID-4140","size":8,"head":"eb3216c43cabe1b4fad29ce84a6b9b6ea2c02e16","actor_gravatar":"79fd3dab7ec8674c7185a1453fd5330e","push_id":27798793}