You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (Closed) (JIRA)" <ji...@apache.org> on 2011/10/18 02:11:11 UTC

[jira] [Closed] (TAP5-1684) Allow custom script ordering

     [ https://issues.apache.org/jira/browse/TAP5-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1684.
--------------------------------------

    Resolution: Won't Fix

This is going down the rabbit hole ... there comes a time where there's no good way to server edge cases like this, and provide out-of-the-box functionality, and backwards compatibility, and have a system that can be easily described.  Also, you should your .less -> CSS conversion on the server side (I hope 5.4 will have the pipeline to do that automatically).
                
> Allow custom script ordering
> ----------------------------
>
>                 Key: TAP5-1684
>                 URL: https://issues.apache.org/jira/browse/TAP5-1684
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2.6
>            Reporter: Martin Papy
>              Labels: css, javascript
>
> Tapestry should allow some sort of custom ordering in JS / CSS.
> Exemple : if I want to work with Less ( http://lesscss.org/ ), I need to make sure that *.less script are added before the less.js library.
> Currently the only way I can do that is by adding those script manually in the Layout which is not very convenient

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira