As the work continues on the branch, Hielke provided the first testcases, I fixed many and I implemented support for resource bundles: https://github.com/papegaaij/wicket/commit/c7cd30046728568981e96251d7f6d627d06958a9 (until I decide to rebase again :) ), for all changes in the branch: https://github.com/papegaaij/wicket/compare/trunk...wicket%2Bwiquery
Resource bundles are completely transparent on the side of the components, where resources are added. If one of the resources from a bundle is added, the bundle is added in stead. All other resources are marked as already added. This allows you to register bundles for external libraries, without the library knowing about the bundles. You can create the bundles manually, or use a concatenating resource. Documentation is still mostly missing and an example is also needed, just as some more tests. Reading through some issues on JIRA, I guess WICKET-4000 and WICKET-4235 could also be fixed with this. Some changes will be needed to header rendering to let HeaderResponse render wicket:head header contributions, but that's no problem for Wicket 6. Best regards, Emond Papegaaij On Friday 02 December 2011 09:33:44 Emond Papegaaij wrote: > Hi all, > > For the past few weeks, and especially the last few days, Hielke Hoeve and I > have been working on improvements to resource management in Wicket. Most of > the improvements are based on work in WiQuery, but the actual > implementation is from scratch. The targets for the improvements can be > found in WICKET-4273. In short, it boils down to following points: > - Dependency support for resources > - Sorting of resources in the header > - Native resource bundle support in Wicket > - Aggregating many small scripts into 1 large script tag, esp. for events > > The target for these changes will be Wicket 6 and the work in progress can > be found on github: > https://github.com/papegaaij/wicket/compare/trunk...wicket%2Bwiquery > > At the moment, all features, except the resource bundles are implemented and > working. Documentation is still missing on most places. I've also not yet > come to writing tests and an example on how to use it. > > Please provide your feedback on the code, here on the mailing list or at > JIRA. > > Note to Jeremy: I deleted some of the code you contributed to Wicket 1.5 > because there was a large overlap in functionality, and it proved difficult > to keep the old code working as is. It would be great if you could shed > some light on what the exact problem was, you were trying to solve with > that code, so I can make sure that it can also be solved with this new > approach. > > Best regards, > Emond Papegaaij
