[TYPO3-team-templavoila] RFC #11521

[Fernando Arconada]

I have to apologized for not include the patch but I have asked Ron for it

The look and feel it's something that have to change: i agree with you. 
We could start thinking about it and meet Ron and talk about it in T3CON09

Kind Regards

Fernando Arconada
El Thu, 16 Jul 2009 08:49:59 +0200, Tolleiv Nietsch escribió:

> Hi,
> I thought you're usually supposed to provide a patch with such requests
> ;)
> 
> I don't like to idea of just including foreign JS/CSS files very much.
> 
> Regarding the proposed solution it should imho not just be a listing of
> header-parts, it should be a list of files. Otherwise it would be much
> harder to determine if something is included twice.
> 
> Personally I think that there's maybe really the need to change the
> look&feel of the page-module - but in this case we should provide some
> documented API to use "skins" for it instead of including some JS/CSS
> files. I share Dmitry's opinion that we shouldn't change thing too fast.
> Maybe we could get in touch with Ron at the T3CON and discuss how a real
> API for this could look like.
> 
> I've to admit though that Ron's example doesn't look too bad.
> 
> Just my two cents...
> 
> Best-
> Tolleiv
> 
> Fernando Arconada schrieb:
>> This is an SVN feature request.
>> 
>> Type: New feature
>> 
>> Bugtracker references:
>> http://bugs.typo3.org/view.php?id=11521
>> 
>> Branches:
>> trunk
>> 
>> Problem:
>> The current look&feel it is a bit annoying
>> 
>> Solution:
>> Ron Hall is proposing to add a DS tag for page templates that would
>> allow the developer to add paths for stylesheets and javascript files
>> that would load with the current TV page module. Of course, they would
>> need fall after any other stylesheets and JavaScript provided by the
>> backend.
>> 
>> Here is an example of the tag
>> 
>> <bePageAssets>
>> 
>> <![CDATA[
>> <link rel="stylesheet" type="text/css" href="/fileadmin/templates/
>> mybackend.css" />
>> <script src="/fileadmin/mybackend.js" type="text/javascript"></script>
>> ]]>
>> 
>> </bePageAssets>
>> 
>> Currently the developer has to put style info and javascript inside
>> each DS. Having this tag would have the following advantages:
>> 
>> 1) Easier maintenance of datastructures. The develop could put backend
>> styles and JavaScript shared by multiple datastructures in one file
>> each
>> 
>> 2) The editor's browser would cache these files and make for better
>> performance.
>> 
>> 
>> Possible look&feel (much more ussable)
>> http://templavoila.busynoggin.com/