[TYPO3-mvc] f:form.dateselect ? (fluid)

Martin Kutschker masi-no at spam-typo3.org
Tue Jan 5 15:19:21 CET 2010


Franz Koch schrieb:
> 
>>> these are exactly the reasons (apart from no time ;) ) why this has not
>>> been done yet.
>>
>> Maybe it makes sense to provide within FLUID a set of view helpers for
>> ExtJS as it is shipped with
>> the Core (and there is infrastructure for loading it), but create
>> additional extensions/packages for
>> other frameworks.
> 
> I wonder for what I would need a FLUID viewhelper for JS stuff. Isn't it
> so, that the trend is to move all js at the end of the body tag in a
> external file and thus only provide some special markup (IDs, classes)
> in your HTML that your JS-methods are aware of?
> 
> At least I'm working that way now, that f.e.

I think the point is that you can say in the FLUID template "this input field is a date field (with
a date selector widget". FLUID and it's helpers will load the necessary libraries. But this raieses
the question how FLUID may maniplates objects outside its scope ($TSFE).

> Ok, it would be nice if FLUID could also trigger the integration of
> certain JS snippets to a autogenerated merged JS file, but that's not
> necessary in the first step I think, if ever. If FLUID would provide
> common HTML-markup for use in JS, addon-extensions/libraries for various
> JS-frameworks might arise in TER which could hook in the FLUID
> viewHelpers and trigger themselfs the necessary JS integration for their
> particular framework. Might that be a solution?

I should have read to the end before I start to write an answer :)

Masi


More information about the TYPO3-project-typo3v4mvc mailing list