I would like to freeze new features development for Wicket 1.5 and move this feature to 1.6. I like the feature and I understand how important it is but I also I would like to release 1.5 as soon as possible.
I just migrated our application to 1.5 (it is relatively big) and I'll report/debug problems if we decide to add this feature, but as I said already - I prefer to postpone it. On Tue, Nov 9, 2010 at 12:34 AM, mbrictson <[email protected]> wrote: > > Hi Jeremy, > > My company has spent quite a bit of time working through the issues of > resource merging and dependency resolution in Wicket, specifically with > JavaScript, so I thought I could add my two cents to this discussion. > > > [email protected] wrote: > > > > An IHeaderResponse that aggregates resources into a single http request. > > > > I've used wicketstuff-merged-resources for this purpose, and it works well. > But upgrading it to support Wicket 1.5 looks like it will be a daunting > task. If you could add an elegant way to support this feature within Wicket > 1.5 itself (or at least make it easier to accomplish), that would be > extremely helpful. > > > > > ONE: Header/footer splitting. > > > > I agree with Igor that the responsibility of contributing to the header or > the footer belongs to the component developer. This feature would be very > much appreciated. > > > > > NOTE: after committing this, I had planned to start a discussion about > > renaming IHeaderContributor / IHeaderResponse to IResourceContributor / > > IResourceResponse in trunk / 1.5 so that it is more generic since now > > users > > can decide where they want things. > > > > +1 > > > > > TWO: the ability to configure resource reference dependencies within your > > app. > > > > While resource merging is a deployment concern and therefore makes sense to > configure at the application level, I think resource reference dependencies > are a concern best left to the component author. I agree with Igor that the > component should be responsible for calling code to resolve dependencies to > obtain resource references (he suggested a behavior or static helper > method; > I use the former), and then add those references to the header response (or > footer as the case may be). > > I've actually implemented a fairly complete solution for resolving > JavaScript dependencies along these lines. If you're curious, please email > me directly and I can share the code with you (it's Apache v2 licensed). > > -- > Matt > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Re-jira-Commented-WICKET-3149-Merge-DecoratingHeaderResponse-to-trunk-tp3029081p3032848.html > Sent from the Forum for Wicket Core developers mailing list archive at > Nabble.com. >
