[TYPO3-mvc] About limitations in Fluid

[Lienhart Woitok]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi list,

we used to create templates for processing through LaTeX with markers and subparts. This worked very well with the default mechanisms of TYPO3 (substitueMarkerArray, substitueSubpart, ...). Now, since we have Extbase and Fluid, of course the need occurred to build LaTeX templates with Fluid. I tried this yesterday in the naïve hope that this could just work. Well, it can't. LaTeX needs many, many curly brackets to enclose arguments to commands. But Fluid does not leave many curly brackets in the document as it treats them as object accessors. I played around with Fluid, but to no avail.

I now see several possibilities to get this working:
* Somehow escape the curly brackets in the template. This has several drawbacks: First, the template cannot be processed with the LaTeX compiler or an editor with syntax completion. Second, the readability of the template is reduced (ok, one can argue the readability of LaTeX code, but that's not the point here). Example \section\{foobar\}
* Replace the brackets with a view helper like it is done in the kickstarter for html template templates. The previous drawbacks also apply here. Example: \section{pdf:curlyBracket(value: 'foobar')}
* Use a different way of defining object accessors in Fluid. If one can configure the enclosing characters, a LaTeX template could access objects with something like \fvalue{some.crazy.object.assigned.to.the.view}. Then, curly brackets could be normally used in the LaTeX code. Example: \section{foobar}
* Some proposal of you

I actually prefer the third mentioned way, as it would allow adaption of Fluid syntax to the format at hand.

By the way, some means to post process generated output would be really cool, for example to run the LaTeX compiler on the generated output. I haven't found a way to do this now other than subclassing the TemplateView. Such a post processor could also be used to automatically determine that for the requested format "pdf", templates of the format "tex" can be transformed to PDF by the post processor. Fluid could then use this transformation/post processing to generate the requested format without further hassle. Another use case for such magic could be to render graphs with gnuplot, graphviz or similar or to render svg as png.

I'm curious what you think about this.

Kind regards,

Lienhart Woitok
Web-Entwickler

Telefon: +49 (911) 539909 - 0
E-Mail: Lienhart.Woitok at netlogix.de


- --
netlogix GmbH & Co. KG
Systemhaus | Trainingscenter | Medienagentur
Andernacher Straße 53 | 90411 Nürnberg
Telefon: +49 (911) 539909 - 0 | Fax: +49 (911) 539909 - 99
E-Mail: mailto:info at netlogix.de | Internet: http://www.netlogix.de/

netlogix GmbH & Co. KG ist eingetragen am Amtsgericht Nürnberg (HRA 13338)
Persönlich haftende Gesellschafterin: netlogix Verwaltungs GmbH (HRB 20634)
Umsatzsteuer-Identifikationsnummer: DE 233472254
Geschäftsführer: Stefan Buchta, Matthias Schmidt




-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 3.0.0 (Build 2881)
Charset: Windows-1252

wpUDBQFL2ZMXWevMF2ftbKMBCGFkA/9TfxSHllIb8TdqB/lch8ICEKndi+h/8rie
P66ILp94BaB4GsgzRZlRlcRmM97A8cnt+AiAVGJC6jWNhMX4dj8xMSL9WhW6etCZ
jJvig9SLfBw6i+oFyVAYImIgV/w3rLOvONOzcO/1zzAvLo7Zafu7KWdZbBGVxEOs
WZ0AWCVqLg==
=2Pmb
-----END PGP SIGNATURE-----