Loading...

XML

Word

Printable

Type: Improvement
Resolution: Fixed
Priority: Major
Fix Version/s: 4.0
Affects Version/s: None
Component/s: templating
Labels:
None

Template:
Acceptance criteria:

Empty

show more show less

There is certainly room for improvement and removal of duplicate stuff. TemplateRenderer and ParagraphRenderer could be one single thing. Maybe Pages too.
Maybe Paragraph, Template and Pages would implement a common "Renderable" interface, for instance.
As Philipp mentionned, pages already have support for:

multiple actions
usage of commands
setting request parameters
simple template selection based on resolved view name

Acceptance criteria

depends upon

MAGNOLIA-1462 Create a freemarker-based paragraph renderer

Closed

is depended upon by

MAGNOLIA-2545 Cleanup soft-dependency between gui components, templating and taglibs

Closed

is related to

MAGNOLIA-2381 provide an action for templates and paragraphs like in the freemarker paragraphs

Closed

MAGNOLIA-2642 aggregation state: use current content property consistently

Closed

MAGNOLIA-1455 Remove usage of HttpServletRequest and -Reponse in TemplateRenderer

Closed

MAGNOLIA-2369 Templates should be instanciated with content2bean

Closed

MAGNOLIA-2370 Move Template/Paragraph related code to templating module

Closed

(2 is related to)

Assignee:: Magnolia International

Reporter:: Magnolia International

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Created:: 23/Apr/07 3:06 PM

Updated:: 23/Jan/13 9:09 AM

Resolved:: 26/Jan/09 5:13 PM

Date of First Response:: 04/Oct/08 9:48 PM

Details

Description

Checklists

Attachments

Issue Links

Activity

People

Dates