[Commits] [fluid-project/infusion] 020d4d: FLUID-4159: Working ability to instantiate Uploade...

noreply at github.com noreply at github.com
Thu Mar 24 08:37:17 UTC 2011


Branch: refs/heads/master
Home:   https://github.com/fluid-project/infusion

Commit: 020d4dc9d019e6517a7057ab520f6d79e3e41251
    https://github.com/fluid-project/infusion/commit/020d4dc9d019e6517a7057ab520f6d79e3e41251
Author: Antranig Basman <antranig.basman at colorado.edu>
Date:   2011-03-24 (Thu, 24 Mar 2011)

Changed paths:
  M src/webapp/components/uploader/js/Flash9UploaderSupport.js
  M src/webapp/components/uploader/js/FlashUploaderSupport.js
  M src/webapp/components/uploader/js/HTML5UploaderSupport.js
  M src/webapp/components/uploader/js/Uploader.js
  M src/webapp/demos/uploader/html/uploader.html
  M src/webapp/demos/uploader/js/uploader.js
  M src/webapp/framework/core/js/FluidIoC.js
  M src/webapp/framework/enhancement/js/ProgressiveEnhancement.js
  M src/webapp/tests/framework-tests/core/js/FluidIoCTests.js
  M src/webapp/tests/framework-tests/enhancement/js/ProgressiveEnhancementTests.js

Log Message:
-----------
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 progressiveEnhan
 cement. 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.





More information about the Commits mailing list