[Commits] svn commit: 8193

Subversion Database Process svn at thor.atrc.utoronto.ca
Thu Oct 1 17:43:21 UTC 2009


------------------------------------------------------------------------
r8193 | antranig at caret.cam.ac.uk | 2009-10-01 13:43:21 -0400 (Thu, 01 Oct 2009) | 1 line
Changed paths:
   M /fluid/infusion/trunk/src/webapp/framework/renderer/js/fluidParser.js
   M /fluid/infusion/trunk/src/webapp/framework/renderer/js/fluidRenderer.js
   M /fluid/infusion/trunk/src/webapp/tests/framework-tests/renderer/html/Renderer-test.html
   M /fluid/infusion/trunk/src/webapp/tests/framework-tests/renderer/js/RendererTests.js

FLUID-2980, FLUID-2962: Fixes and test case for multiple decorator issue. This was actually caused by failure of re-entrancy in the renderer, which was being invoked recursively in the case where the fluid decorator designated a component which itself invoked the renderer. Establishing reentrancy for the renderer actually puts this work also under the heading of FLUID-2962 which required to enable the renderer for multi-threaded access for use on the server-side, which work had been incomplete but seen as lower priority for this release until now. This reorganisation creates a new top-level API fluid.renderer which follows the "that-ist" convention that is now standard for the framework, but which had not been in place when the renderer was initially designed. The original low-level API fluid.renderTemplates is preserved for backwards compatibility, but should be deprecated in a future release - in this implementation, it forwards to an invocation of the that-ist API which c!
 an be "stealthed" for this release but which should be advertised in future ones. The fluid.renderTemplates API does not provide any mechanism for decorators to be honoured - but it never did in any case, so this behaviour remains consistent. More thought and design is needed over future releases to create a family of strategies for honouring decorators, which will become very important as they begin to be used more cooperatively between client and server with the implementation of Kettle.
------------------------------------------------------------------------



More information about the Commits mailing list