Feature #38629

Make TypoScript usable outside the context of TYPO3 / Nodes, but also for building extensible FLOW3 applications

Added by Sebastian Kurfuerst about 3 years ago. Updated almost 3 years ago.

Status:Resolved Start date:2012-07-04
Priority:Should have Due date:
Assigned To:Sebastian Kurfuerst % Done:

86%
Category:-
Target version:-

Description

For the management view in the Phoenix backend, we want to use TypoScript for the generic and extensible rendering mechanism.

Thus, we want to investigate the changes to be done in TypoScript to make it usable in the context of generic objects. We planned the new TypoScript in a way that this is possible; though we still have to connect some loose ends for good usability.

See the subtasks for some detailed TODOs.

Subtasks

Feature #38630: Implement TypoScriptView which can be used as replacement...ResolvedSebastian Kurfuerst

Bug #38631: Make use of FlowQuery explicit by introducing a wrapper f...Resolved

Feature #38633: Make TypoScript Context multi-valuedResolved

Task #38634: Move TypoScript Processors from TYPO3 to TypoScript PackageClosedRobert Lemke

Feature #38636: Implement get() function to retrieve arbitrary objects vi...Rejected

Feature #38638: Introduce PresentationModel Wrapper in eel expressions in...On HoldSebastian Kurfuerst

Bug #38692: FluidTemplate: Make Layout and PartialPath settableResolved

History

#1 Updated by Sebastian Kurfuerst about 3 years ago

  • Status changed from New to Accepted
  • Assigned To set to Sebastian Kurfuerst

#2 Updated by Sebastian Kurfuerst almost 3 years ago

  • Status changed from Accepted to Under Review

#3 Updated by Sebastian Kurfuerst almost 3 years ago

  • Status changed from Under Review to Resolved

Also available in: Atom PDF