[TYPO3-mvc] RFC: New comments in FLUID

Stephan Schuler Stephan.Schuler at netlogix.de
Thu Mar 1 12:01:46 CET 2012


Ah, then just don't change anything please. I didn't know about the comment view helper so I just +1-ed Christian Müllers first post.
Then ignore my suggestion of introducing it again but keep my opinion against any changes in this field :)



Stephan Schuler
Web-Entwickler

Telefon: +49 (911) 539909 - 0
E-Mail: Stephan.Schuler at netlogix.de
Website: media.netlogix.de


--
netlogix GmbH & Co. KG
IT-Services | IT-Training | Media
Andernacher Straße 53 | 90411 Nürnberg
Telefon: +49 (911) 539909 - 0 | Fax: +49 (911) 539909 - 99
E-Mail: 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



-----Ursprüngliche Nachricht-----
Von: typo3-project-typo3v4mvc-bounces at lists.typo3.org [mailto:typo3-project-typo3v4mvc-bounces at lists.typo3.org] Im Auftrag von Claus Due
Gesendet: Donnerstag, 1. März 2012 11:46
An: TYPO3 v4 MVC project
Betreff: Re: [TYPO3-mvc] RFC: New comments in FLUID

Hi everybody,

> I just read all of your comments and thought a lot of "no, please don't" :).

Yep. I have that same feeling after loosely reading. And here's why:

> If we really want a dedicated comment syntax, we should go for "<f:comment></f:comment>" as a tiny non-rendering comment view helper.

Fluid already has f:comment. Why do we need a change that increases parsing time, complicates transparency and uses off-standard annotations, when we already have something that does exactly what is needed? Is this for aestethic reasons in your editor's code highlighting? If so... then I would have to say that pushing for a core change in Fluid itself is rather optimistic given the severe implications.

My vote is a clear no. This is bad thinking. We don't want this given the performance and transparency concerns combined with the fact that what you desire to do is already possible to do. Sorry, but it's just not smart and not necessary.

Cheers,
Claus
_______________________________________________
TYPO3-project-typo3v4mvc mailing list
TYPO3-project-typo3v4mvc at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-typo3v4mvc


More information about the TYPO3-project-typo3v4mvc mailing list