[jira] Commented: (WICKET-767) Generify IModel
[
https://issues.apache.org/jira/browse/WICKET-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513838
]
Eelco Hillenius commented on WICKET-767:
I've seen Gafter talk about it on his blog, but is that through now?
Anyway, *I* would love to start coding with Scala. That language is seriously
cool. Too bad it currently looks and feels like a project for academics (in
order words, they don't seem to focus much on getting the language out there).
> Generify IModel
> ---
>
> Key: WICKET-767
> URL: https://issues.apache.org/jira/browse/WICKET-767
> Project: Wicket
> Issue Type: Wish
>Reporter: Willis Boyce
> Fix For: 1.4.0-alpha
>
>
> I find myself writing custom IModel implementations that depend on the
> underlying object being some specific type. It would be nice if I could get
> some type safety using generics, e.g.
> class MyCustomModel implements IModel
> {
> MyCustomObject getObject(Component component) { ... }
> ...
> }
> I imagine that this has already been suggested, but I couldn't find a JIRA
> issue about it in the road map.
> I don't think that the core Wicket code would change too much, except in
> cases where the code actually cared what was in the model. Elsewhere it can
> just use IModel.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-767) Generify IModel
[
https://issues.apache.org/jira/browse/WICKET-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513834
]
Johan Compagner commented on WICKET-767:
eelco: with java7 they will improve the syntax (hide the verbosity) if i am not
mistaken so then you also will love it ;)
> Generify IModel
> ---
>
> Key: WICKET-767
> URL: https://issues.apache.org/jira/browse/WICKET-767
> Project: Wicket
> Issue Type: Wish
>Reporter: Willis Boyce
> Fix For: 1.4.0-alpha
>
>
> I find myself writing custom IModel implementations that depend on the
> underlying object being some specific type. It would be nice if I could get
> some type safety using generics, e.g.
> class MyCustomModel implements IModel
> {
> MyCustomObject getObject(Component component) { ... }
> ...
> }
> I imagine that this has already been suggested, but I couldn't find a JIRA
> issue about it in the road map.
> I don't think that the core Wicket code would change too much, except in
> cases where the code actually cared what was in the model. Elsewhere it can
> just use IModel.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-767) Generify IModel
[
https://issues.apache.org/jira/browse/WICKET-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513782
]
Eelco Hillenius commented on WICKET-767:
Yes, this is one of the major things we're planning to re-introduce (we had
this in the 2.0 branch) for Wicket 1.4. Unfortunately (imho) we can't generify
models without also generifying components as well. Personally, I'm not crazy
about the change, but from earlier threads we can conclude that most people are
in favor of it.
We'll start working on this once 1.3 is final.
> Generify IModel
> ---
>
> Key: WICKET-767
> URL: https://issues.apache.org/jira/browse/WICKET-767
> Project: Wicket
> Issue Type: Wish
>Affects Versions: 1.2.6
>Reporter: Willis Boyce
>
> I find myself writing custom IModel implementations that depend on the
> underlying object being some specific type. It would be nice if I could get
> some type safety using generics, e.g.
> class MyCustomModel implements IModel
> {
> MyCustomObject getObject(Component component) { ... }
> ...
> }
> I imagine that this has already been suggested, but I couldn't find a JIRA
> issue about it in the road map.
> I don't think that the core Wicket code would change too much, except in
> cases where the code actually cared what was in the model. Elsewhere it can
> just use IModel.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
