Hi Andrea,
thx for the reference. Michael's proposal is awesome and I'm I think we
should go for a better model interface hierarchy. But this proposal, of an
IReadyOnlyModel as an IModel extension, wasn't discussed. My point is that
we can provide an interface "designed" to provide a function as
Github user sebfz1 commented on the issue:
https://github.com/apache/wicket/pull/218
My bad, you used it! ;)
Then opened question: why not centralize all in `JQueryResourceReference`
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user sebfz1 commented on the issue:
https://github.com/apache/wicket/pull/218
There is/was already a `VERSION_2` in `DynamicJQueryResourceReference`.
I think only one should be kept...
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/wicket/pull/218
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user solomax opened a pull request:
https://github.com/apache/wicket/pull/218
[WICKET-6354] string constants and references are added for all versiâ¦
â¦ons of jquery
You can merge this pull request into a Git repository by running:
$ git pull
Hi Pedro,
Your proposal will not work because Java does not resolve functional
interfaces to subtypes of the target type. For example, take the Label
constructor:
public Label(String id, IModel model)
I would like to use this constructor as follows:
new Label("id", Math::random)
In Wicket 8
