Concept - Rendering Context

Added by Philipp Bärfuss, last edited by Grégory Joseph on May 04, 2012  (view change) show comment
Labels:
Your Rating: Results: PatheticBadOKGoodOutstanding! 0 rates
Draft for ?

Draft for ? - Discussion points about rendering context.

Rationale:

  • today renderers can't stream binaries (images, pdf, ..): MAGNOLIA-3014@jira
  • the links are not always rendered the same way
    • mails: use full links including the domain
    • integration into other sites: portlets, ajax, ...

Goal

  • uncouple the rendering and request processing
  • possibility to streaming binaries (jsp)

Implementation

  • interface
    • getLinkTransformer()
    • getWriter()
    • getOutputStream()

Outlook

  • parameters/attributes?
  • redirect()/redirect()
  • setExceptionHandler()
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (2)

 

  1. Mar 12, 2010

    Grégory Joseph says:

    Attributes would be one way to let components "talk" to each other; see for an e...

    Attributes would be one way to let components "talk" to each other; see for an example info.magnolia.module.templatingcomponents.components.SingletonParagraphBar#isInSingleton

    This would also need to hold current node+renderable(+model?); this pair (or trio) could maybe be kept in a stack of sorts.

  2. Apr 27, 2010

    Jan-David Salchow says:

    Wouldn't it be way better to use some kind of dependency injection instead of pu...

    Wouldn't it be way better to use some kind of dependency injection instead of putting everything into a context and collecting dependencies whenever needed? Maybe a JSR-330 compatible version of autowireing would be possible?