[
https://issues.apache.org/jira/browse/TAP5-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-768.
-------------------------------------
Resolution: Won't Fix
Assignee: Howard M. Lewis Ship
The way Tapestry's JavaScriptStack mechanism has evolved overlaps with this in
a way that would make implementing this problematic. It's now easy (and getting
easier) to add JS to a stack, which is more performant at runtime anyway.
> When Tapestry includes a JavaScript library, it should look for an adjacent
> second file that lists dependencies of that library
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-768
> URL: https://issues.apache.org/jira/browse/TAP5-768
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> Or, perhaps this should be a bit of configuration in some service. Either
> way, there should be a way that a component can includes a JavaScript file,
> and automatically get the dependencies of that JavaScript file. For example,
> I'm working on some code that uses Modalbox, and it has a dependency on
> scriptaculous' builder.js ... if I have multiple components that use Modalbox
> in different ways, each of them needs to know about that relationship.
> In fact, for YUI this is even more important as each component has some very
> specific dependencies.
> This could even be generalized to allow both dependent libraries AND
> dependency CSS (a common feature for Ajax libraries) to be automatically
> included.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
