Oh, I didn't explain that part, huh? :-( Hey, it was a long post!
I mentioned the problem this way:
The thorniest problem is that components package their JS
dependencies in files stored in the component's directory.
Something would have to be done to ensure that the same file is
I don't understand how your proposal solves the problem. How shall
Wicket ever know that two *.js files (may be with same name and size
but in different directories/jar because they belong to different
re-usable components) are the same and shall be downloaded just once?
Juergen
On 9/30/05,
Hi Folks,
It's been far too long since I asked a question on this list. One might
think I was starting to get it. :-)
I'm planning on building my first reusable panel soon; and I'm pretty
sure I understand what I need to in order to do this, but one thing is
nagging at me. The panel will
I see what you mean. So far we made sure that e.g. a DatePicker
doesn't contribute the same javascript includes for each instance. But
that's still too limited I guess. We additionally need some way to
globally (application level) register scripts, so that the header
contribition algoritm can
